Home › Blog › ServiceNow Developer Interview Questions (2026): 30 on GlideRecord, Business Rules, ACLs

ServiceNow Developer Interview Questions (2026): 30 on GlideRecord, Business Rules, ACLs

ServiceNow developer interview questions test the platform's scripting model: where code runs (browser or server), which script type fits a requirement, GlideRecord, ACLs, update sets and scoped applications, integrations and performance. A strong candidate picks the lightest tool that works, often configuration before code, and can explain the trade-off.

ServiceNow developer interview questions test the platform's scripting model: where code runs (browser or server), which script type fits a requirement, GlideRecord, ACLs, update sets and scoped applications, integrations and performance. A strong candidate picks the lightest tool that works, often configuration before code, and can explain the trade-off.

This page is about the ServiceNow platform, not about interviewing at ServiceNow the company; for that, see ServiceNow coding interview questions and the ServiceNow online assessment. Release names and UI labels change twice a year, so the 30 questions below stick to concepts that hold across current releases.

ServiceNow developer fundamentals: questions 1–9

  1. Client-side vs server-side scripts? Client scripts, UI policies and catalog client scripts run in the browser with g_form, g_user and GlideAjax; business rules, script includes, scheduled jobs and fix scripts run on the server with GlideRecord and gs. Choosing the right side is the core design skill.
  2. Which client script types exist? onLoad, onChange, onSubmit and onCellEdit (list editing). onChange receives control, oldValue, newValue, isLoading, isTemplate; return early when isLoading is true to skip the initial form load.
  3. UI policy vs client script? UI policies make fields mandatory, read-only or visible under conditions without code and can reverse when the condition is false. Use them for field behaviour, and client scripts for logic, validation or server calls.
  4. Which business rule types exist? Before (runs before the database write; set fields on current without calling update()), after (runs after the write; update related records), async (after, in a background job, for slow work or integrations) and display (before the form loads; passes data to the client through g_scratchpad).
  5. What are current and previous? In a business rule, current is the record being processed and previous holds its values before the change, so current.state.changesTo(6) or previous.assigned_to != current.assigned_to detect transitions.
  6. Write a basic GlideRecord query. var gr = new GlideRecord('incident'); gr.addQuery('active', true); gr.addQuery('priority', 1); gr.query(); while (gr.next()) { gs.info(gr.getValue('number')); }. Use get() for one record by sys_id and addEncodedQuery() to reuse a list filter.
  7. What is a script include? A reusable server-side class or function library. Marked client callable and extending AbstractAjaxProcessor, it can be called from the browser through GlideAjax.
  8. What is dot-walking? Following reference fields through related tables, such as current.caller_id.manager.email in scripts, conditions or list columns. It's convenient, but each hop can cost a query, so avoid deep walks inside loops.
  9. What is a sys_id? The 32-character unique ID of every record. Don't hard-code sys_ids in code that moves between instances; use system properties or lookups.

Intermediate ServiceNow developer questions: 10–18

  1. Why use GlideAjax rather than client-side GlideRecord? Client-side GlideRecord is discouraged: it returns whole records and, without a callback, blocks the browser. GlideAjax calls a client-callable script include asynchronously, for example with getXMLAnswer(), and returns only the data you need.
  2. How are ACLs evaluated? Access to a field needs a passing table-level ACL and a passing field-level ACL. Rules are matched from the most specific (table.field) to the most general (parent table, then *), and a rule passes only if its roles, condition and script all pass. The security debugger shows which rule decided.
  3. What moves in an update set, and what doesn't? Customisations to configuration records such as business rules, form layouts and ACLs move; transactional data such as incidents and users doesn't. Preview before committing to catch collisions and missing dependencies.
  4. Global vs scoped applications? Scoped apps have their own namespace (such as x_acme_app), controlled cross-scope access and cleaner deployment through the application repository or source control; global is the legacy shared space. New custom apps should be scoped.
  5. What is GlideAggregate for? Counting, summing or grouping in the database instead of looping: var ga = new GlideAggregate('incident'); ga.addQuery('active', true); ga.addAggregate('COUNT'); ga.query(); if (ga.next()) gs.info(ga.getAggregate('COUNT'));. It's much faster than getRowCount() on large tables.
  6. When do you use setWorkflow(false) and autoSysFields(false)? setWorkflow(false) stops business rules and engines running on that update, which suits controlled data fixes; autoSysFields(false) stops updates to system fields such as sys_updated_on. Neither belongs in normal business logic.
  7. Flow Designer vs script? Flow Designer (inside Workflow Studio on recent releases) builds low-code flows, subflows and actions, with spokes for integrations, and is the recommended place for process automation. Script when logic is complex or performance-critical, and wrap it in a custom action so the flow stays readable.
  8. How do you build an inbound integration? The Table API for simple create, read, update and delete; a Scripted REST API when you need a custom contract or validation. Authenticate with OAuth or basic auth over HTTPS as a dedicated integration user with minimal roles, and return proper status codes.
  9. Import sets and transform maps? Data lands in a staging import set table; a transform map maps fields to the target table, with coalesce fields deciding insert versus update and transform scripts for logic. Failed rows stay in staging for review.

Experienced ServiceNow developer questions: 19–27

  1. How do you avoid recursive business rules? Don't call current.update() in a before or after rule on the same table; in before rules, just set the fields. If an update is unavoidable, add conditions that stop the loop or use setWorkflow(false) in a controlled way.
  2. How do you make server scripts fast? Query only what you need with setLimit(), indexed fields and encoded queries; use GlideAggregate for counts; never query inside loops; move slow work to async rules or events; cache repeated lookups. Check the slow script and transaction logs.
  3. How do events and notifications fit together? gs.eventQueue('x_acme.incident.escalated', current, parm1, parm2) queues an event; notifications and script actions react to it. Events keep business rules short and decouple side effects.
  4. What does a MID Server do? A Java service inside the customer's network that runs discovery, orchestration and integrations with systems the cloud instance can't reach directly. It connects outbound to the instance, so no inbound firewall holes are needed.
  5. What should a developer know about the CMDB? Configuration items live in cmdb_ci and its child classes, with relationships in cmdb_rel_ci. Write CIs through the Identification and Reconciliation Engine so duplicates are prevented, rather than inserting records directly.
  6. How do you test ServiceNow code? Automated Test Framework tests for forms, server scripts and catalog items, run before upgrades and in your pipeline, plus testing in a sub-production instance with realistic roles and data.
  7. What are skipped records after an upgrade? Baseline records you customised, which the upgrade doesn't overwrite. Review the skipped list after every upgrade and revert or merge. Extending (new records, scoped apps) instead of modifying baseline code keeps upgrades cheap.
  8. Which security mistakes come up? Treating client-side checks as security instead of enforcing ACLs on the server; client-callable script includes that use GlideRecord without access checks (GlideRecordSecure enforces ACLs); logging sensitive data; and unvalidated input in Scripted REST APIs.
  9. How is a Service Portal widget structured? An HTML template, a client controller, a server script that fills the data object, CSS and options. The server script runs first; the client reads c.data and calls c.server.update() to send changes back.

ServiceNow developer scenario and troubleshooting questions: 28–30

  1. A field value changes and nobody knows what changed it. Check the record's history and audit trail first, then business rules, flows, client scripts, data policies and integrations that touch that table and field. Session debugging for business rules and a code search for the field name usually find the culprit.
  2. A form takes eight seconds to load. Look for synchronous server calls in onLoad client scripts, heavy display business rules, many related lists or UI policies, and slow reference qualifiers, using the browser's timing details and the transaction log. Fix the slowest item first, then measure again.
  3. An update set shows errors on preview. Read each problem: a missing dependency (commit the parent set first or batch the sets), a collision with a newer change on the target (decide which version wins), or a record from another scope. Never accept or skip errors blindly.

How interviews test ServiceNow development

RoundWhat they askWhat a strong answer shows
ScreenClient vs server scripts, business rule types, update setsPicking the right tool for each requirement
Technical roundWrite a GlideRecord or GlideAggregate query, a client script with GlideAjaxCorrect API use and avoiding queries in loops
Scenario roundDebug a slow form or a mysterious field changeA method that starts with logs and history
Senior roundScoped app design, integrations, upgrade safety, CMDBChoosing configuration first and code only where needed

Candidates commonly report live scripting on a shared screen or a personal developer instance, often a business rule or a GlideAjax call. ServiceNow scripting is JavaScript, so brush up with JavaScript interview questions, and for integrations see REST API interview questions.

Where CoPilot Interview fits

CoPilot Interview is an AI interview assistant whose free AI mock interview builds ServiceNow development questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10, which is a quick way to find the answers above that you can't yet explain without notes. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. The browser demo at /try has 145 practice questions in 10 tracks with typed answers scored out of 10, no signup needed. Paid plans are Standard at $24.99 a month and Pro at $39.99 a month, and the desktop app runs on Windows 10 and 11 and macOS 12 or later. Technical screens, take-home tasks, online assessments and proctored tests usually forbid outside help, so prepare for those rather than use any tool during them; in any live interview, follow your employer's rules.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.

Frequently asked questions

What are the most common ServiceNow developer interview questions?

Business rule types, client scripts vs UI policies, GlideRecord and GlideAggregate, GlideAjax, ACL evaluation, update sets vs scoped apps, and how to debug a slow form.

What is the difference between a ServiceNow admin and developer interview?

Admin interviews focus on configuration: forms, lists, users, roles, notifications and catalog items. Developer interviews add scripting, integrations, scoped apps and performance, and usually include writing code.

How can I practise ServiceNow development?

ServiceNow offers free personal developer instances through its developer program. Build a small scoped app with a table, a business rule, a client script, an ACL and a REST endpoint, then break it and debug it.

Do I need ServiceNow certifications for a developer job?

They help with screening, and some partners require them, but interviews still test hands-on scripting. Be ready to explain an app or fix you built.

Practice this interview before the real one

The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.

Start a mock interview