What I think a new engineer’s first month should be for

A round red door set into a grassy hill at Hobbiton, with a garden and a birdhouse post in front

The first month of a new engineer's job is not for productivity. Teams that measure it that way get the month wrong twice. They get little useful work out of it, and they teach the new person that being seen to produce matters more than understanding. Nobody is productive in month one. The question is whether the month is arranged so they learn the right things.

A map of the system

Not the architecture diagram, which is a drawing of what someone intended. The map a new engineer needs is of what actually exists. Where the code lives, which parts are feared, what breaks when, and why that odd module is the way it is.

The first month should include deliberate time for this, not just a reading list. Walk through a request from the browser to the database with someone. Find out which parts of the system the team avoids and ask why.

A map of the people

The second map is who to ask. Every team has the person who knows the build, the one who knows the history, the one the product manager trusts, and the one who will answer a question at 6pm. None of that is on the org chart. A new engineer who has it can get unstuck in minutes.

So a manager owes a new hire specific introductions, this person for this kind of question. And the new engineer owes the team a willingness to ask, which some people need to be told is allowed.

How the team decides

The third is the hardest to teach because nobody thinks of it as a thing. How does this team make a decision. In the pull request, in a meeting, in a hallway, by one person who says so. What does disagreement look like here, and who ends it. A new engineer who gets this wrong will propose things in the wrong place and wonder why nothing happens. The only way to learn it is to watch a few decisions get made, so the first month should put the new person in the room, or the thread, where they happen.

One real thing shipped

The fourth ties the others together. Something small, real, and end to end, through the actual pipeline, into production, within the month. Because shipping is how the maps get tested. Every gap in the system map, the people map, and the decision map shows up as a question on the way to shipping, and the questions are the learning.

What the manager owes

The manager's part is to make the month deliberate instead of accidental. Block the time for the system walk. Make the introductions. Put the person in the decisions. Pick the first thing to ship, small enough to finish. And resist the pull to measure output, because the output of a good first month is a person who can be productive in the second.

The teams I have seen do this well treat the first month as an investment, not a cost to absorb. The difference shows in month six.

Photo source: https://photos.robertstowe.com/new-zealand