Role-Pack Template
Copy this page to roles/<firm-role>/README.md when adding another role.
Source metadata
- Firm and role:
- Location/team:
- Description source and capture date:
- Seniority:
- Explicit languages/technologies:
Competency map
| Source wording | Normalized competency | Core chapter | Priority | Evidence to prepare |
|---|---|---|---|---|
Role thesis
In one sentence, why does this team hire this role?
Candidate positioning
- Transferable strengths:
- Direct evidence:
- Gaps to close:
- Honest 90-second bridge:
Three-day overlay
| Day/block | Core material | Role-specific drill | Proof |
|---|---|---|---|
Likely capability questions
List questions implied by the role. Label any process-specific claim as inference.
Coding drills
Include contract, examples, edge cases, complexity, and scoring.
Design drills
Include scale, identity/time, ordering, backpressure, recovery, observability, deployment, security, and alternative designs.
Behavioral evidence
Map six candidate stories to the role signals.
Questions for interviewers
Ask about real work, constraints, ownership, success, and technical boundaries.
Final checklist
- [ ] every priority maps to source wording;
- [ ] critical gaps have practice output;
- [ ] two coding and one design mock completed;
- [ ] six story cards rehearsed;
- [ ] internal links and code/tests validated.