ServiceNow | Senior Software Engineer | IC3

servicenow logo
servicenow
· Senior Software Engineer | IC3
February 1, 2026 · 28 reads

Summary

I shared my interview experience for a Senior Software Engineer | IC3 role at ServiceNow, detailing rounds focused on DSA, LLD, HLD, and a Hiring Manager discussion. I successfully navigated all stages and received an offer.

Full Experience

Hey everyone, sharing my experience to give back posts from this community genuinely helped me during prep 🙌

🟢 Round 1 (R1) – DSA Question Types: Disjoint Set (Union-Find) based problem Interval-based problem (merging / scheduling style) Verdict: ✅ Passed

🟡 Round 2 (R2) – DSA + LLD Mix This round felt like problem solving wrapped inside a design discussion. Edge cases around overlaps and ordering Efficient use of sorting + greedy logic LLD-style Part: Designed an Attendance Management System Entities, APIs, and data flow discussion Handling scenarios like multiple check-ins, late entries, etc. More emphasis on logic correctness than heavy OOP theory Verdict: ✅ Passed

🔵 Round 3 (R3) – HLD (System Design) Focus: Designing a scalable backend service which interacts with LIVE running applications. APIs, databases, and scaling strategy Handling failures & bottlenecks Discussing design trade-offs Verdict: ✅ Passed

🟣 Round 4 (Hiring Manager)

Focus: Past project experience Ownership & decision-making Team fit and communication No deep DSA/LLD/HLD grilling here Verdict: 👍 Went well

Final Verdit - Selected

Comp Details - https://leetcode.com/discuss/post/7537147/offer-evaluation-microsoft-l61-serviceno-8tbc/

Interview Questions (3)

1.

Disjoint Set (Union-Find) Problem

Data Structures & Algorithms

A problem based on the Disjoint Set (Union-Find) data structure.

2.

Interval Merging/Scheduling Problem

Data Structures & Algorithms

An interval-based problem, likely involving merging or scheduling scenarios.

3.

Design an Attendance Management System

System Design

Designed an Attendance Management System. The discussion covered entities, APIs, data flow, and handling specific scenarios such as multiple check-ins and late entries. Emphasis was placed on logic correctness rather than extensive OOP theory.

Preparation Tips

Posts from this community genuinely helped me during prep.

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

Be the first to share your thoughts and start the discussion!