ServiceNow | SSE | Hyderabad | May 2024

servicenow logo
servicenow
Senior Software EngineerHyderabadRejected
June 13, 20243 reads

Summary

I interviewed for a Senior Software Engineer position at ServiceNow, successfully clearing four rounds of interviews. Despite receiving positive feedback throughout the process, I was ultimately rejected with a generic email.

Full Experience

My journey began with an introductory call from a recruiter who discussed my background, previous experience, the role's details, and compensation expectations. After confirming alignment, they informed me that another HR representative would assist with scheduling.

Approximately 10 days later, my first technical round was scheduled:

Problem Solving Round

This round focused heavily on problem-solving skills and the rationale behind choosing specific algorithms. The interviewer was less interested in perfectly working code and more in my thought process and a draft solution. I was presented with two coding challenges and one behavioral question:

Miscellaneous Round with Staff Engineer

Immediately after clearing the first round, HR contacted me to schedule the next round, which happened two days later. This round with a Staff Engineer touched upon a wide range of topics, with the interviewer emphasizing that he was evaluating my problem-solving approach rather than just the final solution. We discussed a coding problem, its extensions, and several system design and conceptual questions:

Miscellaneous Round with EM

After a week, HR informed me I had cleared the Staff Engineer round and scheduled the next round for the very next day. This round was with an Engineering Manager (not the hiring manager) and focused on my previous work experience, a deep dive into one of my past projects, and some Object-Oriented Programming (OOPs) concepts.

Techno-Behavioral Round with HM

Two days later, HR called again to confirm I had cleared all three technical rounds, and the final round with the Hiring Manager was scheduled for the following day. This round involved extensive discussions about my previous work, expectations from the company and the role, and ensuring mutual alignment. I was also asked a system design question:

All my rounds proceeded well, and I consistently received positive feedback. However, despite this, I eventually received a generic rejection email, which felt similar to a rejection during the resume screening phase. I've observed this pattern with other candidates too, which I believe is an inefficient use of time and resources for both candidates and the company, potentially impacting the company's reputation.

Interview Questions (11)

Q1
Next Greater Element II
Data Structures & AlgorithmsMedium

Given a circular integer array nums, return the next greater number for every element in nums. The next greater number of a number x is the first greater number to its traversing clockwise next in the array. If no next greater number exists, output -1 for this number.

Q2
Evaluate Balanced Parentheses String
Data Structures & AlgorithmsMedium

Given a string s consisting of only open and closed parentheses '(', ')', evaluate its score based on the following rules:

  • () has a score of 1.
  • AB has a score of A + B, where A and B are balanced parentheses strings.
  • (A) has a score of 2 * A, where A is a balanced parentheses string.

Q3
Anti-Engineering Experience
Behavioral

Describe a time when you engaged in 'anti-engineering' practices and explain your rationale for doing so.

Q4
Find Unique Element in Sorted Duplicated Array
Data Structures & AlgorithmsMedium

Given an array where all elements appear twice and are placed next to each other, except for one single element which is not repeated. Find that unique element. Example: [1,1,2,2,4,4,5,6,6] output 5.

Q5
Define Fault Tolerance
System Design

What is fault tolerance?

Q6
Define Transactions
System Design

What is a transaction?

Q7
Transactions in Distributed Systems
System Design

Explain transactions in a distributed system context.

Q8
Inter-service Communication (Payment & Order)
System DesignHard

Describe how a payment service and an order service can communicate and update their respective values during the process of an order creation.

Q9
Low-Level Design: Cab Booking System (Pricing)
System DesignHard

Perform a Low-Level Design (LLD) for a Cab Booking system, specifically focusing on implementing the pricing mechanism with simple assumptions.

Q10
REST API Best Practices
System Design

What are the best practices for creating a new REST API?

Q11
Data Model: Aarogya Setu App
System DesignMedium

Design a data model for the Aarogya Setu application.

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!