Dedicated resources for engineering managers and software engineers.

This newsletter is all about bringing value to you. Below are the curated documents used to help hundreds of engineering managers and engineers.

Resources shared include:

For engineering managers:

  1. One on One template with individual contributors
  2. Checklist for (New) Engineering Managers: the checklist I wish I had
  3. Advocate and Inspire - Tech Lead Expectations to empower engineers to lead projects
  4. Narrative/Business Case for a Platform team used to create one
  5. Performance Review Example and Template for EMs
  6. Promotions Map for EMs to visualize promotions progress
  7. Oncall compensation data
  8. Checklist for growing a (junior-heavy) team
  9. Checklist for planning preparation for engineering managers
  10. Project reporting example for regular engineering project updates.
  11. Preparing for layoffs: a checklist
  12. Pragmatic Engineer job board special offers for subscribers: posting jobs for free, or with a discount


  • EM interview process
  • Software engineering interview process


  • Onboarding Overview
  • Onboarding Task List
  • Onboarding Email Example
  • Onboarding Checklist for Engineering Managers
  • Onboarding Check-In Questionnaire that many places use to check-in around the one-month timeframe


  • Resources to find great tech jobs: 100+ of the highest paying jobs, and 50+ places to find promising high-growth startups and a list of the best executive recruitment firms in tech
  • Writing goals and accountability document: to help making progress in becoming a better writer.

For software engineers:

  • A migration checklist
  • Incident Analysis Templates
  • Project reporting example
  • Performance Review Example
  • Work Log Template for software engineers
  • Team Standup Template

I do not suggest blindly copying any of these documents. Instead, use them as inspiration. They worked for me for my specific situations over the years. Your situation - business context, team structure, team dynamics - will be different, and you’ll want to tailor for this context. If you think they'll help: give it a go, iterate on them, and make them yours!

Consider creating your own “templates” for common situations you come across: and share them with your peers for feedback. This is how I created many of these documents: and I have always been surprised by the quality and quantity of helpful feedback received.

What are other documents, templates, or approaches that you'd find helpful? Please send a message or leave a comment.