Your First 90 Days: How to Make an Impact in a New Tech Role

The First 90 Days Matter

How you start a new role sets the tone for everything that follows. The best engineers we place approach their first three months with intention.

Month 1: Listen and Learn

Resist the urge to change everything immediately:

• Focus on understanding the codebase and architecture
• Map out who knows what – find the experts
• Learn the team's processes and why they exist
• Ask questions – lots of them
• Ship something small to build confidence

Month 2: Start Contributing

Now you can start adding value:

• Take on increasingly complex tasks
• Identify quick wins and low-hanging fruit
• Start forming opinions (but hold them loosely)
• Build relationships across the team
• Seek regular feedback from your manager

Month 3: Drive Impact

Time to step up:

• Own a significant piece of work end-to-end
• Propose improvements based on what you've observed
• Mentor newer team members if appropriate
• Establish yourself as the go-to for something specific
• Have a clear conversation about expectations and growth

Common Mistakes to Avoid

• Trying to change too much too fast
• Going heads-down and not building relationships
• Being afraid to ask "stupid" questions
• Waiting for permission instead of taking initiative
• Comparing yourself to people who've been there for years

Questions to Ask Along the Way

• "What does success look like in 90 days?"
• "What's the one thing I should focus on?"
• "How can I best support the team right now?"
• "What do you wish you'd known when you started?"

Final Thoughts

Your first 90 days aren't about proving you're the smartest person in the room. They're about building trust, understanding context, and setting yourself up for long-term impact. Be curious, be humble, and focus on adding value rather than making a splash.