A typical ServiceNow interview question sounds like this: users complain that approval requests sit untouched for days. What would you check, and what would you change? The interviewer wants a working method, not a list of features. Practise answering in the form of investigation first, then solution, then verification.
Answering a scenario well
- Start with questions: who is affected, when did it start, and which records show the delay.
- Check the obvious causes first, such as approval rules pointing at the wrong group or notifications going nowhere.
- Propose a fix at the right level: a configuration change before a script, and a script before a custom build.
- End with how you would confirm the fix worked, such as checking approval times over the next week.
Fundamentals interviewers check first
Before the scenarios, most interviews test whether the basics are solid. Rehearse short, plain answers to these — one or two sentences each, not lectures.
- What is ServiceNow, in one sentence? A cloud platform for running IT and business workflows — incidents, requests, approvals and changes — on shared tables instead of scattered spreadsheets and inboxes.
- Table, record, field. A table is a collection of similar records (for example, incidents); a record is one row; a field is one column on that row. If you can explain this cleanly, half the follow-ups get easier.
- Client script vs business rule. A client script runs in the browser, for things like hiding a field or checking a value before submit. A business rule runs on the server, for things that must hold no matter how the record was created — including imports and integrations.
- UI policy vs data policy. A UI policy changes what a user sees on a form; a data policy enforces rules on the data itself, even when the form is bypassed.
- What is GlideRecord? The server-side way to query and update records in code. Know when you would use it instead of a simple configuration — and when you would not need code at all.
- Access control rules (ACLs). Who can read, write, create or delete a record, and under what conditions. Mention that ACLs are checked after business rules, and that a missing ACL is a common reason a user cannot see a field.
- Flow Designer vs Workflow. Flow Designer is the current no-code way to automate multi-step processes; Workflow is the older engine. For a new build, Flow Designer is the usual answer.
- Import sets and transform maps. Data lands in a staging table (the import set) and a transform map decides how it becomes real records. Say this when asked how external data gets into the platform safely.
Scenario questions to practise
These are the questions that separate memorised answers from real understanding. For each one, practise the investigation-first method above out loud before you read the pointers.
1. Approval requests sit untouched for days
Ask who is affected and whether it started after a change. Check whether approvals point at the right group, whether the group has active members, and whether notifications are actually reaching them. Fix at the configuration level first — a wrong group or a broken notification — before writing any script. Confirm by watching approval times over the following week.
2. A form takes far too long to load
Look for the expensive parts first: too many related lists, heavy client scripts, or reference fields pulling large tables. The strong answer separates what the browser does from what the server does, and removes or defers the expensive piece instead of adding more code on top.
3. Duplicate incidents keep getting created
Ask how duplicates are recognised today — matching on caller, short description, or configuration item — and what happens when a match is found. A good answer covers both prevention (deduplication rules, better categorisation) and cleanup (merging duplicates into a parent incident).
4. An integration stops syncing records
Check in order: is the connection up, are credentials valid, is data arriving in the import set, and is the transform map failing on specific rows? Saying "check the import set first" marks you as someone who has actually debugged one.
5. A report's numbers do not match what managers expect
Do not rebuild the report first. Check the filter: which table, which conditions, which date range, and whether archived or cancelled records are included. Most report mismatches are filter mismatches, not platform bugs.
6. A user cannot see a field their colleague can see
Work through the layers: UI policy hiding it, an ACL blocking read access, or a different role on the two users. Name the layers in order instead of guessing one cause.
A one-week practice plan
- Days 1–2: write one-sentence answers to every fundamentals question above, then say them out loud until they sound natural.
- Days 3–5: take one scenario a day and answer it in the investigation–solution–verification shape, timed at under two minutes.
- Days 6–7: run a mock interview — our AI Interview Coach can throw follow-ups at you — and note every question that made you pause. Those are your revision list.
Clear structure beats long answers every time. Interviewers remember the candidate who diagnosed the problem before prescribing the fix.