Service Now Interview Experience for Associate Software Engineer (On-Campus)
Question Details
ServiceNow visited our campus in august for the role of Associate Software Engineer.
Round 1 The first round was an online Hackerrank test which had a duration of 60 minut...
Full Details
ServiceNow visited our campus in august for the role of Associate Software Engineer.
Round 1 The first round was an online Hackerrank test which had a duration of 60 minutes. It consisted of 1 Coding question and 15 MCQs that consisted of questions from topics like OS, DBMS, Algorithms, etc. The coding question was exactly like this one. https://leetcode.com/problems/maximal-square/solution/ High efficiency in MCQs was required to clear the test.
Round 2 Technical Interview 1 This round lasted for an hour. The interviewer was friendly and he started off by giving his introduction. Then he gave me 3 DSA problems which I had to code in Notepad. The problems were as follows: https://www.geeksforgeeks.org/dsa/find-common-elements-three-sorted-arrays/ https://www.geeksforgeeks.org/dsa/print-right-view-binary-tree-2/ https://leetcode.com/problems/copy-list-with-random-pointer/ I was able to solve the first 2 problems without any help from the interviewer. The interviewer gave me some hints on 3rd problem. For all the problems interviewer asked me to give an efficient solution in terms of time as well as space complexity.
Round 3 Technical Interview 2 This interview was started with a general introduction followed by a little discussion on my past interns and projects. First, he asked me how would I design databases for a e-commerce websites like amazon. Then he followed up with 2 DSA problems. The questions are as follows : https://leetcode.com/problems/non-overlapping-intervals/ The second problem was related to a bitwise operation which was similar to Ugly numbers. I was able to solve the first question completely whereas gave the worst-case solution for the second problem.
Round 4 Hiring Manager Round This was the Technical +
HR round which lasted about 45 minutes. The interviewer asked something from every project which I mentioned in my resume. He then tested my OOP concepts by asking some standard OOPs questions. Post this I was given a puzzle that was reduced to a binary search problem. After this he asked me basic HR questions like strengths, weakness, favorite team with which you have worked till now, why ServiceNow?.
Round 5 Hiring Manager Round This was another Technical +
HR round which lasted about 30 minutes. For the first 15 minutes, the interviewer and I had a simple chat on where do I live, my achievements, his achievements. After this, he gave me a DSA problem. It was a simple DFS problem with a minute change in it. I was able to code it in 10 minutes by covering all the edge cases.
Verdict Selected The interviewers were friendly and helped me whenever I was stuck. Tips : Be clear whenever you are giving any answer. Don't hesitate if you can't solve the problem, ask for hints and try to follow that. Ask for feedback/things where you went wrong in the interview.
About This Question
This is a reported interview question from a service now interview for a swe role (junior level) during the oa round reported in 2025.
It covers the following topics: Oop, Trees, Bit Manipulation, Binary Tree, Binary Search, Graph, Graphs, Arrays .
Difficulty rating: Easy
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.