You got the offer. Now comes the part nobody prepares you for: getting up to speed in a new codebase, a new domain and a new team, all at once. Here's a calm, practical plan for your first 90 days, broken into three phases, so you can ramp fast without burning out or trying to learn everything on day one.
By LearnHero · · 6 min read
You made it through the interviews, negotiated the offer and signed. For about a day, it feels great. Then the start date gets closer, and a new worry shows up: what if you can't get up to speed fast enough?
That worry is normal. A new tech job asks you to learn a codebase, a business domain, a set of tools and a whole team of people, often all in the same week. Most of us try to absorb everything at once and end up overwhelmed, or we keep quiet for too long because we don't want to look lost.
There's a calmer way. Your first 90 days in a new job go much better when you learn things in a sensible order and set small goals for each phase. Here's the plan we'd hand a friend starting a new engineering, product or data role.
Before day one: set yourself up
You don't need to study the company's entire stack before you start. But a little preparation goes a long way.
Rest. Starting tired makes everything harder. If you can, take a few days off between jobs.
Read what's public. The product, the docs, the engineering blog if there is one. Get a feel for what the company makes and who uses it.
Brush up on the obvious gaps. If the team uses a language or tool you haven't touched in a while, a few short sessions now will make week one easier.
Write down your questions. What you're curious about now is a good starting list for your first conversations.
The three phases at a glance
We find it helps to think of the first 90 days in three rough phases, each with a different focus:
Phase
Main focus
Signs it's going well
Days 1-30
Learn people, tools and context
You know who to ask
Days 31-60
Contribute and own small things
You ship without hand-holding
Days 61-90
Take on real ownership
Others start asking you
These aren't strict deadlines. Some roles ramp faster and some take longer. The order is what matters.
Days 1-30: Learn before you change
Your main job in the first month is to listen and learn. It's tempting to show your value by suggesting big improvements right away. Hold off. You don't yet know why things are the way they are, and there's often a good reason.
Meet the people first. Ask your manager who you should get to know, then set up short one-on-ones. Good questions to ask everyone:
What are you working on, and what's hard about it right now?
What do you wish you'd known in your first month here?
Who else should I talk to?
Get your environment working. Getting the code running locally and shipping one tiny change, even a typo fix, teaches you the whole path from your laptop to production. It's the most useful first step in onboarding as a new engineer.
Map the system. Sketch the main services, data stores and how requests flow between them, then ask a teammate to correct your drawing. It's the same skill we cover in system design interview prep, now pointed at a real system. You'll learn more from their corrections than from reading docs.
Learn the domain. Every company has its own words, customers and rules. Keep a running glossary of terms you don't recognize, and ask about them.
Days 31-60: Start contributing
By the second month, you have enough context to be genuinely useful. The goal now is to take on small pieces of real work and finish them well.
Own a small, well-scoped task end to end. Pick something with a clear finish, ship it, and follow it into production.
Review other people's code or work. It's one of the fastest ways to learn how the team thinks, and it builds trust.
Ask questions out loud. Ask in the team channel instead of in private. Others often have the same question, and it shows you're engaged.
Write down what you've learned. If onboarding docs were missing something, fill the gap. It's a useful early contribution that everyone notices.
This is also when you'll feel the pull to fix things you've noticed. Now's a reasonable time to start mentioning them, framed as questions: "I noticed we do it this way. Is there a reason, or would it be worth trying something else?"
Days 61-90: Take real ownership
In the third month, the goal shifts from learning to owning. You should be able to take on a meaningful piece of work with less guidance and start contributing to how the team decides things.
Take on a larger project, or own a part of one, from planning through launch.
Share an opinion in design discussions. You now have enough context for your view to be useful.
Help the next new person. Nothing tests what you've learned like explaining it to someone else.
Keep learning on purpose
The amount you'll learn in 90 days is enormous, and most of it gets forgotten if you only meet it once. A few small habits help it stick:
Keep a daily notes file. A few lines about what you learned and what confused you.
Review it weekly. Turn the shaky parts into questions and test yourself. Our guide on how to remember what you learn has a simple system for this.
Make a short learning plan for your biggest gap. If it's a new language, a new domain or a new part of the stack, a focused plan beats hoping it sinks in. Our guide to building a learning plan you'll actually finish shows how.
Check in with your manager at 30, 60 and 90
Don't wait for your first formal review to find out how you're doing. Ask your manager for a short check-in around each phase, and bring three questions:
What's going well, and what should I keep doing?
What would you like to see more of in the next month?
What does success look like for me by the end of my first six months?
These conversations build trust early, and they set you up for the long game. The habits that help you ramp, like keeping notes on your work and knowing what the next level looks like, are the same ones that help later when you're thinking about how to get promoted in tech.
A worked example
Say you've joined a payments team as a backend engineer, coming from a company that built internal tools. You know the language, but payments is new to you.
In the first month, you meet everyone on the team and a few people in finance and support, ship a small logging fix, and keep a glossary of payments terms. In the second month, you own a small bug fix that touches the refund flow and review a teammate's code each week. By the third month, you're leading a modest improvement to how failed payments are retried, and you've written the onboarding page you wished you'd had.
Nothing heroic. Just the right things, in the right order.
Your ramp-up is shaped by what you already know
No two new hires start in the same place. You might know the language but not the domain, or know the domain but not the stack. Generic onboarding can't account for that, so you end up sitting through what you know and guessing at what you don't.
That's why we built LearnHero to start from you: what you bring to the new role, and the specific stack, tools and domain you need to learn.
Use the 90-day plan above on your first day, or let us build a ramp-up course around your new role and what you already know.