Build a Team
Hiring plans, interviews, team design: from the person who ran them at a 3,000-engineer organization.
Ours ran at an organization of
3,000 engineers- the hiring loops
- the promotion committees
- the reorganizations that worked and the ones that did not
You get the distilled version, sized for your company.
Why the number matters
Team design fails quietly and expensively, and most advice on it has never been tested at scale.
The scope
- StructureTeam shapes and interfaces designed around the architecture, not an org chart copied from a company with different problems.
- Hiring planWhich roles, in which order, at which seniority. And which roles not to hire, because the work should be automated or bought.
- InterviewsLoops that measure the job, not trivia.
- Promotions and growthCareer paths that keep the engineers you cannot afford to lose.
- CoachingYour leads, made better at the parts nobody taught them: feedback, scoping, saying no.
Interviews
- We design them
- run the first ones with you
- train your people to keep the bar where we set it
Finding candidates stays with you or your recruiter.
The deliverable
A team that exists and functions:
- the structure on paper
- the hiring plan, role by role
- the interview loop that keeps quality up after we leave
- a prioritized action plan for what to build next

Which roles do you need to fill first?
A 30-minute call about the roles you need, in the right order, and the interviews that test for them.

