Motivation & Narrative Questions

These questions are one question

"Tell me about yourself", "why us", "why are you leaving", "proudest project", "where do you see yourself" — interviewers ask them separately, but they are all probing the same thing: does this person's career have a direction, and is this role actually on it? The preparation, therefore, is one artifact: a career narrative — a two-sentence account of where you have been, what you are good at, and what you are moving toward — that every individual answer draws from consistently.

Example narrative spine: "I've spent four years going deep on backend reliability — payments infrastructure, then on-call and incident tooling. I'm looking for a team where that reliability focus meets larger scale, and where I can grow into technical leadership." Every answer below is that spine wearing different clothes. Inconsistency is what kills candidates here — saying you love greenfield product work in one round and deep infrastructure in another reads as telling each interviewer what they want to hear.

"Tell me about yourself" — the 90-second version

This is usually the opener, and it sets the level the interviewer perceives before any technical signal exists. Structure it in three beats:

1. Present, framed as ownership (30s). "I'm a backend engineer at Acme, where I own our payments-retry service end to end — I designed it, shipped it, and run it in production. It processes about 2M transactions a day."
2. Selected past, not a chronology (30s). One or two prior chapters, chosen for relevance: "Before that I spent two years on the checkout team, where the thing I'm proudest of was cutting our incident rate roughly in half by rebuilding our alerting."
3. The bridge to this room (20s). "I'm looking for exactly the kind of scale problems this team works on, which is why I'm here."

What to avoid: starting from college, reciting the resume they are holding, or exceeding two minutes. Note the mid-level tells packed into the strong version: own, end to end, a number, and unprompted mention of running things in production.

"Why do you want to work here?"

The test is whether you did real homework or are mass-applying. Generic praise ("great culture, smart people, exciting products") scores zero because it fits every company. A strong answer is specific and two-sided — something concrete about them, connected to something true about you:

"Two reasons. First, the problem: your feed infrastructure handles a scale of fan-out I've only read about, and my last two years have been exactly this kind of latency-versus-freshness problem at smaller scale — I want to do it at yours. Second, I've read your engineering blog's postmortems; a company that publishes its failures publicly is one I'd trust to have a real engineering culture."

Preparation is 30 minutes: the engineering blog, the product itself (use it), recent launches, and the values page. One specific, true observation beats five generic ones.

"Why are you leaving your current company?"

The iron rule: run toward, not away — and never badmouth the employer you are leaving. Complaints about your manager, team, or company read as risk (you may describe them this way in two years) regardless of how justified they are.

Every reframe above can be true — you are choosing the forward-facing half of the truth. Keep it to two or three sentences and pivot to why this role is the direction you are running toward. If you were laid off, say so plainly and without drama; in 2025–2026 it carries no stigma, and spin is riskier than candor.

"What project are you most proud of?"

This is a behavioral question in disguise — answer it with story-bank discipline, not nostalgia. Pick the story that best shows mid-level scope: a feature or service you owned end to end, and make your specific contribution unmistakable, because the follow-up will be "what exactly was your part?". Include the result number and, ideally, why it was hard: "I'm proudest of the retry service because it was ambiguous — no one could tell me what 'done' meant, so I defined it, shipped it, and it cut failed payments 35%."

Choose pride honestly but strategically: a modest project you drove alone usually beats a famous project you touched lightly.

"Where do you want to be in a few years?"

The interviewer is checking that the role feeds your trajectory — retention risk assessment, in plain terms. The safe, honest, strong shape for a mid-level candidate: deeper mastery plus emerging leadership, in this domain.

"In a few years I want to be operating at a senior level — owning the technical direction for a service area, and being the person who mentors engineers through their first big designs. This role is the right next step because it hands me bigger-scale versions of the problems I already love."

Avoid the two failure modes: "I have no idea" (no direction) and answers that leave engineering or this company's orbit ("I want to found a startup", "move into product management") — honest as they may be, they answer the retention question in the wrong direction.

Your questions for them

When they ask "any questions for me?", "no" reads as low interest. Prepare two or three that show product and team curiosity and that you cannot answer from the website: "What does the team's on-call actually look like in a bad week?", "What separates the mid-level engineers here who reach senior quickly from those who don't?", "What's the most contested technical decision on the team right now?" The last five minutes are still the interview — and the answers are genuinely useful for your own decision, which is what makes the questions sound real. They are real.