ServiceNow Interview Experience for Software Engineer
Question Details
The process at ServiceNow consisted of 5 rounds: 1 Online Test, 3 Technical Rounds, 1 Manager Round.Online Test: It consisted of 1 Dynamic Programming problem.Find the Lon...
Full Details
The process at ServiceNow consisted of 5 rounds: 1 Online Test, 3 Technical Rounds, 1 Manager Round. Online Test: It consisted of 1 Dynamic Programming problem. Find the Longest Increasing subsequence in an array. (https://www.geeksforgeeks.org/dsa/longest-increasing-subsequence-dp-3/) After successful solution HR contacts you with further rounds.
Technical Round 1(60 minutes): 2 Coding problems based on the interviewer's mind or the difficulty of the problem he asks. Provided you with an online IDE, you've to share the screen and write the code and explain the logic you're going to use. Given 2 arrays of Train arrivals and departure. Find the minimum number of platforms required so that no train has to wait outside the platform. ( https://www.geeksforgeeks.org/dsa/minimum-number-platforms-required-railwaybus-station/ ) Largest sum contiguous subarray.
Technical Round 2(60 - 90 minutes): 2 Coding problems with intermediate difficulty. The Interview started with a breif discussion about the projects I've done in my previous company and a question was framed according to that. Provided you with an online IDE, you've to share the screen and write the code and explain the logic you're going to use. Given a set of Parent/Child job relations and find out the total runtime of the parent job. A -> B-> 40; B->C->20; A->NULL-> 10 X->Y->20; X->NULL->5; X->Z->10; Answer : A -> 70; X -> 35 Solution: A tree traversal approach given the relations you've traverse through all child nodes from a given parent and calculate the sum of all child process runtimes. Infix to Postfix ( https://www.geeksforgeeks.org/dsa/convert-infix-expression-to-postfix-expression/ )
Technical Round 3(60 - 90 minutes): The interview started with a normal introduction and went on with a detailed discussion on my projects on Github. Explained different logic of my projects on Github/Apps on Playstore. Discussion on different design patterns that I've used. Explained 5–6 design patterns in detail. Manager Round (120 minutes): 1 Coding question, Very detailed discussion on the projects and expectations from the job. How does my day look like with the previous employer? Given a N*N board with the Knight placed on any block of an empty board. Moving according to the rules of chess knight must visit each square exactly once. Print the order of each cell in which they are visited. ( https://www.geeksforgeeks.org/dsa/the-knights-tour-problem/ ) Had a very detailed discussion on the solution with different ways of solving the same problem and a better approach. Final
Verdict Accepted. Important Takeaways: Interviewers were mostly looking for the problem-solving approach and gave hints when required. If you get stuck into please ask them they will guide you to reach a solution.
About This Question
This is a reported interview question from a service now interview for a swe role during the oa round reported in 2025.
It covers the following topics: Arrays, Trees, Dynamic Programming, Oop .
Topics
More Service Now Interview Questions
About Service Now Interview Reports
This question was reported by a candidate who interviewed at Service Now. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Service Now are the higher-signal extractions to take from this report.
For broader preparation context, the Service Now interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Service Now reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Service Now Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Service Now reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.