Software Engineering Interview

Most Indian companies run an HR screen, one or two hiring-manager or technical rounds and a final HR discussion on expectations, spread over days. ExamPilot compresses the loop into one 17-minute panel (HR → hiring manager → role/technical lead → behavioural → closing) or a 12-minute one-on-one with the hiring manager. Rounds are pass/fail in real life; here you get a scored report on role knowledge, problem solving, communication and attitude, with STAR feedback on every behavioural answer.

1. 1

   Ownership

   Walk me through the last feature you shipped to production, from the ticket to the release. What exactly did you write yourself?

   What a strong answer covers

   A clear arc: the problem, the design you chose, the code you personally wrote, how it was tested and rolled out, and one number after release such as latency or adoption. Separate your work from the team's. Avoid narrating the whole sprint without ever saying what you owned.

2. 2

   Debugging

   A user-facing API that normally responds in 200 milliseconds is now taking four seconds since this morning's deploy. How do you find the cause?

   What a strong answer covers

   A calm sequence: check dashboards and error rates, compare with the deploy diff, look at slow-query logs, traces and downstream dependencies, decide whether to roll back first, then root-cause. Mention communicating status to stakeholders. Avoid guessing a single cause before gathering any evidence.

3. 3

   Fundamentals

   Our order page recalculates a customer's lifetime spend by scanning every past order on each load, and it is slow for loyal customers. How would you fix it, and what does your fix cost?

   What a strong answer covers

   Name the current cost as linear in order count, then propose a database index with aggregation, a precomputed running total updated on each order, or a cache with invalidation. Compare consistency, write cost and memory for each. Avoid jumping straight to adding Redis without explaining staleness or what happens on refunds.

4. 4

   System design

   Design a URL shortener for a campaign that a large Indian bank will send by SMS to two crore customers on one morning.

   What a strong answer covers

   Clarify scale and read-to-write ratio, then cover key generation, storage choice, a cache for hot links, redirect latency, rate limiting and analytics. Discuss the morning spike and what fails first. Avoid listing buzzwords like microservices and Kafka without explaining why each is needed.

5. 5

   Engineering practice

   How do you decide what to test in a pull request, and what do you do when a reviewer says your tests are not enough?

   What a strong answer covers

   Explain the testing pyramid in practice: unit tests for logic, integration tests for boundaries, and a few end-to-end checks for critical flows, guided by risk. Show you treat review comments as useful, ask clarifying questions and add tests. Avoid sounding defensive or treating coverage percentage as the goal.

6. 6

   Behavioural

   Recall a design argument with a senior engineer where you thought they were wrong. How did you make your case, and how did it end?

   What a strong answer covers

   A STAR story: the decision, your reasoning with data or a prototype, how you raised it respectfully, the outcome, and what you learned even if you lost the argument. Show you committed once a decision was made. Avoid making the senior sound foolish or claiming you were simply right.

7. 7

   Failure

   Which bug of yours reached real users, and what did the post-mortem change in how your team ships code?

   What a strong answer covers

   Honest ownership: what broke, how it was detected, the immediate fix, the blameless root-cause analysis and the lasting change such as a test, alert or checklist. Show the impact in users or minutes. Avoid picking a trivial bug or quietly blaming the QA team or the process.

8. 8

   Motivation

   You are switching from a service company to a product role here. What will be different for you, and what gaps are you closing?

   What a strong answer covers

   Specific differences: owning a product end to end, faster release cycles, on-call, writing design docs and talking to product managers. Name one concrete gap and how you are closing it, such as a side project or course. Avoid running down your current employer or sounding as if only salary drives the switch.

9. 9

   Closing

   What is your current CTC, your expected CTC, your notice period, and can you relocate to Bengaluru or Pune if needed?

   What a strong answer covers

   Give accurate figures, a reasoned expected range based on role and market, the real notice period and whether buyout is possible, and a clear answer on relocation with any genuine constraint. Avoid inflating your current CTC or promising an early joining date you cannot actually deliver.

• English
• Hinglish (Hindi + English)Hinglish