The First 90 Days Determine Your Next Three Years

You walk into a new job with goodwill you didn’t earn yet. That goodwill has a shelf life.

Most engineers don’t realize this. They spend the first few weeks getting oriented, learning the codebase, figuring out where the bathrooms are. By the time they feel ready to contribute meaningfully, three months have passed. And the people who hired them have already started forming opinions.

The first 90 days of a new engineering role aren’t an orientation period. They’re an audition. The difference is that nobody told you that.

I saw this pattern over and over at Facebook. We’d hire someone strong - someone who’d performed well in interviews, had solid experience, came in with good references. Six months later, the hiring manager would be expressing concerns. The person was technically capable but hadn’t figured out how to operate inside the organization. They were doing good work in isolation. They weren’t having impact.

The engineers who accelerated through those early months understood something the others didn’t: the first 90 days don’t just determine how you feel about your new job. They set the trajectory for everything that comes after.

The Mistake Most Engineers Make

The default strategy for starting a new engineering role is to stay quiet and learn. Don’t step on toes. Ask lots of questions. Understand the codebase before you touch it.

This is reasonable advice taken too far.

There’s a version of “learning the codebase” that looks like humility but is actually risk aversion. You’re not contributing because you don’t feel ready. You don’t feel ready because you haven’t shipped anything yet. You haven’t shipped anything because you’re waiting until you feel ready. This loop can run for months.

The engineers who thrived in their first 90 days at Facebook were the ones who started delivering early - not perfectly, but visibly. They asked clarifying questions and then acted on the answers. They made decisions with incomplete information rather than waiting for certainty that never came.

Learning and contributing aren’t sequential. The best early-tenure engineers did them simultaneously.

What Actually Matters in the First 30 Days

Before you can have impact, you need to understand the landscape. Not perfectly - just well enough to orient yourself.

There are three things worth mapping in your first month.

How decisions actually get made. Every organization has an official decision-making process and an actual one. The official process involves design docs and approval chains. The actual process involves whoever has the informal credibility and whoever the team trusts on a given type of problem. Find out who those people are. Not to work around them - to work with them.

What success looks like for your team right now. This sounds obvious, but most new engineers don’t ask it directly. “What’s the most important thing this team needs to accomplish in the next quarter?” is a question worth asking your manager in your first week. The answer tells you where to focus your energy and where your early contributions will have the most signal value.

Where the pain is. Every codebase has sections nobody wants to touch. Every team has the recurring problem they’ve accepted as permanent. New engineers have fresh eyes - you’ll notice things veterans have become blind to. Write them down. Some will be real opportunities. Some will be things you don’t fully understand yet. Revisit the list at day 60 and see which is which.

The 30-60 Day Window: When to Stop Watching and Start Doing

This is where most new job strategies fall apart.

By day 30, you have enough context to contribute. Not enough context to lead, but enough to be useful. The mistake is waiting for the moment when you have enough context to be certain. That moment doesn’t come. The engineers who waited for it were still waiting at month four.

The 30-to-60 day window is when you should be shipping small things, taking on well-scoped tasks, and starting to form opinions you’re willing to share. Not loudly - but not silently either.

One specific thing that worked at Facebook: new engineers who added value in their first 60 days almost always did it by picking up something that was falling through the cracks. Not the prestigious project. The annoying bug that had been open for eight months. The runbook that was out of date. The test coverage gap everyone knew about.

This isn’t about being a martyr. It’s strategic. Low-visibility problems are exactly where a new engineer can have real impact without stepping on anyone’s turf. You fix something that mattered. You learn how the systems actually work. You demonstrate that you show up to do the job, not just the interesting parts of the job.

What Days 60-90 Are Really For

By day 60, you’ve shipped something. You know how decisions get made. You have a clearer picture of what your team needs.

Now is when you start operating at your actual level.

This means forming and expressing technical opinions. Not steamrolling the team with your experience from your last company - that’s one of the fastest ways to lose credibility in a new role. But engaging seriously with technical decisions, pushing back when you have a real reason to push back, and contributing your perspective when it’s relevant.

It also means starting to build the relationships that will matter over the next few years. Your manager, obviously. But also the senior engineer who knows where all the bodies are buried. The PM you’ll work with most closely. The engineer on the adjacent team whose work intersects with yours.

At Facebook, the engineers who had the strongest first years almost always had a strong internal network by the end of their first 90 days. Not because they were politically savvy - most of them weren’t thinking about it consciously. They’d just spent three months showing up, delivering, and being easy to work with. The network was a byproduct.

The Thing Nobody Tells You About Goodwill

Here’s the part worth sitting with.

When you start a new engineering job, you have a reserve of goodwill from the hiring process. The team wanted you. They’re rooting for you. They’re inclined to interpret your early work charitably.

That goodwill doesn’t last forever, and it doesn’t transfer. You have to convert it into something else - a reputation based on actual delivery, actual judgment, actual relationships.

The engineers I watched struggle in their first year weren’t bad engineers. Most of them were technically strong. What they hadn’t figured out was that starting a new job isn’t just about learning a new codebase. It’s about establishing yourself as someone the team depends on.

The first 90 days are when that happens - or doesn’t.

The good news is that the bar isn’t that high. Show up. Deliver small things consistently. Ask questions and act on the answers. Find the pain and reduce it. Form opinions and share them carefully.

Do those things for 90 days, and the next three years take care of themselves.

If you’re heading into a new role after a job search and want the complete system - resume to offer - the SWE Bundle has both the resume and interview guides for $78.