Starting a new job is exciting but also pretty scary.
Those first few weeks? They show people what kind of engineer you are and will be.
From our conversations with engineers, they all share a common fear: being judged quickly. After all, people form opinions VERY quickly.
So, in this blog, we'll help you make a great first impression by sharing key tips for planning your first month and the most common KPIs engineers focus on.
Cover the basics
In your first week, focus on understanding your team, their roles, and how things work.
There's no strict formula for this, but gather as much context as possible. People are usually more willing to help new joiners, even if they're busy, so make the most of this opportunity.
When introducing yourself, mention past projects and what you're excited to work on. Also, ask your teammates about their roles, business goals, and work so you'll know who to reach out to with questions.
"The initial month should be about understanding the business and what the company or team is trying to achieve at a higher level. Don't just narrowly focus on your role - take a step back and grasp the bigger picture first. What problems are you collectively trying to solve? Find that out first." —Amalan Thiyagarajah, Data Engineer at CertifyOS
Now, at larger companies, you might get a peer or buddy for onboarding. In startups, ask your manager to connect you with someone.
Finally, schedule a brief meeting with your manager to clarify your first month's expectations and understand the role.
Understand your tech stack
Next, start understanding the tech stack your team uses. If it's new to you, especially as a junior engineer, aim to get comfortable with it within a month or two.
You can start by asking your manager about the specific part of the product you'll be working on. Then, focus on the tech stack relevant to that area first.
Begin by setting up your development environment and get to know the frameworks, languages, and internal tools your team relies on. If needed, ask experienced team members for help. The quicker you're set-up, the sooner you can start learning.
The goal is to begin contributing to the codebase within a month, whether that means fixing bugs or adding small features.
"If you're a fresher entering the industry, the first thing is to grab the basics of whichever tool or technology you'll be using. Master the fundamentals, as it will make your life a lot easier going forward. You can skip the basics and get the work done, but you'll struggle in the future if you do that." —Meet Rayvadera, Senior Software Engineer at Optum
Set up your coding environment
By the end of the first 2 weeks, aim to have all your tools set up, full access to the codebase, and a solid understanding of the coding standards.
If you need setup guidance, we published a report with engineers' insights on IDEs and tools—take a look after reading this :)
Now, we've noticed that senior engineers typically start delivering by weeks three or four, while junior engineers need more time to ramp up. So, if you're a junior, don't struggle alone—it's normal to feel lost at first.
"For folks with more experience - the expectations are higher, and the ramp-up time is shorter. You're expected to know how to communicate, figure things out, and have some project management skills. They might give you a brief orientation, but you're expected to contribute as soon as possible." —Shivam Mathur, Freelance Software Engineer
On the other hand, senior engineers should focus on the bigger picture. Since you might be already familiar with the tech stack, spend a few days understanding how the whole system fits together.
Ask questions
In your first month, don't stress about having ALL the answers.
Most engineers suggest avoiding a 'know-it-all' attitude, as it leaves no room for your team to explain why things are done a certain way.
Ask questions strategically. Save them for your 1:1s with your manager—if those aren't scheduled, set them up yourself.
"You might not understand everything right away, but go through it all. Note down your questions and ask them during knowledge transfer (KT) sessions. Questions are always welcomed in good company. If you're asking questions, it shows you're learning. Don't hesitate to ask as much as you can." —Anjalica Suman, Software Engineer at Thimblerr
See, people are busy but generally happy to help—just ask the right person at the right time. And always check for new joiner documentation before reaching out about the codebase.
"Do your due diligence by reading knowledge documents and identifying who you can discuss questions with. Batch your questions together to save people's time, and do your research beforehand." - Akshay Khandelwal, Senior Software Engineer at Kognitos
Finally, the key focus areas for the first month
The KPIs for your first month will vary depending on your experience level.
However, from our observations, engineers often concentrate on two crucial areas: mastering the tech stack and building relationships with their team.
This dual focus helps you get up to speed technically while also integrating into the team culture.
Technical: Familiarize yourself with core technologies and start making meaningful contributions to project tasks.
Non-technical: Establish rapport with your manager and senior engineers through regular communication and collaboration.
Finally, after your first month, it's important to keep the momentum going and plan for the rest of the year. Check out this blog to discover the next key steps.
