Skip to content

Question bank

What it asks, and what a useful answer contains.

These are starting questions. In the room the next one depends on what you just said.

Two people talking across a table during an interview

Opening

  • Tell me about yourself, focused on this role.

    All tracks

    A short arc, not a biography. Role first, then one proof.

  • Why this role, and why now?

    All tracks

    A reason tied to work you have already done.

Projects

  • Walk me through one project end to end.

    Student

    Sequence: problem, your part, what shipped, what you would redo.

  • What was your exact contribution versus the team's?

    Student

    A boundary. 'We' is fine only after 'I' is clear.

  • Defend one design decision against an alternative.

    Student

    A real alternative, and the cost of the one you picked.

Fundamentals

  • Explain a technical concept from your resume in simple words.

    Student

    Plain language. Jargon without an example is a miss.

  • What is an API, as you would explain it to a new teammate?

    Student

    A contract between two sides, with one concrete example.

Debugging

  • Describe a bug that took you embarrassingly long to find.

    Engineering

    The wrong hypothesis, then the clue that changed it.

  • A user reports an issue you cannot reproduce. What next?

    Engineering

    How you narrow it: environment, steps, logs, not a guess.

Judgment

  • Talk about a tradeoff between shipping fast and doing it properly.

    Engineering

    What you deferred, and the check that would tell you to stop.

  • Where do you put validation, and what broke when you got it wrong?

    Engineering

    One layer you own, and a failure you actually saw.

Craft

  • How do you review someone else's code?

    Engineering

    What you read first, and how you write a comment a person can act on.

Coding

  • Design a rate limiter. Start with requirements, not code.

    Engineering

    Who is limited, over what window, and what the caller sees when blocked.

  • Make this check-in idempotent. Talk before you type.

    Engineering

    A client key, a stored result, and the double-click case.

Behavioral

  • Tell me about a disagreement with a teammate and how it ended.

    General

    The disagreement, your move, and the outcome. Not a moral.

  • Describe a time you missed a deadline. What did you tell people?

    General

    When you said it, and what you changed the next time.

Motivation

  • Why this company and this role, specifically?

    General

    A detail from the job post, not a compliment about the brand.

  • Connect your previous work to this role in two minutes.

    General

    A skill that transfers, with one story that proves it.

Screening

  • What would your last manager say you need to improve?

    General

    A real gap, and the evidence you are working on it.

Closing

  • What questions do you have for me?

    All tracks

    A question about the work, not the perks.

How the company rooms open

One first question from each loop. The follow-ups depend on your answer.

  • Meta-style room

    “Tell me about something you shipped fast with incomplete information.”

    Answer this live
  • Google-style room

    “Design a URL shortener. Start with requirements, not code.”

    Answer this live
  • Amazon-style room

    “Tell me about a time you took on work outside your role.”

    Answer this live
  • Microsoft-style room

    “Tell me about feedback that changed how you work.”

    Answer this live
  • MongoDB-style room

    “Explain a tradeoff you made for the developer using your work.”

    Answer this live
  • Walmart-style room

    “Tell me about a process you simplified to save time or cost.”

    Answer this live
  • Flipkart-style room

    “Tell me about a high-traffic moment you handled. What broke first?”

    Answer this live
  • Razorpay-style room

    “A merchant's payments fail at peak hour. Walk me through your response.”

    Answer this live
  • Apple-style room

    “Tell me about something you polished until the details mattered.”

    Answer this live
  • Netflix-style room

    “Describe a high-stakes call you made with incomplete data.”

    Answer this live
  • Uber-style room

    “How do you ship fast without breaking trust on the other side?”

    Answer this live
  • Stripe-style room

    “Explain a failure mode your API had and how you surfaced it.”

    Answer this live
  • Adobe-style room

    “Walk me through feedback that changed a feature you cared about.”

    Answer this live
  • Oracle-style room

    “Tell me about a production issue where rollback was the right move.”

    Answer this live
  • Atlassian-style room

    “How do you write work so another team can pick it up?”

    Answer this live
  • Swiggy-style room

    “What broke first during a spike, and what did you do in the first ten minutes?”

    Answer this live
  • Zomato-style room

    “A restaurant partner is furious at peak hour. Walk me through your response.”

    Answer this live
  • PhonePe-style room

    “A UPI failure spikes at checkout. What do you check first?”

    Answer this live
  • CRED-style room

    “Tell me about a detail users noticed that most teams would skip.”

    Answer this live
  • Infosys-style room

    “Explain a concept from your training project to a non-technical client.”

    Answer this live
  • TCS-style room

    “Walk me through your final-year project and your exact contribution.”

    Answer this live

Company-style rooms. Practice inspired by public interview loops. Not affiliated with or endorsed by these companies.