CTO Team Building & Technical Leadership 4 — Questions and Answers
Question 1: A CTO wants to reduce 'hero culture' where the same few engineers fix all production incidents. What is the best systemic fix?
- Rotate on-call duties and invest in runbooks and incident training (Correct answer)
- Reward engineers who do not need to escalate incidents
- Hire additional senior engineers to distribute the expert pool
- Move to a NoOps model to eliminate manual incident response
Correct answer: Rotate on-call duties and invest in runbooks and incident training
Rotating on-call with supported runbooks builds broad incident response capability and eliminates single points of failure in the team.
Question 2: When should a CTO choose to rebuild a technical team structure rather than incrementally adjust it?
- When attrition exceeds 10% annually
- When the existing structure creates systemic bottlenecks that incremental change cannot resolve (Correct answer)
- When a new VP of Engineering is hired
- When the company adopts a new technology stack
Correct answer: When the existing structure creates systemic bottlenecks that incremental change cannot resolve
Structural rebuilds are warranted when bottlenecks are architectural to the org design itself, not addressable through personnel changes or process tweaks.
Question 3: A remote engineering team reports feeling disconnected from company strategy. Which intervention has the most sustained impact?
- Sending a monthly company newsletter with strategy updates
- Creating a Slack channel dedicated to strategy questions
- Including engineers in quarterly planning and showing how their work maps to company goals (Correct answer)
- Hosting annual in-person all-hands events
Correct answer: Including engineers in quarterly planning and showing how their work maps to company goals
Including engineers in planning and explicitly connecting their work to outcomes creates ongoing strategic alignment rather than passive information consumption.
Question 4: A CTO is evaluating two engineering manager candidates: one with strong technical depth but limited people experience, another with strong people skills but limited technical depth. For a team building a new distributed system, which factor should weigh most heavily?
- Technical depth, because the team needs technical direction
- People skills, because engineers need coaching and growth (Correct answer)
- Whichever candidate the engineering team prefers
- The candidate's experience with the specific technology stack
Correct answer: People skills, because engineers need coaching and growth
Engineering managers primarily succeed through people development and team health; technical direction can be provided by tech leads and architects on the team.
Question 5: What does the 'two-pizza rule' for team sizing, popularized by Jeff Bezos, primarily optimize for?
- Cost efficiency in headcount
- Cognitive bandwidth and communication overhead within the team (Correct answer)
- Delivery speed of individual features
- Clear accountability in performance reviews
Correct answer: Cognitive bandwidth and communication overhead within the team
The two-pizza rule (5-8 people) limits communication overhead, which grows factorially with team size, keeping teams focused and fast.
Question 6: A CTO is preparing a technical roadmap for the board. Which framing will be most persuasive to a non-technical board?
- Detailed architecture diagrams showing current and future state
- Risk-reduction and capability timelines tied to business outcomes (Correct answer)
- A comparison of the company's tech stack to industry benchmarks
- Engineering velocity metrics showing sprint completion rates
Correct answer: Risk-reduction and capability timelines tied to business outcomes
Boards focus on risk and business outcomes; framing technical investments in those terms makes the roadmap legible and actionable for non-technical stakeholders.
Question 7: Which leadership behavior most strongly predicts whether an engineering team will proactively flag technical debt before it becomes a crisis?
- The CTO mandating quarterly tech debt audits
- Leaders consistently rewarding engineers who surface problems early (Correct answer)
- Tracking tech debt in a dedicated backlog visible to all
- Including tech debt reduction in sprint velocity calculations
Correct answer: Leaders consistently rewarding engineers who surface problems early
Consistent positive reinforcement for surfacing problems early creates the psychological safety and incentive structure needed for proactive flagging.
CTO Team Building & Technical Leadership 4
A CTO wants to reduce 'hero culture' where the same few engineers fix all production incidents.
What is the best systemic fix?