Tech Leadership Challenge — the quiz for engineers who lead

The Tech Leadership Challenge is built for the population that actually reads Staff Engineer, argues about whether High Output Management has aged well, and has at least one Paul Graham essay bookmarked. It's not an engineering pop quiz — it's a knowledge check across the canon senior engineers and managers are expected to have read. Jasper runs the round like a competent moderator at a founder AMA — crisp, high-signal, no filler — and the pacing respects that the audience doesn't want sound effects, just clean rounds and a clear score.

Questions span the actual reading list senior tech leaders pass around. Staff Engineer archetypes and the path from senior to staff. The Making of a Manager's first-90-days framework and the manager-IC pendulum. High Output Management's managerial leverage and the 1:1 structure. Accelerate's four DORA metrics and the research behind them. Team Topologies' stream-aligned and platform teams. The Paul Graham essays that shaped a generation of founders (Maker's Schedule, Do Things That Don't Scale, Beating the Averages, How to Start a Startup). The Google SRE book's error-budget concept. The practical trade-offs — on-call rotations, performance calibration, RIFs done well versus badly — that don't show up in books but show up in every senior-manager 1:1. The questions aren't trick questions; they're recall for people who've read the material and applied it.

Engineering-leadership channels share work like this exactly the way product-management channels share Lenny's Newsletter: one person plays, the score drops into #engineering-leadership, and the next person has to either match it or admit they haven't read Staff Engineer. The format loops in Slack because the share card previews the pack name and the score. Over the first 90 days at a new company, new staff engineers and EMs use it as the cleanest way to surface the reading-list gap — play the round, see what you got wrong, pick the book off that gap.

Custom rounds are where this gets useful operationally. Paste your team's internal engineering-principles doc and Trivana generates a hosted round keyed to it — run it at the new-EM onboarding, the staff-eng sync, or the tech-all-hands as a replacement for a slide summary. Drop an ADR PDF and get a round that tests whether the team actually read the decision. Drop your founder memo and get a quiz that tests whether the company remembers the strategy shift from last quarter. The pattern is: docs nobody re-reads become rounds everybody plays.

Jasper is the default voice for tech-leadership content because his tone carries the credibility the audience expects. Calm, confident, never breathless — closer to a podcast moderator than a gameshow host. On paid plans, Smart Host voice reactions mean Jasper reacts specifically to each answer, which turns the round into something that feels less like a form and more like a sparring partner who's read the same books.