Interview experience
ServiceNow interview experiences covering Online assessment, Technical interview(s), HR interview. Round-wise notes, common questions, and what candidates report clears each stage.
Explore: Interview experience · HR interview questions · Overview · Placement papers · Preparation guide
ServiceNow runs a leaner fresher loop than most enterprise-software peers - often just 2-3 rounds - but candidates consistently report the coding bar running harder than the overall “chill” tone would suggest, with JavaScript fundamentals weighted more heavily since the whole Glide platform is built on JS.
Interview experience
ServiceNow interview experiences covering Online assessment, Technical interview(s), HR interview. Round-wise notes, common questions, and what candidates report clears each stage.
HR interview questions
ServiceNow HR interview questions with sample answer frameworks - motivation, relocation, STAR stories, and culture-fit prompts.
| Round | Duration | What they test |
|---|---|---|
| Online assessment | 60-90 min | Coding + aptitude |
| Technical interview(s) | 45-60 min each | DSA, JavaScript fundamentals, OS/networking |
| HR interview | 30 min | Motivation, fit |
These answers are compiled from public candidate reports, not from an official ServiceNow notice, and drives differ by campus, role and year. The instruction screen of your own test is the final word.
| Question | Answer |
|---|---|
| Which platform is it on? | HackerRank. Campus and off-campus reports from 2024 to 2026 name it consistently. |
| How many questions and how long? | Two formats are reported. A 60-minute screen with about 15 MCQs (DSA, DBMS, OS) plus one coding problem, or a 90-minute set of 2-3 medium DSA problems. A March 2026 Hyderabad test had two coding problems (one medium, one hard), a hard SQL query, two MCQs and a prompt-writing task. |
| Is there a prompt-engineering question? | In recent drives, yes. 2026 reports from Hyderabad and a Bengaluru campus drive both describe a prompt-writing question alongside the coding problems. |
| Does it have negative marking? | No public candidate report mentions negative marking, and ServiceNow does not publish a marking scheme. Coding is scored on hidden test cases. |
| Is there a sectional cutoff? | Not published. Reports say some drives advance candidates who fully solve two of three coding problems. |
| How much is the cutoff? | No test cutoff is published; shortlists are relative to the batch. Campus eligibility is typically around 7.5+ CGPA or 75%, varying by drive. |
| Is there coding, and which languages? | Yes, 1-3 DSA problems on arrays, hash maps, intervals, trees and sliding window, plus SQL in some tests. HackerRank’s usual languages are allowed; JavaScript comfort helps in later rounds. |
| Do I need ServiceNow platform knowledge? | No, not for software-engineering roles. Platform (Glide) questions appear in platform-developer, support and consulting roles. |
These themes come from candidate reports on Glassdoor for ServiceNow’s Hyderabad and Bengaluru offices. They show the level and style, not a fixed list.
| Role | Reported questions and topics |
|---|---|
| Associate Software Engineer (fresher) | Tree traversals and matrix problems (2025 Hyderabad); implement a linked list and find the kth smallest node in a BST (February 2026); a third round on backend concepts; a hiring-manager round on OOP after three DSA rounds on arrays, trees and DP. |
| SDE intern | Basic CS questions plus one coding problem, then a medium round with fundamentals and two coding problems (February 2024); Gas Station (LeetCode) in a DSA-only round that the candidate found harder than expected (late 2024). |
| Software engineer (experienced) | Operations on two matrices, flattening a nested object, debouncing in JavaScript and where you would use it, and designing an LRU cache with a doubly linked list in the hiring-manager round. |
| Quality engineer | Describe an automation framework you have built, how you handled test data and how you ran tests in parallel (June 2025 Hyderabad). |
| Platform / support roles | ServiceNow platform knowledge, JavaScript, troubleshooting and customer-handling scenarios (2025 report). |
Asked across every role: complexity and optimisation follow-ups on every coding answer, a walk through your project’s architecture, and why ServiceNow.
A timed coding and aptitude test that screens candidates before any live interview. Candidates report the questions skewing harder than a typical fresher OA. Recent 2025–2026 campus and off-campus write-ups describe either a 60-minute HackerRank screen (often 15 MCQs across DSA, DBMS, and OS plus one coding problem, e.g. distinct pairs with a given sum) or a longer 90-minute set with 2–3 medium DSA problems (intervals, trees, sliding window). Treat partial credit seriously: some drives advance candidates who fully solve two of three OA problems.
Common questions
One to three live technical rounds are common in 2025–2026 reports - not always the minimal 2-round fresher loop. A typical pattern is ~80% DSA (often two problems per round with complexity and optimisation follow-ups) plus resume and project depth (schema design, scaling a side project, cloud/SQL vs NoSQL). Round three or the hiring-manager stage may add OOP, puzzles reduced to binary search, or light system design (e.g. a social or e-commerce schema), so do not assume the final conversation is HR-only.
Common questions
this binding, async/await, prototypal inheritance (sometimes a dedicated segment after DSA)Full round-by-round narratives are on the ServiceNow interview experience page.
A closing conversation on motivation, fit, and logistics.
Common questions
Sample answer frameworks for each of these are on the ServiceNow HR interview questions page.
ServiceNow’s core platform (workflow automation, ITSM, GlideRecord scripting) is built on JavaScript, so even general fresher software-engineering interviews probe JS fundamentals - closures, async behavior, prototypes - more deeply than a typical Java/C++-centric enterprise interview. You don’t need prior Glide/ServiceNow-platform experience as a fresher, but solid JavaScript beyond syntax basics is worth more here than at most companies on this list.
“ServiceNow developer” and “ServiceNow admin” jobs at partners and IT services firms are about configuring the ServiceNow platform for clients: GlideRecord scripting, business rules, client scripts, flows and ITSM modules. Those interviews test platform knowledge and certifications such as Certified System Administrator.
This page covers engineering jobs at ServiceNow itself (Associate Software Engineer, Software Engineer, interns) in Hyderabad and Bengaluru. That loop is a HackerRank test, DSA-heavy technical rounds with JavaScript, OS and networking questions, and an HR or hiring-manager close. Platform experience is not required, though the JavaScript depth overlaps with what platform developers use.
A closure is a function bundled with a reference to the lexical environment where it was created, so it keeps access to those outer variables after the outer function has returned. For example, function counter() has a local let n = 0 and returns function() with n = n + 1 and returning n; each call to counter() produces an independent counter whose n cannot be touched from outside. Closures are how JavaScript expresses private state, memoisation caches, and once-only initialisation. The classic bug is capturing a loop variable declared with var, which shares one binding across all iterations - switching to let creates a fresh binding per iteration and fixes it.
For a normal function, this is decided at call time by how the function is invoked: as a method it is the object before the dot, as a plain call it is undefined in strict mode and the global object otherwise, with new it is the freshly created object, and with call, apply, or bind it is whatever you pass. Arrow functions have no this of their own - they capture it lexically from the enclosing scope, which is why arrows are the right choice for callbacks inside a method and the wrong choice for object methods themselves. The common interview trap is passing obj.method as a callback, which loses the receiver; obj.method.bind(obj) or an arrow wrapper preserves it.
JavaScript runs one call stack; when it is empty the event loop drains the microtask queue completely, then takes one macrotask (a timer or I/O callback) and repeats. Promise callbacks are microtasks, so a resolved promise’s then runs before a setTimeout with zero delay that was scheduled earlier. async/await is syntax over promises: an async function returns a promise, and await suspends the function and resumes it in a microtask when the awaited promise settles. Because microtasks starve macrotasks, an infinite chain of promise resolutions will block timers and rendering entirely.
Every JavaScript object has an internal link to a prototype object; when a property is not found on the object itself, the engine walks that prototype chain until it hits null. A constructor function’s prototype property becomes the prototype of objects created with new, which is why methods defined on Foo.prototype are shared by every instance rather than copied per object. The ES6 class keyword is syntactic sugar over exactly this mechanism - class methods land on the prototype and extends sets the prototype chain - it does not introduce classical classes. This matters at ServiceNow because Glide server-side scripting has historically used prototype-based object definitions rather than class syntax.
Use a sliding window with a map from character to its last seen index. Move the right pointer across the string; when you meet a character already inside the window, jump the left pointer to one past that character’s stored index rather than moving it one step at a time. Update the answer as right minus left plus one at every step, and record the current index in the map. This is O(n) time with one pass and O(k) space where k is the alphabet size, which is the answer interviewers want after you dismiss the O(n squared) substring check.
The seven layers from bottom up are Physical, Data Link, Network, Transport, Session, Presentation, and Application. Physical moves bits over a medium, Data Link frames them and does MAC addressing and error detection, Network handles IP addressing and routing, and Transport handles end-to-end delivery - TCP for ordered reliable byte streams, UDP for unreliable datagrams. Session manages dialogue setup, Presentation deals with encoding and encryption, and Application holds protocols like HTTP, DNS, and SMTP. Practical TCP/IP stacks collapse the top three layers into a single application layer, so HTTP is described as application layer over TCP at the transport layer.
HTTPS is HTTP carried inside a TLS session, so the request line, headers, cookies, and body are encrypted, while plain HTTP sends all of that in cleartext. TLS gives three properties: confidentiality through symmetric encryption, integrity through a message authentication code, and server authentication through an X.509 certificate signed by a trusted CA, which is what stops an attacker impersonating the host. The handshake exchanges supported cipher suites, validates the certificate, and agrees a session key - in TLS 1.3 that costs a single round trip, or zero with session resumption. Note that HTTPS still leaks the destination IP and, unless encrypted client hello is used, the hostname via SNI.
A process owns its own virtual address space, file descriptor table, and heap; a thread is a schedulable unit inside a process that shares that address space and heap but keeps its own stack, registers, and program counter. Creating a thread is far cheaper than forking a process and switching between threads of the same process avoids a page-table swap, which is why servers use thread pools. The cost is that shared mutable state needs synchronisation - without a mutex you get race conditions and torn reads. A crash or memory corruption in one thread takes the whole process down, whereas separate processes give isolation at the price of IPC overhead.
No public candidate report mentions negative marking, and ServiceNow does not publish a marking scheme. The test is on HackerRank and is mostly coding scored on hidden test cases, sometimes with a few MCQs on DSA, DBMS and OS, a SQL query and, in 2026 drives, a prompt-writing question.
It is a HackerRank test, either about 60 minutes with around 15 MCQs and one coding problem, or 90 minutes with 2-3 medium DSA problems. A March 2026 Hyderabad test had two coding problems, a hard SQL query, two MCQs and a prompt-writing task. Fully solving two of three problems has been enough in some drives.
ServiceNow’s process for freshers is leaner than most product companies - often just 2-3 rounds: an online assessment/coding round (60-90 min), one or two technical interviews (45-60 min each) covering DSA, OS/networking fundamentals, and JavaScript, and a closing HR interview (30 min). Candidates have reported the coding questions running noticeably harder than a typical fresher screen, even when the overall interview felt low-pressure.
Expect JavaScript fundamentals (closures, async behavior, prototypes), DSA coding problems, and OS/networking basics - process/kernel concepts, file systems, the OSI model, and HTTP vs HTTPS have come up in recent loops. Because ServiceNow’s platform (Glide, GlideRecord) is built on JavaScript, strong JS fundamentals matter more here than at a typical enterprise-software company, even for roles that don’t require prior ServiceNow platform experience.
Typically 2-3 for freshers: an online coding/aptitude round, one or two technical interviews, and an HR round. Experienced-hire loops for ServiceNow-platform roles (developers, admins) can add a dedicated round on GlideRecord, business rules, and ITSM/ITOM workflow concepts.
Get comfortable with JavaScript beyond the basics - closures, scope, async patterns - since it underlies ServiceNow’s Glide scripting layer. Practise DSA under time pressure (candidates report the coding bar being higher than expected for a fresher round), and brush up OS/networking fundamentals like the OSI model and HTTP/HTTPS. If you’re applying to a platform-specific role, learn GlideRecord query basics.
No - most fresher software-engineering interviews at ServiceNow test general CS fundamentals (DSA, JavaScript, OS/networking), not the ServiceNow platform itself. Platform knowledge (GlideRecord, business rules, ITSM workflows) becomes relevant mainly for roles explicitly built around ServiceNow development or administration, or once you’re on the job.
Fresher analyst/SDE packages at ServiceNow India have been reported in the high-20s to high-30s LPA range in recent cycles, with a typical eligibility bar around 7.5+ CGPA or 75% - both vary by role and drive, so confirm on your specific offer letter.
Associate Software Engineer loops are often shorter than big-tech but coding can run harder than the “chill” reputation suggests. Interviewers score:
Soft fail modes: ignoring JS while grinding only C++ LeetCode, or speed-over-correctness stories that scare enterprise panels.
Good fit: You enjoy medium DSA (especially DP/graphs), can explain a multi-step ticket workflow without jargon soup, and have one project you can defend for 20 minutes. Comfort with Hyderabad or Bengaluru relocation helps.
Harder path: You only practiced service-company aptitude; you skip system design because “freshers don’t get design”; you cannot explain your project’s data model. Some OAs also include aptitude - ignoring both sides fails for different reasons.
Use this as a default four-week loop before a ServiceNow drive. Adjust to your invite timeline.
10-day crash version: Days 1-4 timed DSA, days 5-7 resume projects + CS fundamentals, days 8-9 mock interviews out loud, day 10 HR STAR stories on the HR page.
Candidate-reported fresher/early-career packages for ServiceNow often cite ₹28-38 LPA for strong SE fresher offers. Treat forum numbers as ranges, not guarantees - confirm the written offer letter for your team and location.
Interview process details and sample questions on this site are editorially organized from public candidate reports and hiring write-ups, with round structure, prep notes, and company-specific framing added by our team. For round-by-round stories, see the ServiceNow interview experience page. For OA papers and coding drills, use ServiceNow on placementpapers.app. OA quick answers and role-wise questions draw on Glassdoor candidate reviews for ServiceNow’s Hyderabad and Bengaluru offices (2024-2026), including associate software engineer, SDE intern and quality engineer reports.
Guides often searched alongside this page: Salesforce interview questions · Oracle interview questions · SAP interview questions · Microsoft interview questions · Atlassian interview questions · Adobe interview questions.