For Software Engineers, Tech Leads, and New Engineering Managers
The hardest part of technical growth is not the code — it is the high-stakes conversation. Asking for promotion. Pushing back on unrealistic deadlines. Disagreeing with tech leads. Rehearsed in private before you are in the room.
Select a scenario below and choose how you would respond. See the real-time manager reaction and behavioral coaching breakdown.
Each guide breaks down the exact conversations, friction points, and evaluation criteria that decide progression at your stage.
Why strong individual contributors stall, and the 4 conversations that unlock senior promotion cases.
Influence without authority — the senior-to-staff gap, cross-team alignment, and unblocking org-level roadblocks.
Accountability without authority. Handling architectural disagreements, code review friction, and protecting scope.
First 1:1 frameworks, navigating underperformance, and surviving the transition with no immediate feedback loops.
Most communication errors in engineering are not caused by lack of technical intelligence, but by unpracticed default reactions under pressure.
Most technical plateaus are not skill deficits — they are predictable behavioral patterns. Which one describes where you are right now?
Excellent in a crisis, which is why you are always in one. Your week belongs to whoever pings last, leaving high-impact promo work stranded.
Substantive engineering output that nobody outside the team notices. Believing code speaks for itself while calibration docs are written from memory.
Deeply knowledgeable in a legacy domain that has stopped evolving. Irreplaceable where you are, making promotion lateral moves impossible.
Avoids friction, lets architectural concerns slide, and pays for it privately. Read by leadership as agreeable rather than technically discerning.
Competent and executing well, but drifting in a direction you never deliberately chose. Stalls at senior due to a lack of explicit career thesis.
Took the tech lead or manager role and kept doing the IC coding late at night. The team bottleneck because delegating feels slower.
Explore how DrillUp measures and coaches each of the 6 foundational dimensions that determine engineering trajectory.
Absorbing interrupts silently without making tradeoffs explicit, leaving critical initiatives delayed and burning out.
Asking what gets displaced before committing to new scope; protecting non-negotiable deep-work blocks for promotion cases.
A structured framework to diagnose your baseline, rehearse challenging interactions, and build verified communication reflexes.
Answer 12 calibrated scenario questions mapping your tendencies across Focus, Visibility, Growth, Conflict, Ambition, and Leadership.
Access psychology-backed templates designed for pushback, performance check-ins, offer counters, and compensation reviews.
Rehearse branching dialogues in the app. Experience realistic manager pushback and test responses in a zero-stakes environment.
Log structured reflections in the smart journal to track workplace dynamics and receive weekly synthesized pattern analysis.
Built from the ground up for technical leaders who want deliberate practice, not generic workplace advice.
Every response branches the conversation. Practice disagreeing with strong personalities and navigating tough deadlines.
Curriculums generated specifically around your assessed archetype and career transition goals.
Track your score progression across 6 core technical leadership dimensions with tangible benchmarks.
Synthesize weekly reflections to identify recurring communication hurdles before they impact your reviews.
Free, standalone guides equipped with behavioral frameworks, interactive builders, and copy-paste verbal scripts.
The "Tradeoff Matrix" method to protect scope and quality without sounding uncooperative.
How to challenge architectural decisions constructively using data and rollback risk arguments.
The 30-minute agenda framework to build mutual trust and set clear expectations from day one.
Moving from task execution to scope ownership: building a promotion document that passes calibration.
How to counter tech offers and annual performance reviews based on market compensation bands.
Delivering critical architectural critiques on pull requests without demoralizing teammates.
Join thousands of engineers and technical leaders rehearsing high-stakes conversations before stepping into the room.
