prepare-a-technical-interview

name	prepare-a-technical-interview
category	get-hired
description	Turn a specific technical role and interview format into a focused practice plan, realistic mock sessions, and an evidence log that targets actual gaps. Use when someone has a software, data, product, design, or technical interview and needs role-specific preparation beyond generic interview advice.

prepare-a-technical-interview

Practice the work the interview will sample, under the constraints the person will face. Diagnose gaps from recorded attempts and improve the weakest high-value behavior first.

Inputs

• Gather the job description, company brief, recruiter guidance, interview stages, timing, and allowed tools.
• Ask what the person has already practiced, where they freeze, and when the interview occurs.
• Use only public or legitimately provided interview information. Do not seek leaked questions.

Procedure

1. Build an interview map with stages, duration, likely competencies, expected artifacts, interaction style, and known evaluation criteria.
2. Extract role signals from the posting and company context. Rank skill areas by role importance, current confidence, and time available.
3. Run one baseline exercise under realistic timing without coaching. Save the solution, notes, and self-explanation.
4. Score the attempt on problem framing, clarification, correctness, trade-offs, communication, verification, and recovery from mistakes.
5. Build a practice backlog from observed gaps. Prefer one representative exercise per gap over many random problems.
6. Practice a complete loop: restate, clarify, propose approach, implement or analyze, test, discuss alternatives, and summarize. Include collaboration rather than silent performance.
7. Rehearse relevant formats: coding, debugging, SQL, system design, portfolio review, case exercise, take-home explanation, or technical presentation.
8. Conduct at least one mock with another person or a fresh evaluator. Keep feedback tied to the rubric and examples from the session.
9. Repeat the baseline skill area with a new problem. Compare the two attempts and update the backlog.
10. Prepare logistics, concise project stories, questions for interviewers, and a recovery script for uncertainty or a stuck moment.
11. Stop intensive practice early enough for sleep and a calm final review.

Boundaries

Do not impersonate the candidate, complete a take-home that forbids assistance, or fabricate project experience. Do not use private interview banks or employer-confidential material. Keep accommodations and accessibility needs under the person's control.

Done

• An interview map connects each stage to likely competencies, constraints, and preparation evidence
• A baseline and later attempt use the same rubric and show specific improvement or a remaining gap
• The practice log records exercises, timing, errors, feedback, and the next targeted repetition
• Logistics, project stories, interviewer questions, and a stuck-moment recovery plan are rehearsed

Then use interview-prep for behavioral practice and research-a-company for current role context.