Technical screening questions
Ask for one example per question and listen for specifics.
- When do you use a business rule versus a client script? A good answer: Server-side logic and data rules versus form behavior in the browser.
- How do you move changes between instances? A good answer: Update sets or application repositories, and clone considerations.
- How have you integrated ServiceNow with another system? A good answer: REST integrations, authentication and error handling.
- What ITSM processes have you configured? A good answer: Incident, change, problem or request with specific work.
- How do you avoid performance issues in scripts? A good answer: Efficient GlideRecord usage and limiting queries.
Quick screening questions
Use these when you have only a few minutes.
- Which modules have you built on?
- How do you manage update sets between instances?
- Describe an integration you built.
What separates the levels
Match the level to the requirement before you submit.
- Junior: configures and fixes tickets.
- Mid: builds features and integrations.
- Senior: designs platform architecture and governance.
Red flags
Any of these is a reason to probe further.
- Admin-only experience for a developer role.
- Cannot describe update sets.
- No scripting examples.
Tools you should hear mentioned
A ServiceNow developer with real experience usually names several of these without prompting.
- ServiceNow platform
- Glide scripting
- Flow Designer
- Update sets
- REST and SOAP integrations
- Service Portal
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a ServiceNow developer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.