Become VP Engineering (First Time)
52 weeks · 0 milestones
Earn or be promoted to your first VP Engineering role, with documented scope: team size, budget, and reporting line.
Milestone map
Milestone map
3 milestones
Evaluate your current engineering organisation structure and produce a redesign proposal. The proposal must be grounded in explicit criteria: team size norms (two-pizza or similar), cognitive load per team, system ownership clarity, and cross-team dependency minimisation. Document the current state, the proposed state, the rationale for each structural change, and the transition risks. Present to senior engineering and product leadership and document their challenges.
Proof required
Submit your team structure redesign proposal (min 1000 words), including current-state diagram, proposed-state diagram with rationale, and a documented Q&A session with senior engineering or product leadership who challenged the proposal.
What gets checked
- Current state and proposed state are diagrammed — not just described
- Each structural change is argued against explicit criteria (cognitive load, ownership, dependencies)
- Q&A record shows genuine challenges to the proposal from senior leadership
Resources
Enroll free to unlock learning resources →Mastery
Google re:Work — Manager Tools
Research-grounded principles for effective engineering organisations
Unlocks after completing Foundation + Depth