The onboarding document that actually works
Most onboarding docs are written by people who already know. Here is what a new engineer needs on day one, in order.
tech, developers, and the code underneath
12 pieces tagged engineering-management,
from April 25, 2025 to July 13, 2026.
Most onboarding docs are written by people who already know. Here is what a new engineer needs on day one, in order.
The role is genuinely ambiguous and that ambiguity is load-bearing. An attempt at a concrete description.
Internal platforms fail for predictable reasons. The successful ones share four properties.
The entry-level pipeline is breaking in a way that will be expensive in five years. Some of the fixes are cheap.
Not the hourly rate. The fragmentation. Here's why a 30-minute meeting costs four hours.
Refusing work badly is a career problem. Refusing it well is one of the most valuable things a senior engineer does.
If your rotation is painful, that's information about your architecture, not about your people's resilience.
Every team says docs matter. Almost none of them assign an owner, a budget, or a metric.
Most incident reviews produce a document and a ticket that never gets done. Here's the difference.
Every hiring process eventually optimizes for the wrong signal. The current one has a new failure mode.
You are not bad at predicting the future. You are bad at explaining uncertainty to people who want a number.
"Prove AI can't do this job" as a requirement before headcount. A reasonable policy with an unreasonable failure mode.