“Walk me through a project you're proud of — what was your role and the impact?”
ProbingOwnership and truth-testing: can you separate what YOU did from what the team did, explain choices, and state a real outcome without inflating it?
“Why did you choose this stack? What would you change now?”
ProbingEngineering judgment and honesty — whether decisions were reasoned or default, and whether you've grown enough to critique your own work.
“Tell me about the hardest bug you've debugged.”
ProbingMethod under ambiguity: hypothesis → isolate → verify. Interviewers listen for a system, not luck ('turns out it was a typo' with no process is a red flag).
“How would you design a URL shortener / rate limiter / notification service?”
ProbingStructured thinking at whiteboard scale — clarify requirements first, name trade-offs, size the data. Depth expectations scale with your seniority.
“Explain a time you disagreed with a teammate or senior. What happened?”
ProbingConflict maturity — did you argue the problem or the person, did you commit after the decision, and can you tell it without villainising anyone?
“What happens when you type a URL into a browser?”
ProbingFundamentals breadth — DNS, TCP/TLS, HTTP, rendering. They're probing where your depth stops, and whether you know that you know.
“Why do you want to leave your current role? / Why us?”
ProbingMotivation screen — growth-seeking reads well; grievance-dumping doesn't. For freshers: whether you researched the company at all.
“Do you have questions for us?”
ProbingGenuine engagement. 'What does a strong first 90 days look like?' signals seriousness; 'no questions' ends the interview on a shrug.