ServiceNow developer with 5 years building ITSM and HR Service Delivery solutions on the Now Platform. Built a catalog and Flow Designer onboarding process that cut new-hire setup time from 6 days to 2. Keeps instances upgrade-safe with scoped apps, ATF tests and clean update set practices.
Built an employee onboarding catalog with Flow Designer and IntegrationHub spokes for Workday and Active Directory, cutting setup time from 6 days to 2
Developed scoped apps with Business Rules, Script Includes and UI Policies for 3 departments with no impact on 2 family upgrades
Created 180 Automated Test Framework tests that now run before every release
Tuned slow list views and GlideRecord queries, reducing average form load time by 35%
Junior ServiceNow Developer, Brightriver IT Solutions (Pittsburgh, PA)
Jan 2021 – Jul 2022
Configured incident, problem and change workflows for 6 client instances
Built REST integrations to pull asset data from Jamf into the CMDB
Education
B.S. Information Sciences and Technology, Penn State University (Aug 2016 – May 2020)
Skills
ServiceNow: ITSM, HRSD, CMDB, Service Portal, Flow Designer, IntegrationHub, ATF
Development: JavaScript, Glide API, REST and SOAP integrations, AngularJS
Certifications: Certified System Administrator, Certified Application Developer
How to write a ServiceNow Developer resume
A strong ServiceNow Developer resume shows the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Put your most relevant recent role first and make every bullet show a result, not a duty.
Sections, in order
Summary
Experience
Projects
Skills
Education
Length: One page for most candidates; move to two only if every line is relevant.
Summary: Write two or three lines: your role, your strongest skills, and one result that proves them.
Skills to feature
Programming languages
System design
Cloud platforms (AWS, GCP, Azure)
CI/CD
Testing and code review
Databases and SQL
Observability
Security fundamentals
APIs and integrations
Technical documentation
Example bullet points
Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users
Introduced contract tests and staged rollouts, reducing production incidents by 45% in two quarters
Migrated 30 services to Kubernetes with Terraform, lowering cloud spend by $250k a year
Tips from recruiters
Group skills by category (for example "Languages: Go, TypeScript") so recruiters and ATS parsers find them quickly.
Link to a repository, demo or write-up for at least one project you can talk about in depth.
Name the stack inside each bullet; keyword matching happens at the bullet level, not only in the skills list.
Recommended templates
Classic (ATS-friendly): Jake's-style LaTeX classic: small caps and hairline rules
Tech (ATS-friendly): Developer style: mono headings and tags, sans body
Modern (ATS-friendly): Clean single column with accent headings and rules
ServiceNow Developer resume FAQ
What should a ServiceNow Developer resume include?
A ServiceNow Developer resume should show the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Use these sections in this order: Summary, Experience, Projects, Skills and Education. Put your most relevant recent role first and make every bullet show a result, not a duty.
What is the best resume template for a ServiceNow Developer?
Classic, Tech and Modern work well for ServiceNow Developer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a ServiceNow Developer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a ServiceNow Developer put on a resume?
Prioritize the skills named in the job posting. Common ones for ServiceNow Developer roles are Programming languages, System design, Cloud platforms (AWS, GCP, Azure), CI/CD, Testing and code review and Databases and SQL.
How do I write strong ServiceNow Developer resume bullet points?
Start with an action verb, say what you did, and end with a measurable result such as latency, uptime and deploy frequency. For example: "Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users."