Career guide
First 90 days in tech: how to start strong in your new role
Your first 90 days in a tech role set the tone for everything that follows. Learn the priorities, the mistakes to avoid, and the habits that will make you a trusted team member fast.
The first 90 days are different from everything else
This is the only time you will have beginner’s curiosity and institutional permission to ask basic questions simultaneously. Use it. The questions you do not ask in the first 30 days become awkward to ask in month 6.
Listen and learn
Your primary job is to understand. Not to fix things, not to suggest improvements, not to ship anything significant.
Attend every meeting you are invited to. Take notes obsessively. Ask who makes decisions about what.
Schedule 1:1s with everyone you will work with — engineering, design, data, stakeholders.
Learn the product by using it deeply as a user before you work on it as a professional.
Proposing major changes to how things work. You do not yet know why things are the way they are.
Contribute and connect
Now start contributing. Ship something small. Finish a task end-to-end.
Start building relationships beyond your immediate team. Know who the influential people are and how they prefer to communicate.
Identify the unwritten rules: How are decisions actually made? What does 'done' mean here? Who do you need to consult?
Ask your manager: 'What would make me obviously successful in this role by month 6?'
Own something
By day 60, you should be owning at least one thing end-to-end — a feature, a process, a reporting area.
Begin identifying where you can add value beyond your job description. Not by doing more work — by doing important work.
Start giving feedback, not just receiving it. Participating in retros, offering opinions in reviews, asking hard questions in planning.
Mistakes that derail the first 90 days
Coming in as the expert
Even if you have more experience, showing it before you have earned trust creates resistance.
Going quiet
New team members who disappear become invisible. Presence matters — especially remote.
Skipping the relationship building
Tech roles are collaborative. The people who succeed build relationships deliberately.
Not asking for feedback early
Waiting for the 6-month review to hear how you are doing means six months of potentially going in the wrong direction.
The questions every new team member should ask in month 1
These questions signal curiosity, ambition, and self-awareness — and the answers will orient everything else you do.
What does success look like for this team in the next 6 months?
What is the biggest challenge the team is facing right now?
What do you wish the last person in this role had done differently?
What is the most important thing I can learn quickly to be useful?
Prepare for your tech interview
Land the role first — then ace the first 90 days. Practice the questions that actually get asked.
Prepare for your tech interview