The question taxonomy, "tell me about yourself" and "why us"

There are hundreds of behavioral question phrasings and roughly a dozen underlying questions. Learning the mapping turns an unbounded preparation problem into a bounded one.

This lesson starts with that mapping, then prepares the two questions in it that are answered from your career rather than from a single story: "tell me about yourself" and "why this company". You will be asked both in almost every loop, so they are worth preparing more tightly than anything else.

The twelve

How to use the mapping

When you hear a question you have not prepared, classify it before you answer. Two seconds of silence to place the question is invisible; ninety seconds of the wrong story is not.

Question: "Tell me about a time you had to work with a team that had different priorities from yours."

Classification: This is 6 (disagree and stay trusted), possibly with a 4 (ship under constraint) component. It is not 3 or 12.

Response: the conflict story, told with the delivery pressure kept in the stakes.

Getting the classification wrong is a common and quiet failure. A candidate who answers a conflict question with an initiative story has produced no evidence for the competency being scored, and the interviewer often will not correct them.

Where the twelve map in this course

Questions 3–12 correspond to the nine competency sections:

Questions 1 and 2 are handled in the rest of this lesson, because they are answered from your career rather than from a story.

"Tell me about yourself"

The most frequently asked question in any loop and the one most worth scripting. It is asked by interviewers who have no other behavioral questions, which means it is often the only behavioral evidence a technical round produces.

What it is actually for

Three things, none of which is your biography:

1. Level calibration. The interviewer is placing you on a ladder in the first ninety seconds.
2. Direction of travel. Are you moving toward this role or away from your last one?
3. A menu. A well-built answer plants two or three hooks the interviewer can follow, which means you have partially chosen the questions you will be asked.

The arc

Two minutes, four parts:

Notice it starts with now, not with university. Reverse chronology, same as a resume, for the same reason: the most relevant evidence goes where attention is highest.

A worked answer

Devi, invented, interviewing for a senior backend role at a payments company:

"Right now I'm a backend engineer at Kestrel Systems, which does B2B logistics — I own the routing service, about 12 million requests a day, and I'm the main on-call for it along with three others.

I started out in data engineering, building batch pipelines, and moved to backend about four years ago because I wanted to work on things where latency mattered and you got feedback in seconds rather than in a nightly run. Kestrel was the second of those moves — I went there specifically because they were about to rebuild routing and I wanted to own a system rather than contribute to one.

The piece of work I'd point to is the reconciliation cutover we did earlier this year. Our nightly settlement job took six hours forty, which meant month-end close had slipped to day four and merchants were escalating. I profiled it, found most of the time in one join, and — the harder part — I got finance to agree to move a report out of the critical path, which meant talking directly to the controller rather than through my manager. We got it to fifty-five minutes and close moved to day one.

That work is why I'm here, honestly. The part I enjoyed most was the money-correctness side, and that's the whole job in payments rather than a quarter of it."

Two minutes. Three hooks planted: routing at scale, the reconciliation cutover, and the finance conversation. If the interviewer follows any of them, they have walked into a story that is already prepared.

What to leave out

• Education, unless you are within about two years of graduating.
• A complete job list. Two or three moves. Gaps in the sequence are fine and rarely asked about at this point.
• Personal life. One clause is fine if it is genuinely load-bearing ("I moved to Berlin in 2025"). A paragraph is not.
• Anything negative about a current employer. Frame moves as toward something.

"Why this company, why this role, why now"

The second career question has a simpler test. An answer that could be pasted into another company's interview scores zero. That is the whole test.

The three sub-questions

They are usually asked as one and should be answered as three short pieces.

Why this company — what specifically about this organisation, that is not true of five others. Why this role — why this scope and this problem, given what you have done. Why now — why you are moving at all, framed toward something rather than away.

The copy-paste test

Write your answer, then substitute a competitor's name. If it still reads correctly, it is worth nothing.

"I'm really impressed by the engineering culture and the scale of the problems you're solving, and I think it'd be a great place to grow."

Substitutes cleanly into any company in the industry. Interviewers hear a version of this several times a week.

What specificity actually looks like

Three sources, in increasing order of value:

Public technical material. An engineering blog post, a conference talk, an open-source repository. Cite the specific thing and what you thought about it:

"I read your write-up on moving the ledger to an append-only model, and the part that stuck with me was the decision to keep the mutable balance as a projection rather than removing it. We made the opposite call at Kestrel and paid for it in reconciliation complexity — which is the problem I spent six months on this year."

The product, used. Sign up. Use it. Find something real:

"I set up a test merchant account last week. The thing I noticed is that the payout schedule is configurable per-merchant, which is exactly the flexibility that made our reconciliation hard — so I'm assuming you have solved something we did not."

Conversations. With the recruiter, with the hiring manager, with anyone who works there:

"When I spoke to Ren, they said the team's biggest problem this year is that the settlement pipeline can't be reasoned about end to end. That is the specific thing I've been doing."

Why now — framing the move

The honest answer is often "I'm bored" or "I want more money" or "my manager left". None of those is disqualifying, and all of them need reframing toward what you are moving to.

The rule: true, forward-facing, and short. Do not construct a fiction, because the story has to survive the rest of the loop, and do not spend two minutes on a grievance.