Technical interview guide

Behavioral Interviews & STAR

Structured behavioral interviewing: STAR letters with numbers, conflict and failure without theater, and job-related scoring.

Read: 34 min
Practice MCQs: 25
Interview QA: 25
Edition: v4
Editorial status: Reviewed
Relevant for: Backend EngineerFrontend EngineerFull-Stack DeveloperProduct ManagerSoftware EngineerTechnical Product Manager

Scope: STAR as used in DDI-style behavioral interviews; structured interviewing per U.S. OPM; U.S. federal pre-employment guidance per EEOC and DOJ; principle-mapped loops as published by Amazon.

Interview QA

Treat each question like a live interview question: answer out loud first (structure, assumptions, tradeoffs), then open the model answer to spot gaps and rehearse a tighter follow-up.

Curated: 2026-10-05 · Written: 2026-10-05 · Reviewed: 2026-10-04

QA-1

Tell me about a time you had a technical disagreement with a peer or stakeholder. How did you handle it and what was the outcome?

QA-2

Describe a major mistake or project failure you experienced. What specific actions did you take to remediate it and what did you learn?

QA-3

Walk through situation as scope not autobiography, including where engineers most often get it wrong.

QA-4

What does task as the decision you owned guarantee, and what does it deliberately leave open?

QA-5

Describe action as first-person verbs and the evidence you would collect before relying on it.

QA-6

How do you structure a concise behavioral answer using the STAR method without losing the interviewer to technical minutiae?

QA-7

Where does the missing Result follow-up matter, and where is it irrelevant?

QA-8

Teach we versus I ownership to an engineer who has only seen it as a rule of thumb.

QA-9

If last week's incident involved conflict without villains, what would you write in the report?

QA-10

How would you test a claim that the system depends on failure without redemption theater?

QA-11

What would you measure before treating leadership without a title as settled?

QA-12

How does disagreement with a manager change if the workload grows by two orders of magnitude?

QA-13

A vendor promises saying no to scope is handled for you. What do you still own?

QA-14

When would you refuse a design because of delivering bad news?

QA-15

How would you explain influence without authority without using the usual slogan?

QA-16

What failure would you inject to check a team's understanding of mentoring versus doing the work?

QA-17

How should on-call treat an alert that names incident ownership and blamelessness as the cause?

QA-18

What belongs in a runbook section on trade-off stories with numbers, and what does not?

QA-19

How would you review a pull request whose risk is time-boxing a four-minute answer?

QA-20

What trade-off does the follow-up probe force that a junior answer usually skips?

QA-21

How would you brief product on why mapping a story to a leadership principle delays a ship date?

QA-22

What is the smallest experiment that would change your mind about rehearsed scripts versus reusable facts?

QA-23

How does protected-topic and pre-offer questions interact with rollback, and where do people ignore that?

QA-24

What would you ask a candidate who recites calibrating seniority in the story but cannot apply it?

QA-25