What new hires notice

At one company, every planning meeting ran an hour over. I noticed by my second week and asked somebody about it.

"Oh, that's just how it is here," they said.

They sounded as though the meetings were weather. To me, still new enough to be irritated, they looked like a sign that priorities were unclear and nobody could close a decision.

That gap has stayed with me. A new hire notices the things everybody else has learned to step around.

Three weeks waiting for a decision

I wrote about codebase-first interviews a while ago. Letting candidates work with your real code reveals more than a whiteboard puzzle, and I still believe in it.

Even an honest interview gives a candidate only a few hours with the company. It's hard to see who can make a decision or how the team handles disagreement with leadership in that time.

I felt that more sharply in a job where my first three weeks were spent waiting for decisions. My manager needed approval from their manager, who needed alignment with a peer, who was away until the following month. By week four, I was already wondering whether I'd made a mistake in joining.

What "amazing culture" turned out to mean

In the 2/3 pattern, I describe organizations in terms of leadership, strategy, and team health. The weak part is often hard to hide from somebody who has just arrived.

Unclear ownership shows up as unresolved meetings. A drifting strategy appears when each person gives a different answer to "What are we building?" A struggling team can look friendly at first, until somebody offers the direct feedback promised in the culture deck and gets punished for it.

A friend joined a startup that sold candidates on its amazing culture. Within two weeks, she'd learned that the local meaning of "amazing culture" included not disagreeing with the founder. She then watched another new hire get criticized publicly for challenging a technical decision. She left after three months.

By the time somebody resigns, leaders sometimes say, "They never raised any concerns." It's worth checking what came up in their early one-on-ones or retrospectives before accepting that explanation. An unanswered concern gives a new hire little reason to raise the next one.

Ask while the observations are still fresh

I've started treating the first month as a source of feedback about the organization, alongside the usual work of helping somebody become productive.

The questions can be simple:

• What surprised you?
• What feels different from the interview?
• What has been harder than it should be?

If several new hires mention the same problem and nothing happens, the check-in becomes another meeting where a polite answer will do.

Some observations need context, and sometimes the new person has only seen part of the picture. You can explain why a meeting needs to run long or why a decision needs another person's approval. You might also find that nobody has a good reason anymore. I'd want to know that while the new hire is still willing to ask.