technical-leadership

technical-leadership

Guide others through ambiguity, unblock progress, and make sound calls as a technical lead or mentor.

Debugging an Elusive Staging-Only Bug

Navigate a team debugging session focused on a bug that only surfaces in the staging environment, practicing technical leadership and collaborative problem-solving.

Mid1–4 people
15–20 min

Diagnosing a Performance Regression

Lead your team in diagnosing and addressing a performance regression impacting a production system.

Mid1–4 people
15–20 min

Coaching Peers Through Architectural Ambiguity

Learn how to guide your team through uncertain architectural decisions while fostering collaboration and enhancing everyone's understanding.

Senior1–3 people
10–15 min

Leading Through a Messy Legacy System

Tackle technical debt head-on by guiding your team to address issues in a legacy system while minimizing disruptions.

Senior2–4 people
15–20 min

Deciding When to Refactor vs. Ship

Learn how to balance the need for refactoring with the pressure to ship new features, maintaining code quality without delays.

Mid1–3 people
10–15 min

Balancing Innovation and Stability in Technology Adoption

Navigate the discussion on adopting new technology while balancing innovation and maintaining system stability.

Mid-Senior3–4 people
20–30 min

Navigating a Controversial Design Decision

Practice leading a team through a contentious technical decision, balancing differing opinions and guiding the group to a consensus.

Senior2–4 people
15–20 min

Breaking Down a Large Initiative into Phases

Lead a team discussion to decompose a big project into manageable parts, ensuring clarity, feasibility, and alignment with business goals.

Senior1–4 people
10–15 min

Managing Disagreement Over Tech Debt Priority

Navigate a team discussion on tech debt priorities, balancing technical health with project needs.

Mid2–4 people
10–15 min

Guiding a Junior Developer Through a Problem-Solving Session

Practice how to effectively mentor a junior developer through a technical challenge without taking over.

Mid1–2 people
10–15 min