servicenow logo
ServiceNow· Staff Software Engineer

ServiceNow Staff Software Engineer Interview experience

Posted
9 Feb 2026
496 reads

Summary

I experienced a multi-round interview process for a Staff Software Engineer position at ServiceNow, which included coding, low-level design, and high-level design challenges across four distinct rounds.

How it went

Round 1

Text Justification

Round 2

(LLD) Design a Loan Management System where customers can take loan and see the monthly EMI for the entire loan period (including days beyond current date). The customers can pay advance amounts as well which will change the EMI for the upcoming period that should be reflected in the upcoming monthly sheets.

Follow Up:

  • All DB tables to store loans and calculate EMIs
  • What if the interest rate changed midway through loan ? What changes will be made in the tables and LLD to accomodate that ?
  • What other improvements can be done on the entire system?

Round 3

(Bonus Problem Solving round since second round had mixed feedback)

Round 4

(HLD) Design an Incident Management system which can be shipped to external Clients (ex: Amazon type e-commerece site)

Requirements:

  • CRUD on incidents
  • All DB tables, indexes, query patterns
  • How will the incident be routed to the right team ? The team information is not available while creating the incident. The expectation is to define a PROCESS/SYSTEM through which the right team can be found and the incident can be assigned to them.

Questions asked (5)

  1. 01

    Text Justification

    Data Structures & Algorithms

    The problem can be found at the provided LeetCode link.

    Open the problem
  2. 02

    Design Loan Management System (LLD)

    System Design

    Design a Loan Management System where customers can take loan and see the monthly EMI for the entire loan period (including days beyond current date). The customers can pay advance amounts as well which will change the EMI for the upcoming period that should be reflected in the upcoming monthly sheets.

    Follow Up:

    • All DB tables to store loans and calculate EMIs
    • What if the interest rate changed midway through loan ? What changes will be made in the tables and LLD to accomodate that ?
    • What other improvements can be done on the entire system?
  3. 03

    Jump Game II

    Data Structures & Algorithms

    The problem can be found at the provided LeetCode link.

    Open the problem
  4. 04

    Minimum Window Subsequence

    Data Structures & Algorithms

    The problem can be found at the provided LeetCode link.

    Open the problem
  5. 05

    Design Incident Management System (HLD)

    System Design

    Design an Incident Management system which can be shipped to external Clients (ex: Amazon type e-commerece site)

    Requirements:

    • CRUD on incidents
    • All DB tables, indexes, query patterns
    • How will the incident be routed to the right team ? The team information is not available while creating the incident. The expectation is to define a PROCESS/SYSTEM through which the right team can be found and the incident can be assigned to them.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at ServiceNow recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!