85 lines
5.2 KiB
Markdown
85 lines
5.2 KiB
Markdown
# Prep pack
|
|
|
|
One pack per stage. Sections in this order; omit a section only when it has nothing to say for this stage.
|
|
|
|
## 1. Header and logistics
|
|
|
|
Company, role, stage, date and time with time zone, format, interviewers with titles, and the channel details the owner gave (link, address, dial-in).
|
|
|
|
Format notes, as relevant:
|
|
|
|
- Phone or video: STAR answers written out and within reach, water nearby, test the link and audio beforehand, a quiet room. Taking five seconds to think is fine; asking for clarification on a vague question is fine.
|
|
- Onsite: travel time, who to ask for at reception, what to bring.
|
|
- Take-home or case: the brief's deadline, what is assessed, how it will be presented.
|
|
- Close with: "Is there anything else you'd like to know about my background?"
|
|
|
|
## 2. Likely questions
|
|
|
|
Derive from four sources, in this priority order, and label each question with its source:
|
|
|
|
1. **Earlier-round feedback.** Anything flagged, doubted or left unresolved will come back. Note who raised it.
|
|
2. **Gaps in the fit.** The requirements where the career master is weakest are the likeliest probes. Each gets a bridge per `star-and-gaps.md`.
|
|
3. **The posting's requirements**, competency by competency, essential before desirable.
|
|
4. **The stage type:**
|
|
|
|
| Stage | Typical questions |
|
|
|---|---|
|
|
| Screen | Motivation, why this company, CV walk-through, notice period, salary expectation, location or remote |
|
|
| Hiring manager | Scope carried, how he works with others, a conflict, a failure, priorities in the first months |
|
|
| Technical | The posting's stack, every tool the CV names, design trade-offs, debugging a past incident, live exercise |
|
|
| Case | Structure a problem out loud, estimates, trade-offs, a recommendation and its risks |
|
|
| Panel | Mixed; one question per panel member's angle, consistency across them |
|
|
| Final | Values, long-term fit, salary and start date, "any reservations about us?", references |
|
|
|
|
Aim for 8-15 questions, ranked. Fewer and deeper beats a long generic list.
|
|
|
|
## 3. STAR mapping
|
|
|
|
For each likely question, the best STAR example from the career master, or a bridge if none fits. Rules in `star-and-gaps.md`. Reuse a strong story across questions only with a different angle each time; note which.
|
|
|
|
## 4. Consistency brief
|
|
|
|
List the claims in the submitted CV and cover letter the interviewer is most likely to probe: numbers, scope, titles, tools named, achievements, anything phrased strongly. For each:
|
|
|
|
| Claim on paper | Where | Career-master backing | Depth check |
|
|
|---|---|---|---|
|
|
| Cut deploy time from 40 to 8 minutes | CV, role 2 | Yes, project X | Can explain the before, the change and how it was measured |
|
|
|
|
Then:
|
|
|
|
- **Stretches**: claims that read stronger than the career master supports. Give the honest, defensible version to say in the room.
|
|
- **Pitfall hits**: claims on paper that a pitfall entry marks as wrong. Give the right version and how to correct it in passing without drama ("to be precise, it was ...").
|
|
- **Unclaimed strengths**: relevant career-master facts not on paper. They may be raised if asked, as facts, but do not lead with them as if they were on the CV.
|
|
|
|
The rule, stated in the pack: no claim in the room that isn't on the paper, and every claim on the paper must be defensible in depth.
|
|
|
|
## 5. Hard questions
|
|
|
|
Prepared answers grounded in the career master, in the owner's register, each 30-90 seconds:
|
|
|
|
- **Why did you leave / why are you leaving?** Honest, forward-looking, no negativity about a former employer. Match the dates and reasons the CV implies.
|
|
- **"You don't have X."** One per real gap; bridge per `star-and-gaps.md`.
|
|
- **Where do you see yourself in five years?** Ambition that fits the role's growth path as the posting and research describe it.
|
|
- **Biggest weakness?** A real one with the concrete mitigation the owner actually uses. Not a disguised strength.
|
|
- **Why this company?** Uses the verified hooks. Never a generic line.
|
|
- **Salary expectation**, when the stage calls for it: ask the owner for his number and range; do not invent market data. If he wants a benchmark, research it and cite sources like any other claim.
|
|
- Any hard question the earlier-round feedback implies.
|
|
|
|
## 6. Questions to ask
|
|
|
|
Pick 4-6, matched to the stage, the research and the interviewer:
|
|
|
|
- **Screen**: role and team. What a typical week looks like, what success in the first six months means, the biggest challenge the team faces, how big the team is and how work is divided.
|
|
- **Technical**: stack and growth. The stack for the area the role touches, how work goes from idea to production, room to grow into architecture or strategy, how the team keeps current.
|
|
- **Hiring manager and final**: culture and leadership, the last chance to find a deal-breaker. Leadership style, what people who thrive here have in common, balance between new work and maintenance, professional development, remote or hybrid policy, onboarding.
|
|
|
|
Cut every question the public material or the posting already answers; asking it shows the research was not done. Prefer questions that build on a verified hook or on something an earlier round said.
|
|
|
|
## 7. Sources
|
|
|
|
The claim/source table from `company-research.md`, so the owner can defend any fact he uses.
|
|
|
|
## Closing blocks
|
|
|
|
Facts to add to the career master; Pitfalls to add. See SKILL.md.
|