Interview questionsUpdated 12 Oct 2026 · Team InterviewPlan

ServiceNow Developer Interview Questions and Answers

ServiceNow developer interviews test scripting on the platform, ITSM process knowledge and how you build solutions that survive upgrades. Panels ask about business rules, client scripts, GlideRecord, Flow Designer, ACLs and integrations. These questions reflect what ServiceNow developers face in 2026 at partners, enterprises and managed service providers.

What interviewers test in a ServiceNow developer interview

Most interviews include scripting questions, scenario-based design such as automating a catalog request, and process questions on ITSM. Some include a live task in a personal developer instance.

Interviewers value platform best practices: low-code first, minimal customisation of out-of-box records, secure ACLs and clean update set management.

  • Server-side: business rules, script includes, scheduled jobs and GlideRecord
  • Client-side: client scripts, UI policies, GlideAjax and g_form
  • Automation: Flow Designer, subflows, actions and IntegrationHub
  • Security: roles, ACLs, data policies and domain separation basics
  • Delivery: update sets, scoped apps, ATF tests and upgrades

Technical topics to revise

Use a free personal developer instance to build a small catalog item with a flow, a business rule, a client script with GlideAjax and an ACL. Being able to explain each piece covers most technical questions.

  • Before, after, async and display business rules
  • onLoad, onChange, onSubmit and onCellEdit client scripts
  • GlideRecord query patterns, addQuery, addEncodedQuery and setLimit
  • GlideAjax with client-callable script includes
  • ACL evaluation order: table, field, roles, conditions and scripts
  • Flow Designer triggers, subflows, custom actions and spokes
  • Update sets, scoped applications and the application repository
  • Automated Test Framework, instance scan and upgrade skipped records

How to structure your answers

For scripting questions, state where the code runs, server or client, and why that location is right. Mention performance, such as avoiding synchronous server calls from client scripts.

For project stories, cover the process, the solution with low-code and code parts, and measurable outcomes like reduced ticket handling time or fewer manual steps.

How InterviewPlan AI helps you prepare

ServiceNow mock interviews ask scripting, ITSM and scenario questions and give feedback on clarity. Resume AI helps present your platform work in business outcomes, such as automated fulfilment.

Interview Copilot provides live speaker-labelled transcription and resume-grounded drafts during interviews on Teams, Zoom, Meet and Webex. Once hired, ServiceNow Job Support gives expert-plus-AI help with stories and scripts in your first 90 days, at $5 per hour with 200 AI credits included.

Questions and model answers

9 questions you are likely to hear.

  1. Explain the different types of business rules and when to use each.

    Why they ask: Business rule timing is fundamental to ServiceNow development.

    Sample answer: Before business rules run before the record is saved, so I use them to set or validate field values on the current record without an extra update. After rules run after the save, for actions on related records, like updating a parent. Async rules run after the save in the background, which suits slow work such as integrations or heavy calculations, so users are not kept waiting. Display rules run when a form loads and pass data to the client through g_scratchpad. I avoid calling current.update() in before and after rules because it causes recursion and duplicate audit entries.

  2. What is the difference between a client script and a UI policy?

    Why they ask: This checks low-code versus code judgement on the client side.

    Sample answer: UI policies are a no-code way to make fields mandatory, read-only or visible based on conditions, and they are easier to maintain, so I use them first. Client scripts are JavaScript that run in the browser on load, change, submit or cell edit, for logic UI policies cannot handle, such as calling the server with GlideAjax, complex validation or setting values dynamically. UI policies run after client scripts on load. In one project, replacing about 20 client scripts that only toggled mandatory fields with UI policies made forms easier for the admin team to manage.

  3. How do you get server data in a client script without slowing down the form?

    Why they ask: Performance and correct client-server patterns are tested here.

    Sample answer: I use GlideAjax with a client-callable script include and an asynchronous callback using getXMLAnswer, so the form does not freeze while waiting. I avoid synchronous calls like getReference without a callback or GlideRecord in client scripts, which are slow and blocked in some contexts. If the data is needed on load, a display business rule can put it in g_scratchpad, avoiding an extra round trip. In an incident form, replacing several synchronous lookups with one GlideAjax call returning JSON reduced load time noticeably for agents.

  4. How do ACLs work in ServiceNow?

    Why they ask: Security misconfigurations can expose sensitive data.

    Sample answer: ACLs control access to tables, fields and operations like read, write, create and delete. For a field, the user must pass both the table-level ACL and the field-level ACL. Within an ACL, the user must meet all of the roles, condition and script requirements. ServiceNow evaluates the most specific matching rules first, such as table.field before table.*, and if any matching rule at that level grants access, access is granted. I prefer roles and conditions over scripts for performance. I use the security debugger to test, and I once tightened HR case ACLs after finding a broad wildcard read rule.

  5. When would you use Flow Designer instead of a business rule?

    Why they ask: Modern ServiceNow development favours low-code automation.

    Sample answer: I use Flow Designer for process automation that business analysts or admins should understand and maintain: approvals, notifications, task creation, catalog fulfilment and integrations through IntegrationHub spokes. It has built-in execution logs, which makes troubleshooting easier. I use business rules for simple, fast data logic on the record itself, such as setting fields before save, or when performance is critical. For complex reusable logic, I write script includes and call them from flows through custom actions. Migrating a legacy workflow for new hire onboarding to Flow Designer made it easier to change approval steps without code.

  6. How do you integrate ServiceNow with an external system?

    Why they ask: Integrations are a major part of ServiceNow work.

    Sample answer: For outbound, I use REST Messages or IntegrationHub spokes where available, with credentials stored in connection and credential aliases rather than scripts. I call them from flows or async business rules so users are not blocked, handle errors and log responses. For inbound, I use the Scripted REST API or the Table API with a dedicated integration user with minimal roles, and import sets with transform maps for bulk data. A MID Server handles systems inside the client network. I built an integration that created Jira issues from ServiceNow problems and synced status both ways.

  7. What are update sets, and what problems have you faced with them?

    Why they ask: Release management issues are a common source of production problems.

    Sample answer: Update sets capture configuration changes like business rules, forms and scripts in one instance so they can be moved to another, usually from dev to test to production. They do not capture data like users or most records unless added manually. Common problems are changes made in the wrong update set, missing dependencies and collisions with newer versions in the target. I preview every update set, resolve errors before committing and keep update sets small and named by story. For larger work, scoped applications deployed through the application repository are cleaner.

  8. How do you keep customisations upgrade-safe?

    Why they ask: Upgrade pain is a major cost for ServiceNow customers.

    Sample answer: I avoid modifying out-of-box scripts and records directly; instead I create new business rules, script includes or extend tables. I use configuration options and low-code tools first. I keep custom code in scoped applications where possible. Before each family upgrade, I review skipped records in the upgrade history and decide whether to keep our version or revert to the new baseline. Automated Test Framework tests on key processes run after upgrades in sub-production. In one client, reverting about 60 unnecessary customisations made the next upgrade much smoother.

  9. Tell me about a ServiceNow solution you built that improved a process.

    Why they ask: This shows platform skill applied to business value.

    Sample answer: At a services company, laptop requests went through email, and fulfilment took over a week on average. I built a catalog item with variables and UI policies, a flow with manager and budget approvals, automatic task creation for procurement and IT, and an integration with the asset system to reserve devices. I added ATF tests for the approval paths. After launch, the average fulfilment time dropped to a few days, request status became visible to employees in the portal, and the IT team stopped tracking requests in spreadsheets.

FAQ

Questions people ask about servicenow developer.

Which ServiceNow certifications help in interviews?

Certified System Administrator is the baseline, and Certified Application Developer is important for developer roles. Certified Implementation Specialist credentials for ITSM, HRSD or other modules help for specialised roles. Interviewers still test real scripting and scenarios.

How much JavaScript do ServiceNow developers need?

Solid JavaScript fundamentals: functions, objects, arrays and JSON, plus ServiceNow APIs like GlideRecord, GlideSystem and g_form. Interviewers often ask you to write a GlideRecord query or a client script from memory.

Do I need to know ITIL for ServiceNow interviews?

Yes, at least ITIL basics for incident, problem, change and request management. ServiceNow implements these processes, and interviewers expect you to understand why a feature exists, not just how to configure it.

Is ServiceNow Job Support available?

Yes. InterviewPlan AI's ServiceNow Job Support provides live expert-plus-AI help during your first 90 days with stories, scripts and integrations. It costs $5 per hour including 200 AI credits, and hours never expire.

P.S.

Reading helps. Practising out loud helps more.

Start free with 5 live minutes and 100 AI credits for Resume AI, Job Search, Auto-Apply, mock interviews and Behavioral Coach.