Onboarding: the first 30 days set the tone

You did the search. You took the offer. The job is yours. Now don't squander the first month — it sets a calibration about you that takes a year to undo, in either direction.

What people remember from your first 30 days

Three things, with weights roughly in this order:

1. Did you ship something visible.Doesn't matter what — a documentation update, a small bugfix, a cleanup PR. People notice that you operate.
2. Were you easy to work with. Did you ask reasonable questions, accept feedback gracefully, show up on time. The bar is low; the cost of missing it is high.
3. Did you understand the context. Did you ask about why decisions were made, not just what they were. People remember the curious newcomer who got the why.

Not on the list: how technically brilliant you were on day 12. Nobody's evaluating you on technical depth in month one. Don't fake it; don't over-deliver to the point of burnout. Settle in.

The four habits that compound

1. Take notes for yourself

Day-one journal. Every meeting, write down: who was there, what was discussed, what you agreed to do. Re-read weekly. By month 3 you've internalised the org chart, the vocabulary, and the unspoken rules — without having to ask anyone.

2. Schedule 1:1s with peers, not just your manager

First week: book 30 minutes with everyone on your immediate team. Second week: book 30 minutes with one person from each cross-functional team you'll work with. Open with “tell me about what you do and how it connects to what I'll be doing.”

Effort: ~10 hours of meetings. Payoff: a network inside the company that pays back for the rest of your time there.

3. Ask “why does this exist” before “why is it like this”

Newcomers reflexively ask “why isn't this code refactored / this process automated / this meeting cancelled.” Sounds like criticism. Reframe: “help me understand the history — what problem does this solve?”

Same information, different reception. The original team gets to share context; you get to actually hear it. After 90 days you've earned the right to suggest changes.

4. Ship one small thing in week one

Doesn't matter what. A typo fix in a README. A test coverage improvement. A two-line bug. The point is the social signal, not the code. Your manager has decided in the first week whether you're going to be easy to work with; a small ship is the easiest way to confirm yes.

Two mistakes that don't compound

The over-promise

Manager asks how long you think a project will take. Instinct: under-quote to look fast. Reality: every miss compounds. Pad your estimates by 50% in month one. You don't have the context to estimate accurately, and the cost of being late is much higher than the cost of being conservative.

The criticism in week three

You see a process that's clearly wrong and you say so in a meeting. The team has worked on this for two years. They've had the same observation, plus context you don't have. The critique reads as oblivious.

Wait. Hold the observation. Bring it up at month 3 framed as a question, not a critique: “I've been wondering about X — how did the team end up here, and is there appetite to revisit?”

The 30-day check-in

End of month one, ask your manager for direct feedback. “What's landing well, what should I be doing differently.” Specifically that question, in those words. Don't ask “how am I doing” — you'll get reassurance, not feedback.

Most managers will give you something honest if you frame it actionably. Acting on that feedback in month two is what separates the “solid hire” from the “promising hire” in a manager's head.

The thing to remember

You spent months grinding through applications and interviews to land here. The first month is the easiest opportunity you'll have to set the tone. Spend it on relationships and curiosity, not on proving yourself. The proof comes naturally over the year that follows.