For when your manager controls the budget
Convince your boss
The math, the talking points, and the email. Get to yes in one Slack message.
Reframe the ask first
Don't pitch this as "professional development" — that phrase makes managers think perk, not investment.
Pitch it as the leadership-skills training your senior+ JDs already require. Cross-team alignment, incident leadership, technical communication, executive presence — the things on every staff/principal job description that nobody knows how to teach.
Your manager isn't paying for a course. They're paying for a more promotable engineer who's less likely to leave.
The math
Three talking points (in priority order)
Week 2 covers incident leadership specifically — the "calm voice in the channel" who runs the response. Better communication during incidents = shorter MTTR, fewer botched rollbacks, less stakeholder panic. Show your manager the on-call data; this is a direct ops investment.
The async-vs-sync framework and the disagreement playbook (raising concerns in writing before decisions ship) reduce the meeting bloat and cross-team thrash that quietly burns 10-20% of senior eng time. Your manager has watched this. They know.
The promotion brief, the 1:1 reset, and the follow-up habit are the exact behaviors managers wish their reports would do unprompted. Your manager spends real time writing your packet. This makes their job easier.
The email — copy and paste
Pre-filled. Just swap the bracketed placeholders.
Hi [Manager Name], I'd like to request approval to enroll in the Developer EQ Live Cohort — a 4-week leadership-skills program designed specifically for engineers. It runs Tuesday evenings (7-8:30 PM CST), so it's outside work hours and won't impact my deliverables. Here's why I think it's a strong investment: 1. It targets the exact skills our senior+ JDs already require — cross-team alignment, incident leadership, technical communication, mentoring. The kind of work that's hard to learn on the job because there's no formal feedback loop. 2. The cost is $500. For comparison, comparable individual leadership coaching runs $5,000-$15,000, and external "engineering soft skills" workshops are typically $1,500-$3,000. Per Gallup, the cost of replacing a senior engineer is between half and twice their annual salary — so even a small bump in retention pays this back many times over. 3. I'd come back with three deliverables for the team: - A documented "incident response card" we could adapt for our on-call rotation - A 1:1 agenda template the team could use - A short readout in our team meeting on the most relevant takeaways Logistics: - Cost: $500 one-time - Format: 4 sessions, 90 minutes each, on Tuesday evenings - Dates: [Pick one — May 12 / June 9 / July 7 starts] - Time commitment outside work hours: ~6 hours of class + ~4 hours of homework over 4 weeks - Sign-up: developereq.com/cohort Happy to discuss in our next 1:1, or I can send you a quick summary doc. Either way works. Thanks, [Your Name]
If they push back
It's on Tuesday evenings — outside work hours. Zero impact on sprints, deploys, on-call, or 1:1 cadence. The homework is ~1 hour/week of journaling-style work I do on my own time. If a sprint gets weird, the cohort accommodates real life.
There's a free workbook version at developereq.com/workbook — same content, self-guided. The cohort is the version where you do it with a small group of other engineers and get live feedback. The $500 is for the accountability and the network, not the content.
Most internal engineering training is technical (system design, language deep-dives, tooling). This is specifically the social/career-facing skills that internal programs almost never cover — because they're hard to teach in a generic format. The cohort uses live small-group practice, which is why it works.
It's built and run by an engineer (Kyle has 10+ years of AWS/SRE experience), not a generic leadership coach. The framework comes from solving the problem on actual engineering teams, and the metaphors and examples are dev-coded all the way through. Engineers stop tuning out the way they do during corporate "soft skills" trainings.
Plan B: pay yourself, expense after
If the budget process is slow or your manager wants to see results first — pay out of pocket and request reimbursement after Week 2 (when you have something concrete to show).
Most engineering managers will reimburse a $500 cohort once you can demonstrate it's shipping real artifacts (the incident card, the 1:1 template, the team readout). Frame it as: "I'm doing this anyway. If it delivers, I'd like to expense it."
Got the green light?
Three cohorts to choose from. Max 20 seats each.
Pick your cohort →DevOps Days attendees: code DEVOPSDAYS = $100 off.