Most engineering training stops at the technical layer. After ten years of writing code we know how to write more code; the assistants help us write it faster. The harder questions — how to scope work that’s bigger than you, how to run an incident without burning the team out, what to put in a staff promotion packet, what to say in the negotiation that follows an offer letter — are usually learned through expensive accidents. They are also the questions whose answers have changed most in the last two years, as the rest of the work has changed around them.

We are building short, focused courses on those questions. Each is between four and six hours of self‑paced material — readings, recorded conversations with senior engineers and engineering leaders, exercises drawn from real situations. No multiple‑choice quizzes. No certificate. Just the material, in a form we hope is useful to senior engineers who would rather not learn this on the job.

Courses in development

Scoping & estimation under pressure

How to size work that’s bigger than you, how to communicate uncertainty without losing credibility, how to negotiate dates that survive the first surprise. Includes a section on estimating work in which AI assistants change part of the throughput but not the rest.

Running incidents without burning out

Incident command for engineers who don’t have a manager title. The structural fixes that prevent the next one. How to survive being the person who’s always paged. How AI tools help and hurt during the first ten minutes.

The staff promotion packet that lands

The difference between writing what you did and writing what you decided. A teardown of three real packets — two that landed, one that didn’t — and what’s changed in promotion bars since 2024.

Negotiating a senior offer

What’s negotiable, what isn’t, what the recruiter can and can’t do, and the question that almost always raises the offer by ten percent.