The path from individual contributor to CTO is not a straight line. It's a series of increasingly uncomfortable transitions where the skills that made you successful at the previous level actively work against you at the next. The best engineer on the team is not automatically the best engineering manager. The best engineering manager is not automatically the best director. And the best director is not automatically the best CTO.
Each transition requires letting go of what made you great and developing entirely new capabilities. Here's what that looks like at every level.
The Leadership Ladder
Level 1: Individual Contributor (IC)
Primary job: Solve technical problems. Write good code. Ship features.
What success looks like:
- Delivers assigned work reliably and with quality
- Grows technical skills continuously
- Contributes to code reviews and technical discussions
- Understands the system they work in
Key skills: Technical depth, problem-solving, craftsmanship, learning speed.
What you're optimising for: Personal productivity and technical excellence.
Level 2: Senior IC / Tech Lead
Primary job: Multiply the team's effectiveness through technical leadership.
What changes: Your impact is no longer measured by what you personally build. It's measured by how much better you make the people around you — through architecture decisions, code reviews, mentorship, and technical direction.
What success looks like:
- Leads technical design for complex features
- Mentors junior and mid-level engineers
- Makes architecture decisions that the team follows because they're right, not because of authority
- Writes less code, but the code they write is higher-leverage (frameworks, tooling, critical paths)
Key skills: System design, communication, mentorship, technical decision-making.
The trap: Continuing to optimise for personal output. The senior IC who reviews every PR, writes every critical piece of code, and makes every architecture decision is a bottleneck, not a leader.
Level 3: Engineering Manager
Primary job: Build and maintain a high-performing team.
What changes: Everything. Your job is now about people, not code. Your calendar fills with 1:1s, hiring interviews, performance conversations, and cross-team coordination. The dopamine hit of solving a technical problem is replaced by the slower satisfaction of watching your team solve problems without you.
What success looks like:
- Team delivers consistently and predictably
- Team members are growing in their careers
- Retention is high (people want to stay on the team)
- Hiring pipeline produces strong candidates
- Cross-team dependencies are managed proactively
Key skills: People management, hiring, feedback delivery, priority setting, emotional intelligence.
The trap: The "player-coach" who keeps coding. If you're spending more than 20% of your time writing production code as an EM, you're neglecting the people who need your attention. Every hour you code is an hour you didn't spend on the 1:1, the career conversation, or the hiring pipeline.
Level 4: Director of Engineering
Primary job: Manage managers. Align multiple teams toward business outcomes.
What changes: You're one level removed from the work. You don't know the details of every sprint, and you shouldn't. Your job is to set direction, remove blockers, and ensure that your managers are effective.
What success looks like:
- Multiple teams deliver coherently toward shared goals
- Engineering managers are effective and growing
- Technical strategy aligns with business priorities
- Cross-functional relationships (product, design, sales) are productive
- You can explain what your teams are doing and why it matters to the business
Key skills: Strategic thinking, organisational design, cross-functional leadership, executive communication, conflict resolution.
The trap: Micro-managing your managers. If you're sitting in their team's stand-ups or reviewing PRs, you're doing their job (badly) instead of your own.
Level 5: VP of Engineering
Primary job: Own engineering execution at the organisational level.
What changes: You're now an executive. Your decisions affect the entire engineering organisation — headcount, budget, process, culture. You spend significant time with other executives (CEO, CPO, CFO) aligning engineering with company strategy.
What success looks like:
- Engineering organisation scales effectively (20 → 50 → 100+ engineers)
- Delivery is predictable at the portfolio level
- Engineering is seen as a strategic partner, not a service organisation
- The organisation attracts and retains top talent
- Engineering culture is healthy and productive
Key skills: Organisational design, budget management, executive communication, culture building, strategic planning.
The trap: Staying too operational. The VP who's still running sprints and triaging bugs is not doing VP-level work. Hire or develop directors who can own execution.
Level 6: CTO
Primary job: Set the technology vision and ensure technology enables the business strategy.
What changes: You're no longer primarily an engineering leader — you're a business leader who happens to understand technology deeply. Your peer group is the CEO, CFO, COO, and board. Your job is to connect technology decisions to business outcomes.
What success looks like:
- Technology strategy exists, is understood, and drives decisions
- The board and investors trust the technology direction
- Technology is a competitive advantage, not just a cost centre
- Innovation pipeline produces meaningful capabilities
- The engineering organisation operates effectively without your daily involvement
Key skills: Business acumen, board-level communication, innovation strategy, vendor and partner management, risk management.
The trap: Staying in the VP of Engineering role. If the CTO is managing the engineering organisation day-to-day, they're not doing CTO work. The CTO who can't let go of operational control will never be effective at the strategic level.
The IC-to-Manager Decision
This is the most consequential career decision in engineering, and most people make it for the wrong reasons.
Wrong reasons to become a manager:
- It's the only way to get promoted or earn more money
- You're the most senior engineer on the team
- Someone told you it's the next step
- You want to have "authority"
Right reasons to become a manager:
- You genuinely enjoy helping others grow
- You're energised by organisational problems (hiring, process, team dynamics)
- You're willing to give up the satisfaction of personal technical achievement
- You find cross-functional communication interesting, not draining
The test: Think about the best week you've had in the last year. Was it a week where you solved a hard technical problem? Or was it a week where you helped someone else solve a hard problem, hired a great candidate, or improved a team process? Your answer reveals your actual preference.
Developing Leaders Internally
The Apprenticeship Model
The best way to develop engineering leaders is through apprenticeship:
- Shadow: The aspiring leader observes their manager in 1:1s, hiring decisions, and cross-team negotiations (with appropriate context)
- Assist: They take on specific leadership responsibilities — running a project, mentoring a junior, leading a hiring loop
- Own: They get a small team or project to manage independently, with their manager as coach
- Scale: If successful, they take on larger scope
Common Development Gaps
| Gap | How to Develop It |
|---|---|
| Giving feedback | Practice in low-stakes situations, get coaching on delivery |
| Strategic thinking | Involve them in roadmap planning, ask them to present trade-offs |
| Executive communication | Have them write board updates, present to leadership |
| Hiring | Include them in interview loops, have them make hiring recommendations |
| Conflict resolution | Coach through real situations, debrief on what worked |
The Dual Track
Companies that force a choice between management and IC careers lose talent. Implement a dual-track career ladder where senior ICs (Staff Engineer, Principal Engineer, Distinguished Engineer) have equivalent compensation and scope to management roles. The IC track emphasises technical leverage across the organisation; the management track emphasises people and organisational leverage.
Building an engineering leadership pipeline is one of the highest-leverage investments a technology organisation can make. If you're working on developing your engineering leaders, let's talk.