Behavioral & Interview Skills

Tests whether you can compress your value into one memorable claim under a time limit. Lead with your current role and one narrow specialty, back it with a single concrete proof point, and close with what you want next.

Tests ownership and whether you can make technical work legible fast. Pick one project, set context in about thirty seconds, say what you personally decided and why, land a measured result, and leave room for drill-down.

An outcome bullet names the measure, the value before your work, the value after, and what you did to move it. A duty bullet names only the responsibility, so nothing in it can be verified.

Tests whether your career reads as a trajectory rather than a list. Narrate roughly three minutes chronologically, give a reason for every move, weight the recent roles heaviest, and land on why this job is the next step.

Probes whether your reason for leaving would recur here and whether you can describe a disappointment without blame. Give one clean, forward-looking reason, credit what the role gave you, and say what you are moving toward.

STAR has four beats: Situation sets the context, Task states what you personally owned, Action describes what you did about it, and Result reports what changed. All four are mandatory, and Action carries the evidence being graded.

CARL ends on Learning: after Context, Action and Result you say what the experience changed in how you work. STAR stops at the Result, so it omits the reflection that failure and growth prompts are actually asking for.

A story that stops after the actions gives no evidence they worked, so it reads as effort rather than achievement. The final beat must state what changed because of you, in past tense, plus one line of reflection.

A headline-first opening is one sentence stating what you did and how it ended, said before any background, so the listener knows the point of the story even if they hear nothing else.

Use 'we' only for shared context — the team, the system, the goal that was genuinely collective — and 'I' for every decision, action and tradeoff you personally owned. An interviewer can only score what one named person did.

Probes whether you can be direct without making it personal. Strong answers label severity first, state the objection as a question with the reason attached, cite a shared standard rather than taste, and quote one comment you actually wrote.

Tests whether criticism of your code lands as criticism of you. Answer with one blunt comment, what you did to understand it before replying, the change you made, and the working relationship afterwards.

Tests whether bad news travels fast and arrives with a plan. Answer with the moment you knew, how quickly you said it, what you offered alongside the slip, and the revised date you then held.

Probes conflict resolution and self-awareness. Describe one person in observable behaviours, the charitable read you tested, the direct conversation you had, what you changed yourself, and a work outcome with the relationship still standing.

Tests whether you can be wrong without defending it. Name a real call you got wrong, how you found out, what you said and to whom, and the guardrail that came out of it.

Tests whether you can argue hard and then execute without hedging. Give one decision you lost, show where you voiced the objection while it was still open, then what committing actually looked like in your work.

Tests whether you can say a hard thing kindly and precisely. Name one observable behavior and its impact, show you said it privately and soon after, and end with evidence the behavior actually changed.

Leadership scope widens by rung. A mid-level engineer leads a task and its execution, a senior leads a project and the coordination inside it, and a staff engineer multiplies two or three teams over a much longer horizon.

Probes candour and judgement about where dissent belongs. Answer with one real disagreement, evidence rather than opinion, raised privately first, a decision that actually got made, and you committing to it afterwards.

Tests whether you can own a decision process across team boundaries, not just hold a strong opinion. Answer with the options you framed, the criteria everyone accepted, who decided by when, and how the losing side stayed on board.

Tests whether you can hear criticism without defending yourself. Pick feedback you now agree was right, show the clarifying question you asked, one concrete change you made, and evidence that the change stuck.

Tests honesty and self-awareness under a question designed to tempt evasion. Pick a real failure with a cost you can name, own your part in first person, and show one habit that changed because of it.

Probes early communication and realistic re-planning, not perfection. Give one real slip you owned, the moment you first knew, the options you brought when you escalated, how late it actually was, and the estimating habit you changed.

Tests whether failure actually changed you. Name one concrete mistake, state the lesson in a single sentence, describe the habit or check you adopted because of it, and give evidence the change has held since.

Probes growth mindset and honesty about gaps. Name the skill you lacked, show that you flagged it early, describe a deliberate ramp-up with targeted help, and finish with delivered work plus the ability you kept.

Tests whether your ambition is real, self-aware and satisfiable here. Answer with a direction and a capability rather than a title, one concrete near-term step, and an honest link to what this role actually offers.

Tests whether the thing pushing you out also exists here, and how you talk about people you are leaving. Give one honest, specific reason without blame, credit what the role gave you, then land on the pull toward this job.

Three kinds of source: how the company builds (its public engineering writing), what it sells (the product itself), and how it is funded or performing. Capture the findings on one page as hooks and questions, not as memorised facts.

Asks you to make your own case out loud. Give one claim, two pieces of evidence closest to the job's hardest task, one thing the resume does not show, and an honest note on what you would need early.

Tests whether you want this job or any job. Answer with two or three specifics from the posting, evidence you have already done that kind of work, and what the role gives you next.

Tests whether a change of goal produces resentment or re-planning. Name what changed and what you had already built, show how you triaged salvage versus discard, renegotiated scope openly, and shipped something smaller on purpose.

Tests judgment under uncertainty, not luck. Answer with one real call: the fact you were missing, the timebox you set, the assumptions you wrote down, why the path you chose was cheap to undo, and what the later data showed.

Probes whether you turn a vague ask into a buildable scope instead of guessing or stalling. Answer with the questions you asked, the assumptions you wrote down, and the definition of done you agreed before writing code.

Tests whether you push back on the decision rather than the person. Name one real disagreement, show the evidence you brought, use the proper channel, and end with a decision that everybody owned.

Tests whether you surface schedule risk early and negotiate with options instead of nodding and missing. Answer with the estimate that exposed the gap, a scope-time-people counter-proposal, and the date you actually committed to and hit.

Spend a peer engineer's window on daily mechanics: how a merged change reaches users, deploy cadence, on-call rotation depth, review turnaround, and how tech debt gets picked up. Leave strategy, headcount and pay to other interviewers.

Save the questions only an owner of the business can answer: funding stage and months of runway, how the company will make money, what stops a competitor copying it, and which people the business depends on.

Asking a hiring manager to define success at 90 days converts an advertised job description into the standard you will actually be judged against, and it reveals whether the manager has shaped the role at all.

Ask a skip-level director the org-level questions only they can answer: where this team's work sits among company priorities, how headcount is planned, how disputes between teams get decided. Day-to-day questions belong in the peer round.

Save the process and calibration questions for the recruiter: how many stages there are, what each assesses, the timeline, the level the role is posted at, and the pay band for that level. Later interviewers rarely own those facts.

A walk-away number is the lowest package you would genuinely decline below, chosen from benchmark data before any offer exists. Fixing it early keeps a late, pressured decision from being made by adrenaline rather than by evidence.

Tests whether you know your market and can talk money without flinching. Ask for the band budgeted for the level first, and if pressed give a researched range tied to scope, never a single low number.

A written acceptance creates a shared record of what was agreed. A verbal yes leaves title and level, base, bonus, equity grant and start date to two people's memory, and memory is where offer terms quietly drift apart.

A short expiry limits comparison shopping: it forces a decision before competing processes can finish. Some deadlines reflect real constraints like closing headcount; many are pressure. Asking a recruiter what set the date costs nothing.

Anchoring is the pull the first concrete number exerts on everything said afterwards: later figures get judged as moves away from it rather than valued fresh. Whoever anchors sets the range the rest of the conversation happens inside.