We follow up with candidates at thirty, sixty and ninety days after they start. The pattern in those conversations is consistent: the people who struggle are almost never the ones who lacked technical ability. They are the ones who spent three months waiting to be told what mattered.
Weeks one to two: map the room, not the codebase
You will be given documentation and access. What you will not be given is the informal map: who actually decides things, whose review unblocks a release, which meeting is where scope really changes.
Ask your manager one question in week one — “who should I be building a relationship with in my first month?” — and then have short conversations with every name. This reads as initiative and it saves you a quarter of confusion.
Weeks three to six: ship something small and visible
New starters commonly aim too big. A meaningful contribution in month one is not the migration nobody has attempted; it is a small, complete, visible improvement — a flaky test fixed, a runbook that was wrong and now is not, a report that took an hour and now takes a minute.
Small and finished beats large and pending. It establishes that work assigned to you comes back done, which is the only reputation that compounds.
Weeks seven to twelve: get the standard in writing
By now you should be able to answer, concretely: what does good look like in this role at six months? If you cannot, ask directly. “What would make you say this hire went well?” is not a naive question — most managers appreciate it, and a surprising number have never articulated it.
Write the answer down. It becomes the agenda for every check-in and, later, the evidence in your review.
The mistake that costs the most
Staying quiet when stuck. There is a window — roughly the first month — where “I do not understand this yet” costs you nothing. After that, the same admission becomes expensive. Use the window.
If it genuinely is not working
Sometimes the role was mis-sold, or the team changed under you. Say so early, to us as well as to them. A conversation at week six usually has options; the same conversation at week twenty is a resignation.
