HR interview questions
Common ServiceNow HR questions, sample answer frames, and STAR tips.
ServiceNow Interview Experiences
How ServiceNow fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
ServiceNow placement process includes: 1. Online Assessment (90 minutes) - Coding/aptitude questions. 2. Technical Interview Round 1 (60 minutes) - Technical concepts. 3. Technical Interview Round 2 (60 minutes) - Advanced concepts and projects. 4. HR Interview (30 minutes) - Motivation and company fit. Total duration: 2-3 weeks from application to offer.
Eligibility (from student reports): 7.5+ CGPA or 75%.
Fresher package ballpark (from student reports): Analyst: ₹28-38 LPA. Confirm on your offer letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90-120 min | 2-3 coding problems (DSA) |
| Technical Round 1 | 45-60 min | DSA + detailed project discussion |
| Technical Round 2 | 45-60 min | DSA / system design basics |
| Hiring Manager / HR | 30-45 min | Behavioural + team fit |
Real interview experiences
Section titled “Real interview experiences”These are condensed from public candidate write-ups for the Associate Software Engineer role. Two calibrations worth making: the OA is short and MCQ-heavy (typically 15 MCQs plus a single coding question in 60 minutes, with a CGPA cutoff around 7.0), and the “HR” round is not HR - it is a hiring-manager round that includes real system design. No ITSM or platform-specific knowledge is expected from freshers.
Experience 1: Associate Software Engineer, on-campus (GeeksforGeeks write-up)
Section titled “Experience 1: Associate Software Engineer, on-campus (GeeksforGeeks write-up)”Round 1 - Online test (60 min, HackerRank)
- 15 MCQs plus one coding problem: count distinct pairs with a given sum.
Round 2 - Technical 1 (60 min)
- Debug a piece of C code - the bug was an unsigned integer loop that never terminated.
- Remove duplicates from an unsorted linked list, asked in three progressively constrained versions.
- Count substrings where each character appears exactly K times; the interviewer pushed through three successively better approaches.
- Project discussion.
Round 3 - Technical 2 (60 min)
- Letter combinations of a phone-keypad number.
- Lowest Common Ancestor, then re-asked for different tree structures.
- Deep dives on two projects.
Round 4 - Hiring manager (reported as long, ~90 min)
- Behavioural questions, plus a scenario problem about convincing 60 students to attend an event.
- Then technical again: database schemas, scaling strategies, system design fundamentals.
Outcome: Selected. The candidate’s advice was to ask for a hint when stuck - the interviewers were reported as supportive rather than adversarial.
Experience 2: Associate Software Engineer, on-campus 2022 (GeeksforGeeks write-up)
Section titled “Experience 2: Associate Software Engineer, on-campus 2022 (GeeksforGeeks write-up)”- Round 1 - Online test: 15 MCQs across DSA, DBMS and OS, plus the same “count distinct pairs with given sum” coding problem.
- Round 2 - Technical 1: introduction and projects, then three coding problems (palindrome variants and a binary tree traversal). Then XML, XSLT and XSD; SQL procedures, cursors and triggers; basic OOP.
- Round 3 - Technical 2: explain your project with architecture diagrams, then three more coding problems - an array search, a prime-number algorithm, and pattern matching - each followed by “now make it faster”.
- Round 4 - Hiring manager: resume walk-through, then design a LinkedIn-like platform end to end: functional requirements, bandwidth estimation, components, database schema, caching, scalability, security. Also multithreading and exception handling, plus career goals.
Outcome: Selected.
What both accounts share: three or four coding problems per round, each with an optimisation follow-up - volume and speed matter more than one hard problem. Be ready to sketch your project architecture, and do not walk into the final round assuming it is a formality; system design shows up there in both accounts.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Longest substring without repeating characters. Usually expects sliding window + hashmap
- Binary tree level order traversal. Usually expects BFS
- Detect cycle in a directed graph. Usually expects DFS colouring / topological sort
- Discussion on ITSM workflows and JavaScript, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why this company?
- A disagreement with a teammate and how you handled it
- An ownership example from a project
- Relocation preference
Practical tips for ServiceNow
Section titled “Practical tips for ServiceNow”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain ITSM workflows in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of ServiceNow panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, ServiceNow usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.