A lot of companies treat onboarding like an HR task.
For candidates, that is usually the first mistake.
Because in tech, bad onboarding does not just make your first few weeks awkward. It slows delivery, creates dependency, and tells you very quickly how well the company is actually run.
In Dutch tech, especially in lean teams, people are often expected to get up to speed fast. That is fine when the environment is clear.
It becomes painful when access is delayed, documentation is weak, and nobody really has time to guide you properly.
That usually leads to the same pattern:
- too much context lives in people’s heads
- access to systems takes too long
- basic setup is inconsistent
- new joiners depend on the same two or three people for everything
- early mistakes happen because expectations were never made clear
For candidates, this matters because bad onboarding is rarely just a first-month issue. It often reflects a bigger problem underneath: weak internal structure.
Well-run teams do not need everything to be perfect. But they usually have the basics in place. People know how new joiners get set up, where key information lives, and how to get someone productive without unnecessary friction.
If a company cannot onboard properly, it usually struggles in other areas too.
Why this should matter before you sign anything
- How long does onboarding usually take before someone is fully effective?
- What is already documented, and what still depends on team knowledge?
- What tends to slow new joiners down most?
One last thing worth keeping in mind
A difficult first few weeks can happen anywhere.
But if the whole setup feels improvised, that is not just onboarding.
That is the company showing you how it operates when basic things need to work.
