Slow developer onboarding

A new developer takes months to become self-sufficient

New joiners ask senior colleagues, because the code does not explain itself and the tests that would act as a safety net are missing. The seniors answer, which leaves no time to make the code easier to read, and the next one asks even more. Onboarding stays slow for three reasons that add up: the code, the team’s practices, and knowledge that sits in a few heads.

Book a call

Does this sound familiar?

  • New joiners spend their first weeks reading code with no idea where to start.
  • Understanding one part of the system always means asking the same person.
  • Their first changes break something, because the rules to follow were never written down.
  • The documentation exists, but it describes a system that has since changed.
  • Every new joiner takes time from the senior colleagues who pair with them, and delivery suffers.

Where do new joiners get stuck?

A new joiner is self-sufficient once they can change the code and know straight away whether they have broken anything. Code that explains nothing and missing tests take that confidence away and push them towards the few people who know. That is where onboarding jams.

  1. The code does not explain itself

    Coupled modules, names that do not come from the domain and conventions that live only in the heads of people who were there, so you need a guide just to know where to begin. Documentation tries to fill the gap and drifts out of date quickly, whereas code with clear boundaries and names taken from the product can be read by someone seeing it for the first time.

  2. There are no tests to act as a safety net

    Without automated tests, a new joiner cannot tell whether their change has broken something, so they either proceed with caution or ask for confirmation at every step. Well-written tests also describe how the system is expected to behave, and they are the most up-to-date description a team can have.

  3. Knowledge sits in a few heads

    If only one person knows a part of the system, onboarding depends on how much time that person can carve out, and every new joiner takes that time away from their own work.

  4. People learn alone, one question at a time

    Too often, onboarding comes down to a few questions when the new joiner gets stuck. Pairing on real tasks, taking turns at the keyboard, passes on what no document contains: how to reason about that code and why certain choices were made.

What changes when new joiners become self-sufficient early

New joiners work on real tasks from the start, paired with someone who knows the code, and the tests tell them straight away whether a change has broken anything. There are fewer questions, because many answers are already in the code and the tests and no longer fall to senior colleagues.

When a position opens, the team asks in planning who will pair with the new joiner on their first real tasks, and delivery holds up while they learn.

Show us how a new developer joins today

We walk through the most recent arrival’s first months, then tell you plainly whether you need Technical Coaching in XP and TDD or whether the knot is in the code.

We use your data to respond to your request. Read our Privacy Policy.