Be the GOAT New Hire You Deserve To Be
My tips for fast onboarding
Let me tell you what most engineers do when they join a new team.
They spend the first two weeks setting up their dev environment and reading wikis. They sit through five “getting to know you” 1:1s where everyone is vague about what they actually work on.
They ask their manager for a project that’s “well-scoped for onboarding.”
They take careful notes.
They wait.
Six weeks in, they’ve shipped nothing. Their manager has no strong opinion of them. The interesting projects are already assigned.
I’ve watched dozens of engineers make this mistake.
And I’ve figured out what separates the people who look like rockstars by month three from the people who are still “ramping up” at month six.
It’s not intelligence. It’s not even experience. It’s a mindset shift most people refuse to make.
The uncomfortable truth about joining a new team
Here it is:
You just joined. You are a tool to be used. Be serviceable.
I know that sounds harsh. Stick with me.
When you’re new, you have no credibility, no context, and no leverage. You can’t negotiate for the interesting projects yet. You can’t push back on bad decisions. You can’t say “I’d rather work on X.”
The fastest path to doing whatever you want is to first prove that you execute. Fast, reliably, on whatever is needed. No ego.
This is not a permanent state. It’s a sprint that buys you everything that comes after.
Weeks 1–2: Map people first, systems second
Your first instinct will be to dive into the codebase. Resist it.
Start with people. Who are the 20% doing 80% of what matters? Not the most senior by title — the ones whose names come up in every design doc, whose PRs everyone reviews carefully, who get pulled into incidents.
Find them. Read their PRs. Understand not just what they work on but why. What’s the business problem? What are the tradeoffs they’re navigating?
Then map the systems. But be ruthless: not everything deserves investigation. Label the non-critical parts as black boxes and move on. If you go down every code path you will never finish onboarding. Use judgment.
The output of week two: a clear mental model of who matters, which systems matter, and where the gaps are.
The mindset shift is free. Weeks 3–8 — where engineers either break away from the pack or disappear into the background — is below.