Tell me about yourself as a senior software engineer

Senior is a scope claim. The minute should show judgment and a result, not a longer list of tickets.

Build your answer

Target role The job you are interviewing for. Years of experience Years in this kind of work. Use 0 for a first role or a career change. Current role or background A field, a path, or a short phrase.

Win 1 Include a number. Win 2 Optional. Win 3 Used in the long version.

Key strength One habit, not five adjectives. Why this company or role A reason that would be wrong for a different employer.

Runs in your browser. Nothing you type is uploaded.

30-second version

About 38 seconds · 94 words

A short cut for a recruiter screen.

Stop after one result. A short screen does not need the second story.

60-second version

About 61 seconds · 152 words

The default. Present, then past, then future.

If they lean in, drop the second result and spend the time on how the first one happened. Leave duties from the job description out.

90-second version

About 90 seconds · 224 words

A longer cut when they ask you to walk through it.

I'm looking for a senior software engineer role. For the past 9 years I've worked as a senior backend engineer on a growth team. Before that, this is the work that got me here. One result was chose a cache over an early shard and cut p95 read latency from 800ms to 190ms. Another result was set the review bar for a 6-engineer project that shipped without a rollback. A later result was took weekend pages from 11 a month to 2 by deleting a noisy dependency. None of that is a title. It is the work I can walk through. The through-line is making the tradeoff explicit before the team writes the code. The future I'm aiming at is a senior software engineer role, because this role owns ambiguous product bets, which is the work I want more of. The first thing I'd measure is the constraint the team already feels. The numbers in those results are ones I can defend, including what I owned. The senior software engineer role is the move, and the results are how I know I can do the work. I can say any of those results more slowly, with the owner and the number intact. The work I want next is still senior software engineer work: a clear owner, a number, and a decision I can explain.

They can interrupt. Go present, then proof, then why this role. When they ask, go from the headline number to the decision you made.

When you can say the minute without the page, practice it live with Luna. It hears the question and helps you keep a line. 24 hours free.

How to answer it for this role

A senior answer names the blast radius. You set an approach others used, you made a call under incomplete data, or you took a system from fragile to dull. Years alone do not make the case. Plenty of people have eight years of similar tickets.

Talk about one hard tradeoff. "We could shard now or buy a quarter by caching the hot path. I argued for the cache, shipped it in three weeks, and the shard happened the next half with real traffic data." That is senior. A tour of every system you have touched is not.

Include people only if you changed their output. Mentoring counts when someone else's design or on-call load moved. "I like mentoring" does not. The future beat should match a senior loop: ambiguous problems, cross-team work, or raising the bar on reviews.

What to emphasize

Scope: what got worse if you were wrong.
A decision, not only an implementation.
The next job's ambiguity, in their words.

What to leave out

A promotion narrative ("I was promoted twice").
Speaking only in "we" with no owned decision.

Sample 60-second answer

This is the sample loaded into the builder above. About 61 seconds, 152 words. Replace every fact with yours before you practice it.

I'm looking for a senior software engineer role. For the past 9 years I've worked as a senior backend engineer on a growth team. Before that, this is the work that got me here. One result was chose a cache over an early shard and cut p95 read latency from 800ms to 190ms. Another result was set the review bar for a 6-engineer project that shipped without a rollback. The through-line is making the tradeoff explicit before the team writes the code. The future I'm aiming at is a senior software engineer role, because this role owns ambiguous product bets, which is the work I want more of. In the job I'd bring that strength to the team's current goal, and I'd report what moved. I have the detail under each number, including what I would measure again. That is the minute: the senior software engineer work, the proof, and the reason.

The 30-second cut is about 38 seconds. The longer cut is about 90 seconds. Both use the same facts in the same order. Read the longer structure guide if you want the timing rules in full: how long the answer should be.

Tips before you say it

Say the 60-second version out loud before you edit it. A sentence that looks fine on the page often runs long or sounds like a memo.
One number per win. “Improved the process” is a claim. “Cut hold time from 6 minutes to 2” is a result you can be questioned on.
Stay in order: present, past, future. If you start with where you grew up, the interviewer is waiting for you to arrive.
Leave a door open and then stop talking. The extra story you add in the silence is usually the one you did not prepare.
Keep your part separate from the team’s. “We launched” collapses the first follow-up. “I cut the scope, engineering shipped it” survives.

Other roles

Questions people ask

Should I say I am ready for staff?

Only if you are interviewing for staff. For a senior loop, claim senior scope cleanly. Reaching for the next title in the opener makes the level conversation awkward before they have evidence.

How many projects fit in a minute?

Two. A third belongs in the 90-second version. Senior candidates lose the room by stacking four systems and finishing none of them.

Do I mention the team size?

Yes, if you coordinated people who did not report to you. "Six engineers across two teams" is scope. It is not a substitute for the result.