Academic snapshot
Marks: 7.5+ CGPA / 75% (when listed)
Degree: B.Tech/B.E./M.Tech/MCA CS/IT/ECE/related
Year: Final year + recent grads (~1-2 years)
Backlogs: None active preferred
ServiceNow is a cloud workflow and IT service management platform company founded in 2004. Its Now Platform helps enterprises automate IT, employee, and customer workflows at scale. Growing India engineering hubs in Hyderabad and Bengaluru recruit campus graduates for platform, cloud, and application development roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
ServiceNow hires like a cloud platform company, not a mass IT services drill. The printed CGPA floor gets you into the funnel; the OA and workflow-design talk decide whether you see an offer.
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.5+ CGPA / 75% in 10th, 12th, graduation when listed | Higher GPA helps resume screen; OA still decides |
| Degree | B.Tech / B.E. / M.Tech / MCA in CS, IT, ECE, or related | Circuital branches appear when DSA is strong |
| Backlogs | None active at application / joining | Clear before offer paperwork |
| Experience | Freshers and ~0-2 years | Intern conversion also appears |
| Languages | Java, JavaScript, Python | One deep language for OA + interviews |
| Cities | Hyderabad, Bengaluru | Relocation questions are common |
Is 7.5 enough? It matches the commonly reported floor. A 7.6 with clean timed coding and a crisp ticket-workflow story beats an 9.0 that freezes on graphs. Treat CGPA as a gate, not a scoreboard.
Academic snapshot
Marks: 7.5+ CGPA / 75% (when listed)
Degree: B.Tech/B.E./M.Tech/MCA CS/IT/ECE/related
Year: Final year + recent grads (~1-2 years)
Backlogs: None active preferred
Skills bar
Primary filter: Medium DSA under time (+ aptitude on many OAs)
Interview differentiator: Cloud / workflow design
Languages: Java, JavaScript, Python
Hubs: Hyderabad, Bengaluru
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.
ServiceNow campus volume is selective. Many students enter through careers, referrals, or contests:
If your college does not have ServiceNow on the calendar, start a careers + contest + referral plan early.
You do not need a CSA certification to clear Round 2. You do need workflow vocabulary backed by diagrams:
Do this once a week for a month. Interviewers can tell the difference between someone who watched a platform overview video and someone who thought about workflow state machines.
| Theme | Why ServiceNow-like OAs use it | Cousin drills |
|---|---|---|
| DP | Optimization under constraints | Knapsack light, LIS, string DP |
| Graphs | Dependencies, routing | BFS/DFS, cycle detect, shortest path |
| Arrays / strings | OA stamina | Two pointers, sliding window |
| Trees | Hierarchical data | LCA, traversals |
| OOPs (some intern tests) | Subjective / design basics | Classes, inheritance, SOLID light |
After every mock miss, pull cousins from coding questions. Theme repetition beats random hard hopping.
ServiceNow product work is state-machine shaped. Interviewers use design prompts as a proxy for whether you can reason about SLAs, assignments, and multi-tenant data. You do not need staff-level distributed systems. You do need boxes, arrows, and failure modes.
Download 2026 Servicenow placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
ServiceNow does not publish a permanent official paper bank. Sets on this site are pattern trainers - not leaked live assessments. Full archive: previous year question papers.
| Round (typical) | What to practice |
|---|---|
| Online assessment | 90-min stamina on coding (+ aptitude when listed) |
| Technical 1 | Live DSA + cloud/CS fundamentals |
| Technical 2 | Workflow/SaaS design + project deep-dive |
| HR | Why ServiceNow?, relocation, goals |
ServiceNow hires through campus, careers portal, referrals, and contests. Campus volume clusters in placement season; contests and off-campus run more continuously.
Campus
Placement cell PPT → resumes → OA → virtual/onsite interviews.
Direct apply
ServiceNow Careers with resume. Resume screen then OA invite when roles are open.
Contests / referrals
Women Code to Win and referrals can shorten the queue; DSA bar remains.
Online Assessment - ~90 minutes (sometimes ~95)
| Section | Typical content | Focus |
|---|---|---|
| Coding | 2-3 medium-hard DSA | Arrays, DP, graphs, trees |
| Aptitude / CS (many invites) | MCQs | Quant light, logic, fundamentals |
| Extras (some intern tests) | OOPs subjectives / AI segment | Communication + basics |
Platform is often HackerRank. Languages: Java, JavaScript, Python. Large applicant pools (hundreds) appear in intern write-ups - accuracy matters.
Time boxing: finish sure coding first; do not burn 40 minutes on one DP if aptitude is also scored.
Technical Interview 1 - ~60 minutes
Live DSA plus cloud/CS fundamentals. Interviewers watch approach, code quality, and clarity. Roughly 40-50% of OA survivors advance in student reports.
Technical Interview 2 - ~60 minutes
System design (ticket workflows, SLA engines, notification buses, multi-tenant SaaS) and project deep-dive. About 50-60% of Round 1 survivors move on in many write-ups.
HR - ~30 minutes
Motivation, Why ServiceNow?, Hyderabad/Bengaluru logistics, compensation. Most candidates who reach HR with clean prior rounds receive offers if location and integrity checks pass.
| Phase | Duration | What happens |
|---|---|---|
| Application & screening | 3-5 days | Resume / contest shortlist |
| Online assessment | 1 day | Test + evaluation |
| Technical interviews | 5-7 days | Round 1 + Round 2 |
| HR | 1-2 days | Offer discussion |
| Result | 2-3 days | Offer letter / onboarding |
Total: often 2-3 weeks once active (some intern contest funnels move in under two weeks on calendar).
| Path | What changes | What stays hard |
|---|---|---|
| Campus | Batch OA windows | Medium DSA |
| Careers + referral | Resume visibility | Same OA/design bar |
| Women Code to Win | Faster invite | HackerRank DSA + technicals |
| ASE Intern dense OA | More sections (OOPs/AI) | Still need clean coding |
| Company vibe | Prep you can reuse | What to add for ServiceNow |
|---|---|---|
| Salesforce | SaaS design + DSA | ITSM/workflow + SLA talk |
| SAP | Enterprise data thinking | Ticket state machines |
| Microsoft | Medium DSA | Platform extensibility stories |
Download the 2026 PDF for offline timed runs.
Prefer specific workflow interest (“I like systems where SLA clocks and assignments create real user pain if wrong”) over generic “I love cloud.” Honesty about Hyderabad vs Bengaluru beats fake flexibility.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a ServiceNow invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for ServiceNow sits around ₹28-38 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, Python, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): ServiceNow eligibility for freshers 2026 (from student reports): typically 7.5+ CGPA / 75% in 10th, 12th, and graduation; B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related; final-year students and recent grads (within ~1-2 years); no active backlogs. ServiceNow does not publish one universal cutoff - verify on Careers or your campus JD.
What you are training for: Typical loop: Online Assessment (~90 min, coding + aptitude on many invites) → Technical 1 (cloud/DSA, ~60 min) → Technical 2 (system design + projects, ~60 min) → HR (~30 min). End-to-end often 2-3 weeks. Intern and Women Code to Win paths may alter invite timing but keep a similar skills bar.
Short version of the prep split: Split time roughly: DSA ~40%, cloud/platform + workflow design ~30%, aptitude warm-up ~15%, projects/behavioral ~15%. Drill medium DSA (DP/graphs show up often); practice ticket workflows, SLA engines, and multi-tenant SaaS sketches aloud.
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the ServiceNow previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most ServiceNow drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at ServiceNow usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why ServiceNow?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a ServiceNow-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the ServiceNow story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed ServiceNow papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many ServiceNow papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in ServiceNow-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed ServiceNow paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why ServiceNow. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For ServiceNow, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three ServiceNow mistakes, you are collecting content, not preparing.
Figures below are candidate-reported as of August 2026. Treat them as bands, not offer letters.
| Level | Experience | Total package | Notes |
|---|---|---|---|
| Software Engineer (strong fresher offers) | 0-1 years | ₹28-38 LPA | Confirm role level on JD |
| Broader SE/Analyst band (some tracks) | 0-1 years | ₹18-30 LPA | Title and team matter |
| With 2-3 YOE | 2-3 years | Often higher mid/senior bands | Ownership + design depth |
Health cover, learning budget, stock/bonus where offered, hybrid norms on many teams. Read the offer letter carefully - ServiceNow title differences move totals.
When Round 2 asks you to design a ticket system, they want:
Practice one 45-minute whiteboard. Speak in sentences. Name one metric (SLA breach rate). That is fresher-passing design at ServiceNow.
| Shared | ServiceNow-specific add-on |
|---|---|
| Medium DSA OA stamina | Ticket/SLA state machines |
| SaaS multi-tenant talk | ITSM vocabulary |
| Project defense | Why workflow platforms (not only CRM) |
One DSA error log, one design notebook, two Why-company stories.
Suppose your invite has 2 coding + an aptitude block:
Starving coding for aptitude (or the reverse) is a common self-own when both are scored.
Talk each for 10 minutes. Depth beats covering all eight once poorly.
Freshers often join platform or product squads where code review culture is strong. Expect:
Do not pretend you already know every Now Platform table in HR. Curiosity beats fake expertise.
Hiring shape 2026
Engineering hiring continues across platform and product teams in Hyderabad and Bengaluru.
Process notes
OA may mix coding + aptitude; intern tests can add OOPs/AI segments. Contest paths remain active.
Company context
Workflow automation and ITSM stay central. Confirm live openings on Careers before assuming campus volume.
Prep implication
Double down on timed DSA (DP/graphs) plus weekly workflow design - do not wait for a “new pattern” rumor.
Yes. Free ServiceNow placement papers PDF with previous-year style coding, DSA, and cloud/ITSM themes are on this site - no registration. Start with the 2026 PDF and year pages.
Typical loop: OA (~90 min, coding + aptitude on many invites) → Technical 1 (cloud/DSA) → Technical 2 (design + projects) → HR. End-to-end often 2-3 weeks.
About four core stages for many fresher SE tracks. Intern funnels may use denser online tests before 1:1s.
Often ~90-95 minutes with coding (2-3 medium-hard DSA; DP/graphs common). Aptitude/CS MCQs appear on many invites; some intern tests add OOPs subjectives or an AI interview segment.
A contest/hiring pathway that can shortlist into internship or early-career loops. It is an entry path, not a softer DSA bar.
Live DSA; cloud/CS fundamentals; workflow/SaaS design; project deep-dives; HR motivation. Narration and edge cases matter.
~60 minutes on workflow-shaped architecture: tickets, SLAs, notifications, multi-tenancy. Fresher depth - clear components and trade-offs.
From student reports: 7.5+ CGPA / 75% when listed; B.Tech/B.E./M.Tech/MCA in CS/IT/ECE/related; final-year or recent grads; no active backlogs. Verify your JD.
Java, JavaScript, or Python. Java appears often in ASE Intern notes. Pick one language you can debug live.
Active backlogs are the usual blocker. Cleared historical backlogs are generally fine if the notice does not say otherwise.
Candidate-reported: strong SE offers ~₹28-38 LPA; some tracks cite a broader ₹18-30 LPA band. Confirm written offers.
ServiceNow - workflow/ITSM platform. Salesforce - CRM cloud. SAP - enterprise ERP. Overlapping CTC chatter - choose on domain and city.
Hyderabad and Bengaluru are the main India hubs in student reports. HR will check relocation willingness - answer honestly.
Rough split: DSA 40%, cloud/workflow design 30%, aptitude 15%, projects/behavioral 15%. Weekly OA simulations + aloud design practice beat passive videos.
Practice DP/graph problems under time, keep aptitude warm without overdoing it, and rehearse one ticket-workflow design weekly. Research the platform enough for a real Why ServiceNow? answer.
No for most fresher OA clears. Platform certs help later conversations. Prioritize DSA + design first.
No. Many do, some coding-heavy invites do not. Always read your email. Keep light aptitude warm via the mock quiz either way.
Write-ups describe ~90-minute tests with aptitude/language MCQs, OOPs subjectives, DSA problems, and sometimes an AI interview segment - often with very large applicant pools. Advance rates can be steep; accuracy beats volume guessing.
An off-campus Summer Internship 2025 candidate entered via ServiceNow’s Women Code to Win contest (25 January), got a recruiter note on 5 February, and sat a HackerRank OA on 9 February: “It was a 95-minute test with three medium-to-hard DSA problems, primarily focused on Dynamic Programming and Graphs.” Technicals stacked on 13-14 February; the offer mail arrived 17 February (Medium).
A ServiceNow ASE Intern candidate (write-up updated December 2025) described Round 1 as a 90-minute online test spanning ~700 applicants: aptitude/language MCQs, three OOPs subjectives, two DSA problems, plus an AI interview segment (GeeksforGeeks). They wrote: “So the journey begin with an online test of around 700 candidates that was majorly on JAVA.” About 50 advanced; Round 2 (120 minutes) mixed graph/bitmask DSA, prompt engineering, and SQL before a final 45-minute resume+HackerRank 1:1.
Across reports, the same lessons repeat: DP/graphs show up, contest paths are real, and dense online tests reward calm time boxing. Decide Hyderabad/Bengaluru preference before HR - not during it.
| Day | Plan |
|---|---|
| 1 | DP + graph timed pair |
| 2 | Full OA mock matching invite (coding±aptitude) |
| 3 | Weak DSA themes only |
| 4 | Ticket/SLA design aloud + aptitude warm |
| 5 | Peer live coding + Why ServiceNow? |
| 6 | Light mock + project rehearsal |
| 7 | Sleep, documents, city decision |
Sudden drives reward calm time boxing. Contest shortlists can move fast - keep a “drive week” checklist ready before season peaks.
Students comparing ServiceNow with Salesforce and SAP should remember:
Negotiate with numbers from your letter, not from WhatsApp forwards.
| Dimension | Intern / ASE Intern | Full-time SE |
|---|---|---|
| OA density | Often more sections (OOPs, AI segment) | Often coding ± aptitude |
| Timeline | Can compress to ~2 weeks after contest | Often 2-3 weeks |
| Design depth | Still expected in later rounds | Standard Round 2 weight |
| Conversion talk | PPO expectations may appear | Direct offer discussion |
Prep the same DSA core. Add aptitude and OOPs subjectives if your invite is intern-shaped. Do not assume intern means “easy coding.”
When ~700 people sit one online test, small mistakes compound:
Calm process beats heroics. Simulate crowded-test nerves by mocking with a timer and phone in another room.
Weak: “It is a Fortune company with good package.”
Stronger: “I like building systems where ticket state and SLA clocks affect real employees.” I want to learn platform extensibility on problems that look simple until concurrency and tenancy show up.”
Write your version in your own words. Memorized LinkedIn lines are obvious.
If you clear HR:
Excitement is fine. Process discipline still matters at large product companies. Keep every email thread; verbal numbers are not offer letters.
Small process habits compound when applicant pools are huge. Keep calm, keep shipping clean answers, and protect sleep the night before every ServiceNow loop stage today.
Women Code to Win and similar contests can move from OA to offer in under two weeks. Keep resume, marksheets, and a Hyderabad/Bengaluru answer ready before you click register - not the night the recruiter emails you back today.