The Engineers Who Thrive at Month 6 Do Something Different in Week 1

You accepted the offer. You served your notice period. You showed up on day one. Now what? Most onboarding advice reads like a corporate manual. I want to give you the real version - the stuff that determines whether you're thriving at month 6 or quietly updating your resume again.

Week 1: Absorb, don't perform

Your instinct will be to prove yourself immediately. Resist this. In your first week, your job is to understand the landscape - not to change it. Pull the codebase and read it. Sit in on meetings and listen. Take notes on things that confuse you, not to raise them yet, but to build a map of what you don't know.

"The best new hires are sponges for the first two weeks and contributors by week three. The ones who try to be contributors on day one usually become problems by month two."

Engineers who try to make an impact in week one almost always step on something they don't understand. They refactor code that has a hidden reason for being messy. They suggest tool changes without knowing why the current tool was chosen.

Week 2–3: Map the people, not just the systems

Every company has a formal org chart and an informal power structure. They're rarely the same. Figure out who actually makes decisions - it's not always the person with the Lead or Manager title.

Key relationships to identify early

• Your manager: how do they prefer to communicate? What does "good work" look like to them specifically?

• Your onboarding buddy: use them - ask the dumb questions, that's what they're there for

• The person who knows where everything is: every team has someone who knows the history of every technical decision and every workaround - find them

• Your skip-level manager: knowing their priorities gives you strategic context your peers might lack

Month 1: Land your first win

By the end of your first month, you should have shipped something. Not something big. Something small that works. Fix a bug from the backlog. Improve the documentation that confused you. Clean up a flaky test. The goal isn't the output - it's the signal: this person can navigate our codebase, understand our processes, and deliver working code. That signal buys you trust, and trust buys you more interesting work.

One mistake I see often: new hires pick too ambitious first tasks. They volunteer for the complex migration because they want to prove seniority. Then they struggle because they don't yet understand the system, and by week 4, the team starts worrying. Start small. Earn the big stuff.

Month 1–2: Have a conversation with your manager

Around the 4–6 week mark, schedule a focused 1-on-1. Not the regular weekly sync - a dedicated conversation about how things are going. Ask directly: "How am I doing? Is there anything I should be doing differently?" Most managers won't give you this feedback unprompted. They'll wait until the first review cycle, by which time small issues have calcified into bigger ones.

Month 2–3: Find your lane

By month two, you should have a sense of where you can add the most value. This isn't always the area you were hired for - sometimes the team's needs have shifted. Talk to your manager: "I was hired to work on the recommendation engine, but I've noticed the data pipeline is a bigger bottleneck right now. Would it be useful for me to spend some time there?" This kind of initiative is what separates people who get promoted in 12–18 months from those who stay at the same level for 3 years.

Mistakes that haunt you

• Talking too much about your previous company - "at my last company, we did it this way" is the fastest way to annoy your new colleagues

• Silently struggling - nobody judges a new hire for asking questions; they judge you for wasting a week on something a teammate could unblock in 10 minutes

• Overcommitting - better to do two things exceptionally than five things poorly

• Not building relationships outside your immediate team - your broader network inside the company is what makes you effective and resilient long-term

The 90-day gut check

At the end of three months, ask yourself: Am I learning? Do I respect my manager and teammates? Is the work what I expected? Am I excited to be here on most days? If the answers are mostly positive, you're in good shape. If mostly negative, it's worth having a direct conversation with your manager. Three months is early enough to course-correct.

The first 90 days aren't about impressing everyone. They're about building the foundation for the next 3–5 years of your career at this company. Play the long game.