Service Now On Campus-FTE-August 2019
Question Details
Online test:The were 10 MCQs on computer science concepts (data structures, Java, c++) and one coding question on DP which is https://www.geeksforgeeks.org/dsa/longest-inc...
Full Details
Online test: The were 10 MCQs on computer science concepts (data structures, Java, c++) and one coding question on DP which is https://www.geeksforgeeks.org/dsa/longest-increasing-subsequence-dp-3/ 21 students were shortlisted for further rounds.
Technical round 1: The interviewer asked to introduce myself. He then asked me my favourite subject. I said data structures. He asked me which data structure I was comfortable with. I said linked list and trees. Then he asked if I was interested in any other subjects. I said I have average knowledge on OS and DBMS. He started with a question on trees https://www.geeksforgeeks.org/dsa/print-left-view-binary-tree/ I told him level order traversal approach and he said to code it. I did. He asked if I was good at solving puzzles. I said I wasn't that good. He told me to try https://www.geeksforgeeks.org/aptitude/puzzle-22-maximum-chocolates/ . I said. He asked me explain a project on automation which I mentioned in my resume. He gave another question on trees https://www.geeksforgeeks.org/dsa/lowest-common-ancestor-binary-tree-set-1/ and said to write the code.(I did it) He gave another puzzle https://www.geeksforgeeks.org/aptitude/puzzle-24-10-coins-puzzle/ . I couldn't solve it. I said I had no idea. He said that's fine and said me to leave. The interviewer was so polite.
Technical round 2: The interviewer said we will directly go to problems. I said ok. He gave a question on linked list and said to write the code. https://www.geeksforgeeks.org/dsa/remove-occurrences-duplicates-sorted-linked-list/ . I took time(about 20 min) but did it finally. Since there was less time he said I will give you another problem and I want you to solve it in 10min. https://www.geeksforgeeks.org/dsa/majority-element/ . I said I had been through this problem while preparation. He asked me if I knew the O(n) time and O(1)
space complexity solution. I said yes. He told me to write the code quickly. Then he asked me about encapsulation and abstraction. I told him the definitions. He said what I was saying is all bookish, tell me by taking an object in this room as an example. I told him by taking water bottle as an example. I was confused with the concepts so he explained me and said me to leave. Technical +
HR The HR asked random questions. First he gave an SQL query which was, Find the second largest salary from a given table. I said an approach using LIMIT. He said it was an interesting way to do it, but can I do it without using LIMIT. I told him the approach but couldn't write the query. He asked about projects on my resume. Told me to explain Interface for an 8th class student. I couldn't explain it well. He asked me how huge data is stored in databases. I said Distributed DBMS. He asked me if I knew sharding. I said no. He then asked me how data was processed in apps like hotstar when it has high number of viewers like during the worldcup match. I said work load balancing algorithms will be used. I wrote CSS as my technical skill, so he asked me what is it. I said Cascading style sheets. He asked me why was it named cascading. I couldn't answer so he explained. He asked me if I had any questions for him and told me to leave. 10 students were left after all the rounds and 4 students were selected. Unfortunately I wasn't one of them but it was a good interview experience. TIPS: Solve all must do coding questions from geeks for geeks. Be through will your resume. Confidence was all what the HR was looking for. So be confident while you answer the questions.
Topics
More from Service Now
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.