Starting a new job is exciting, but it can also be VERY overwhelming.
You want to make a great first impression, hit the ground running, and set yourself up for long-term success. So, how do you do that?
The key is to have a plan—not just for the first 30, 60, or 90 days, but for your entire first year.
See, you can approach your first year in one of two ways:
Option 1: Crush it for the first 30 days and then settle into mediocrity, doing just enough to get by.
Option 2: Crush it for the first 30 days and then keep that momentum going, making yourself indispensable by day 365.
Most people fall into Option 1. But Option 2 is the way to actually succeed.
Let’s break down what Option 2 looks like, month by month.
The first month: First impressions
Your first 30 days are all about establishing a solid foundation. During this time, you'll be learning your new role, getting to know your team, and making important first impressions.
So, you should focus on:
- Understanding your role and the expectations
- Getting to know your team and building relationships
- Learning the codebase and tech stack
- Making small contributions to the work
If you get these right, you’ll start off strong. We’ve actually covered this in detail in our previous blog post, "How to spend your first 30 days in a new tech role”. It’s worth reading for a thorough plan :)
The next 3 months: The 90 days start here
Now, conventional wisdom says the first 90 days are the most important, and while there's some truth to that, it’s not the complete story.
See, your first month is mostly about getting used to things. It’s the next three months where you start to focus on deep learning.
As you start contributing to projects, expectations will rise, and how you meet them will impact your growth. So, we’ll share key focus areas to keep you aligned with your team’s work and expectations.
Balance learning and doing
After your first month, you’ll be handling regular tasks. But don’t just focus on crossing them off your list—balance work with learning.
See, over the next three months, you’ll start to really understand your product. So, as you write new code, explore the codebase and learn why certain decisions were made.
“Once you have a good grip on the business, dive into the codebase and see what has been done, what could be done, and what can be improved. Before suggesting changes, ask questions about why things have been done the way they are. There are usually reasons behind the current setup that may not be visible at first glance.” —Keval Vora, Senior Software Engineer at SixSense
Now, if you're in the early stages of building a product, this will be easier. But in a big company, grasping the codebase could take over a year!
The best way to learn is to take on a variety of tasks that push you to explore different parts of the codebase. For example, if you work on a login issue one week, tackle product or order issues the next.
Of course, that might not always be possible. Set up KT (knowledge transfer) sessions with senior engineers to guide you through the trickier parts. Learn the best practices, architecture, and design patterns your team relies on.
Finally, make sure your code follows these patterns for smooth integration as you contribute.
“The architecture and design part is the most important aspect to focus on during this period. Continue collaborating with your team, sharing your knowledge, and learning from others.” —Bharadwaj Reddy, Senior Software Developer at Anarock Technology
Build horizontal relationships
Building strong relationships with senior engineers means they’ll invest more in mentoring you.
“Building teamwork and good relationships within the company is also very important. The first 3 months should involve building communication with your immediate team and other key people like DevOps, front-end, QA, etc.” —Anjalica Suman, Software Engineer at Thimblerr
See, your impact isn’t about the volume of code you write but the problems you help solve. That’s not possible without fully understanding your team’s problem-solving process.
So, as a junior engineer, seek opportunities to pair programs with seniors and request code or feature reviews.
Demand feedback ruthlessly
By now, your goal should be to write code that fits your team’s work.
“Once you have a good grasp of the business and communication norms, the focus for the next 3 months should shift to delivering high-quality code and work that seamlessly integrates with the rest of the team's efforts.” —Kaustumbh Jaiswal, Freelance Software Engineer at Thimblerr
To improve quickly, ask for feedback.
Many engineers just wait for feedback. Big mistake. Instead, set up monthly 1:1s with your manager or team lead, and genuinely want feedback.
Managers can tell if you really want to improve or if you’re just ticking a box.
When you meet, have a plan. There’s no single best way, but here are three things most engineers recommend checking:
- What are your manager’s expectations, and have you met them?
- Where can you improve?
- What can you do more than your present tasks?
Also, don’t just ask your manager. Get feedback from senior peers about your code quality. Ask them to review your best work and suggest improvements.
Finally, plan to use the feedback daily, weekly, and monthly.
The 6 months: Don’t slow down the progress
You’re no longer ‘the new person.’
From our conversations with engineers, the advice for the next six months remains the same:
- Focus on your work and keep learning.
- Take ownership of your tasks.
- Build strong relationships with your team and beyond.
So, in the next six months, we’ll highlight 2 key mistakes to avoid to maintain your progress.
Don't work aimlessly. Make a career plan instead.
As you start new projects, it’s easy to overlook your career goals. But if you want to grow as an engineer, you can’t just do your job and hope your career will grow on its own.
See, half a year is over. You understand your position. Now you need clarity on what exactly to do to move up in seniority in the next few years.
“The first six months are primarily about absorbing information and asking questions, while the latter half of the year is about applying that knowledge, making an impact, and setting yourself up for long-term success in the role.” —Zara Ahmed, Senior Software Engineer at Amazon
For this, you need a plan, and you can't set this alone. So, talk to your manager about it. The 6th month is the perfect time.
Say, for example, if you're an SDE 1 wanting to move to SDE 2 in the next 2 years, you can't do this by just writing good code.
To move up this quickly, you must exceed average performance. Understand your manager's expectations, which might include non-coding tasks. Show you're ready for new responsibilities to actually get them.
Your career growth is up to you. As a senior engineer we spoke to puts it well:
“The best advice I ever received in this area is that however wonderful your manager is, how great the team is, how well-structured the company is on metrics and everything else, no one cares about your career the way you do.” —Akhil Verghese, Senior Engineer at Google
Don’t be invisible. Build your brand instead.
If you stay committed and deliver your best work, you’ll take on important tasks on your team. But if the right people don’t know about it, your impact will stay limited.
“Do not expect that because you work hard, people will recognize it. A general impression may be all that matters in a really small company. But in anything bigger, even if your manager thinks you're the greatest engineer that has ever happened to your company, they need metrics to make your case for a promotion or anything else. If you don't give that to them, they will not be able to match what you want even if they tried.” —Akhil Verghese, Senior Engineer at Google
We're not asking you to brag or make a lot of noise. Instead, you should share your wins to benefit your team and the company. Did you solve a tough problem or ship a key feature? Talk about it.
If you’re a senior engineer, consider mentoring juniors by explaining your problem-solving approach.
Then, look for ways to impact beyond engineering.
Could you help marketing folks write better blog posts about your company's tech? Could you assist your manager in hiring strong junior engineers? Could you also hold knowledge transfer sessions for your juniors?
“Speaking of influence, this is a key aspect to focus on in this phase for accelerating your growth. It's not just about your contributions, but how you can positively influence the efforts of others around you - but be careful not to try influencing prematurely before you've built up sufficient context on the codebase and systems.” —Amey Telwane, Senior Software Engineer at Airbnb
Making it count
Navigating your first year in a new tech role can be tough. But having a solid plan can make it a rewarding experience. See, success in a new role isn't just luck; it's about careful planning and steady effort.
So, use this guide as your go-to resource. Keep coming back to it as you move through the challenges of your first year. The best engineers we have seen aren't just strong at the start—they keep growing, month after month.
So, your first year is just the start. Make it count.
