This is for a ServiceNow Developer there was no ServiceNow Developer Template only Service Administrator.
The Service Management Platform Team is charged with governing and simplifying Information Technology Service Management across multiple internal and external teams and business partners in relation to ServiceNow. This role is responsible for developing, managing and directing ServiceNow for support services to ensure they meet business needs and IT requirements. This position will need to interface closely with the Service Delivery, Architecture and Solution Teams on the implementation of IT Service Management. The individual in this role will support design, execution, and maintenance of our ServiceNow integrations across multiple modules. They will work across technology teams, process owners and counterparts to define, execute and manage application sustainment, enhancement, and/or new development.
Primary Purpose:
The ServiceNow Developer will analyze, design and implement capabilities on our ServiceNow platform. These capabilities span small stories to large epics and, while primarily focused around ITSM, may be spread across various ServiceNow technology areas and integrations. Our roadmap and backlog include substantial improvements across ITSM, removing customizations to return to out-of-box, usability improvements in the core platform as well as through mobile, portal and other integrations and may also span into areas including but not limited to CMDB, Discovery, SecOps, ITOM and CSM. This role will participate in the entire development lifecycle from requirements through production delivery. This individual needs to have strong analytical skills as well as an in-depth understanding of IT Service Management processes, high level understanding of application, infrastructure and network and business processes.
1) Role Scope & Success
What are the top 3 outcomes you expect this developer to deliver in the first 90 days?
Probes: Is it more about reducing technical debt (removing customizations), building new features, stabilizing integrations, or improving user experience?
Building new features with a focus on user experience and reducing technical debt
2) Module Priorities
Which ServiceNow modules are in immediate scope for this role over the next 6–12 months (e.g., ITSM, CMDB, Discovery, SecOps, ITOM, CSM) and in what order of priority?
Probes: Any roadmap epics in flight? What’s the balance between ITSM work vs. expansion into other modules?
ITSM is the focus but a knowledge is SecOps and CSM is a bonus, we have all these modules in ServiceNow and enhancements can be requested for any.
3) Customizations vs. Out-of-Box
What’s the current level of platform customization, and what’s the strategy/timeline for returning to out?of?box (OOB) capabilities?
Probes: Which customizations are critical and must remain? Are there known “hot spots” causing upgrade pain?
We are working aggressively to move out of box to take on other advances in ServiceNow like Now Assist, we do have technical debt with customizations but we have had an approach to limit where we can
4) Integrations & Data Flows
Which systems does ServiceNow integrate with today, and which integrations will this developer own or enhance?
Probes: Integration patterns (MID Server, REST/SOAP, IntegrationHub spokes)? Any data quality or reconciliation challenges with CMDB/discovery sources?
We have over 50+ integrations, a ServiceNow developer has to be familiar with all Integration patterns.
5) Development Lifecycle & Tooling
What does your SDLC look like for ServiceNow (requirements → design → dev → test → UAT → prod)?
A must is scripting and CSA , UX is important because that is a skill we would like to focus more on. We own all these modules so all are nice to haves
8) Process Maturity & Pain Points
Which ITSM processes are most mature (incident, problem, change, request), and where are the biggest friction points you want solved?
What experience or performance goals are you targeting (portal usability, Mobile app, Agent Workspace, page load times, query performance)?
Probes: Any established KPIs—MTTR, deflection via portal/virtual agent, performance baselines, Lighthouse pages that need tuning?
For use we work in the ServiceNow Agile environment so really for us the MTTR is story completion and development accuracy
10) Logistics: Work Model, Timeline & Budget
What are the interview steps, expected start date, work location model, and budget/level for this role?
Probes: Contract length or FTE conversion potential, on?call or release?weekend expectations, time zone coverage, clearance requirements.
The work location is remote, we do have release windows on Thursday nights between 1 and 4 am, but we can discuss releasing some earlier it needed. We prefer EST and Central time zone. Prefer it the resource does not need sponsorship because we might be eventually looking to hire full time
Optional “Quick Wins” Check
If you could flip one thing from custom to OOB tomorrow, what would it be and why?
Which backlog items are blocked today due to missing skills or bandwidth?
Any upcoming platform upgrades or store app deployments we should plan around? No
Applicant Notices & Disclaimers
For information on benefits, equal opportunity employment, and location-specific applicant notices, click here
At SPECTRAFORCE, we are committed to maintaining a workplace that ensures fair compensation and wage transparency in adherence with all applicable state and local laws. This position’s starting pay is: $ 70.00/hr.
