Autocoder

ServiceNow Interview Questions and Answers

Last updated 2026-11-19

ServiceNow builds a cloud platform for IT, employee and customer workflows, so its software engineering interviews commonly combine data structure problems with practical design questions about tickets, workflows and APIs. This page offers practice questions on those themes, with worked answers.

They are practice questions on commonly reported topics, not real papers. For the process, see how to crack the ServiceNow interview, and for timed problems see ServiceNow coding round questions.

Reported roundsOnline assessment, 1-2 technical interviews, behavioural round
Reported platformHackerRank (some reports)
Sourced hiring factPlans to expand Hyderabad teams in 2026 (January 2026 report)

Rounds as commonly reported

Candidate reports cited by this site's ServiceNow process notes describe an online assessment (HackerRank in some reports) with two DSA questions and MCQs on aptitude, DBMS and SQL, then one or two technical interviews with live DSA coding, CS fundamentals and a resume and project walkthrough, and finally a behavioural or HR round. For experienced candidates, REST API design is also reported. This is not an official description.

Topics to revise

Arrays, strings, trees and graphs; SQL joins and aggregation; DBMS normalisation, indexing and transactions; OOP and design basics; REST API design; and clear explanations of your projects.

Hiring status

ServiceNow has a ServiceNow hiring page on this site. The sourced fact: in January 2026, ServiceNow said it plans to expand its Hyderabad teams in 2026, focusing on AI-skilled software engineers, ML specialists, research scientists and forward-deployed engineers, and that over 45 percent of its global product engineering and over 20 percent of its workforce is in India, with Hyderabad its largest engineering site. No numbers of openings or dates are sourced. Check careers.servicenow.com for current roles.

ServiceNow Interview Questions and Answers: questions with worked answers

  1. 1

    Design a ticketing system (incident management) with SLAs.

    hard

    Entities: Ticket (id, requester, assignee, priority, status, timestamps), Comment, Team and SLA policy. Model status as a state machine (New, In Progress, On Hold, Resolved, Closed) with allowed transitions enforced in one place. An SLA policy maps priority to a response and resolution deadline; store the due time when the ticket is created or priority changes and pause the clock during On Hold. A scheduler scans an index on due time to raise breach warnings. Keep an audit table of every change. Search by status and assignee needs composite indexes.

  2. 2

    Model a ticket lifecycle as a state machine in code.

    medium

    Define the allowed transitions as a dictionary from state to the set of next states, and make every status change go through one function that validates, records history and triggers side effects. This avoids invalid jumps such as Closed back to New and keeps business rules in one place.

    python
    ALLOWED = {
        'NEW': {'IN_PROGRESS', 'CLOSED'},
        'IN_PROGRESS': {'ON_HOLD', 'RESOLVED'},
        'ON_HOLD': {'IN_PROGRESS'},
        'RESOLVED': {'CLOSED', 'IN_PROGRESS'},
        'CLOSED': set(),
    }
    
    class Ticket:
        def __init__(self):
            self.status, self.history = 'NEW', []
        def move(self, new):
            if new not in ALLOWED[self.status]:
                raise ValueError(f'{self.status} -> {new} not allowed')
            self.history.append((self.status, new))
            self.status = new
  3. 3

    Detect circular dependencies among configuration items.

    medium

    Treat items as nodes of a directed graph with an edge from an item to what it depends on. Run DFS with visiting and visited states, and report a cycle when an edge reaches a node currently in the visiting state. O(V + E). The same check decides whether a valid deployment order exists via topological sorting.

    python
    def find_cycle(graph):
        state, path = {}, []
        def dfs(u):
            state[u] = 1
            path.append(u)
            for v in graph.get(u, []):
                if state.get(v) == 1:
                    return path[path.index(v):] + [v]
                if v not in state:
                    found = dfs(v)
                    if found:
                        return found
            state[u] = 2
            path.pop()
            return None
        for node in graph:
            if node not in state:
                found = dfs(node)
                if found:
                    return found
        return None
  4. 4

    Write SQL to list open tickets that breached their due time, with the assignee name.

    medium

    Join tickets to users, filter on open statuses and due time earlier than now, and order by how overdue they are. Using a LEFT JOIN keeps unassigned tickets visible. An index on (status, due_at) makes the filter efficient.

    sql
    SELECT t.id, t.priority, u.name AS assignee,
           CURRENT_TIMESTAMP - t.due_at AS overdue_by
    FROM tickets t
    LEFT JOIN users u ON u.id = t.assignee_id
    WHERE t.status NOT IN ('RESOLVED', 'CLOSED')
      AND t.due_at < CURRENT_TIMESTAMP
    ORDER BY t.due_at;
  5. 5

    Explain normalisation and indexes using the ticket table as an example.

    easy

    Keep requester and assignee in a users table and refer to them by id, so a name change is made once (third normal form). Index columns used in filters and joins: status plus due time for queues, assignee id for "my tickets". An index on a column with few distinct values, like a boolean, is rarely useful. Every index adds write cost, so index to match real queries.

  6. 6

    How do you design a REST API for tickets?

    medium

    Use nouns and standard verbs: GET /tickets with filters and cursor pagination, POST /tickets (returns 201 and Location), GET /tickets/{id}, PATCH /tickets/{id} for partial updates, and POST /tickets/{id}/comments. Validate input and return 422 with field errors. Make creation idempotent with an Idempotency-Key header. Use optimistic concurrency through ETag and If-Match so two agents cannot silently overwrite each other. Authenticate with OAuth tokens and authorise per team.

  7. 7

    What is the contract between equals and hashCode in Java?

    easy

    If two objects are equal by equals, they must return the same hashCode; unequal objects may share a hash but fewer collisions are better. Breaking the contract makes HashMap and HashSet lose entries, since lookups look in the wrong bucket. Override both together, use the same fields, and avoid mutable fields in keys.

  8. 8

    Design an event-driven workflow engine (when a ticket changes, run rules).

    hard

    Publish a change event to a queue whenever a ticket is saved. Rule workers subscribe, load the rules for that event type, evaluate conditions and run actions such as assigning, notifying or calling a webhook. Make actions idempotent, bound rule recursion (an action that triggers another event) with a depth counter, and store each execution with its outcome for debugging. Isolate slow customer scripts with timeouts.

  9. 9

    Compare write-through, write-back and cache-aside caching.

    medium

    Cache-aside: the application reads the cache, on a miss loads from the database and fills the cache; simple and common, with stale data possible after writes unless invalidated. Write-through writes to the cache and database together, giving consistency at the cost of write latency. Write-back writes to the cache first and flushes later, which is fast but risks data loss on failure.

  10. 10

    What is a deadlock in a database and how is it handled?

    medium

    Two transactions each hold a lock the other needs and wait forever. Databases detect cycles in the wait-for graph and abort one transaction as the victim, which the application must retry. Reduce deadlocks by locking rows in a consistent order, keeping transactions short, and avoiding user interaction inside a transaction.

  11. 11

    Tell me about a time you had to learn something quickly.

    easy

    Describe the situation (a new framework for a project), your plan (documentation, a small prototype, asking a mentor), how you checked your understanding (code review, tests) and the outcome. Mention how you shared what you learned with the team afterwards.

  12. 12

    Why ServiceNow?

    easy

    Link it to the work: workflow platforms used by large organisations, engineering at scale, and the growing role of AI in automation. Mention something you read or used and a skill you want to grow. Avoid repeating the careers page.

Frequently asked questions

Do I need to know the ServiceNow platform?

For general software engineering roles, interviews are reported to focus on DSA and CS fundamentals. Platform-specific roles may differ, so read your job description.

Is SQL tested?

MCQs on DBMS and SQL are reported in the online assessment by some candidates, so revise joins and aggregation.

How many interview rounds are there?

Reports describe one or two technical rounds and a behavioural round, but this is not official.

Where do I find current openings?

On ServiceNow hiring on this site and the company's own careers site.

Sources

Related guides

More in Company Interview Questions

See all in this section