You join as tech lead of an existing team. What do you do in the first 90 days?

Summary

Listen and map for the first month, deliver one improvement the team already wants in the second, and set technical direction in the third — after you can describe the system's risks in the team's own words.

Longer Answer

Days 1–30: 1:1s with every engineer, the manager, product and key neighbouring teams, using the same questions (what's going well, what slows you down, what worries you); read recent incidents, design docs and the backlog; draw the system and a risk map. Days 31–60: fix one thing the team feels daily (flaky tests, slow deploys) together with them; share back what you heard and ask to be corrected. Days 61–90: propose two or three technical priorities tied to risks and business goals; agree them with product and the manager; publish them. Avoid proposing big changes before you understand why the current design exists.

Key Points

• Same interview questions for everyone
• One visible improvement the team wants
• Direction only after understanding constraints

Deep dive: Your First 90 Days as a Tech Lead

What interviewers look for

Humility and structure: learning before changing, early trust-building, and a concrete plan with milestones.

Red flags

• Arriving with a rewrite or technology change in week one
• No plan to talk to product or neighbouring teams