Fordel StudiosThe junior engineer joined on Monday. They were given a laptop, access to the codebase, an invitation to six Slack channels, and a ticket labeled "good first issue." By Wednesday, they were blocked on something nobody had documented. By Friday, they had asked the same senior engineer four questions that the senior engineer found annoying because they were "too basic." By month three, the manager had a quiet concern about whether this hire was working out.
The hire was working out fine. The onboarding was not working at all.
What Onboarding Actually Requires
Onboarding a junior engineer is a structured investment, not a self-guided tour. It requires a dedicated person — not "the team," a specific person — who is responsible for that engineer being productive in 90 days. It requires a written path: here is what you should understand in week one, here is what you should be able to do by week four, here is what a successful month three looks like. It requires explicit permission to ask questions without being made to feel that the question was beneath the asker.
Most teams have none of these. They have an expectation that capable engineers figure things out, combined with a culture where asking questions reads as incompetence. Junior engineers who are sharp enough to pick up on this culture stop asking questions. They stay blocked longer. They make worse decisions with less information. The manager concludes they are underperforming. The engineer concludes this company does not invest in people.
“You can tell a lot about an engineering culture by asking the junior engineers how they learned what they know. If the answer involves a lot of reading code late at night and piecing things together alone, the culture is eating its own seed corn.”
The Investment Calculus
A senior engineer who spends two hours a week for three months with a junior engineer is investing 24 hours total. If that investment produces a junior engineer who can independently own a feature by month four, the return on those 24 hours is hundreds of hours of productive work over the next two years. This is not a charitable act. It is a high-return investment.
Companies that do not make this investment are not saving the senior engineer's time. They are deferring a cost — the ongoing cost of a junior engineer who never fully ramps, who requires constant hand-holding instead of deliberate mentoring, and who either leaves after 18 months or stays indefinitely at a level of productivity far below their potential.
What Changes When You Fix It
When onboarding is structured, junior engineers ask better questions earlier, which means they learn faster. They understand why the system is built the way it is, which means they make better decisions when building new things. They feel like the company invested in them, which means they stay longer. The retention benefit alone pays for the onboarding investment multiple times over.
The simplest possible improvement: assign every new junior engineer one senior engineer who is responsible for their ramp. Not as an extra task — as a primary task, recognised in their performance evaluation. The accountability makes the investment real.