Your First 90 Days in a New Job: A Practical Plan

The offer letter was the hard part, you might think. In truth, the first three months decide a lot: how your manager rates you, what work you get, and whether you are seen as someone who learns fast.

Here's a plan you can follow even if your company gives you no onboarding at all.

• Confirm logistics: start time, documents to bring, laptop and access, who your buddy is.
• Read about the team and product. Use the company site, recent news and any public docs.
• Prepare a short introduction about who you are, in 30 seconds.
• Settle personal admin: relieving letter and experience letters from the last employer, EPF/UAN number and bank details. See notice period guide if your last exit isn't fully closed.

The aim is to understand, not to impress.

• Ask your manager for a written list of priorities for your first three months.
• Learn the product from a user's point of view. Use it, break it, read support tickets.
• Read documentation, past decisions and recent project notes.
• Set up your environment fully. Note each step you had to figure out and fix the docs later, which is an easy early contribution.

• Schedule short intro chats (15 to 20 minutes) with teammates, adjacent teams and your manager's manager if appropriate.
• Ask each person: "What does your team do? What would you want me to know? Who else should I talk to?"
• Learn the unwritten rules: how people communicate, when meetings happen, how decisions are made, how quickly people expect replies.

1. What does a good first 90 days look like?
2. What are the team's biggest problems right now?
3. How do you prefer to get updates, and how often?
4. How is performance judged, and when is the probation review?
5. What should I avoid?

Write the answers down and share a short summary back. It shows that you listened, and it prevents misunderstandings.

Asking questions is expected. Do it well:

• Try for 15 to 20 minutes first.
• Then ask with context: "I'm trying to X. I tried Y and Z. I'm stuck at W. Can you point me in the right direction?"
• Keep a notes file of answers so you don't ask twice.

The same habit helps in technical work. For a method, see how to debug any bug.

By now you know enough to start doing real work.

• Pick up a small, well-defined task and finish it well. A completed small task beats a half-finished big one.
• Deliver one visible win by day 60: a fixed recurring issue, a better document, a small automation, a cleaned-up process. Make sure your manager sees it, without bragging.
• Communicate proactively. Share progress before people ask. Flag risks early. "I'm blocked on X, and here is what I need" is much better than silence.
• Be reliable. Meet the deadlines you give. If one will slip, say so as soon as you know.

Don't wait for the formal review. Ask: "What's one thing I'm doing well, and one thing I could improve?" Then act on the answer and tell them you did. People remember someone who takes feedback well.

Now move from helping to owning.

• Take responsibility for one area, even a small one, such as a module, a report, a process or a client relationship.
• Suggest an improvement with a short, evidence-based proposal. Keep it modest. You're still new.
• Set goals for the next quarter with your manager.
• Build your network beyond your team. Other teams' goodwill makes your work easier.
• Review your 90 days. What did you learn? What do you need next?

Most companies in India have a probation of 3 to 6 months. During it, notice periods are often shorter and confirmation depends on a review.

• Know the criteria. Ask what confirmation depends on.
• Get the review date in your calendar.
• Keep a log of your work: what you shipped, problems you solved, feedback received. It's useful for your review and for your next resume (resume guide).
• Read your offer's probation terms, including notice, benefits and leave.
• Ask early if something is unclear. Surprises at the end are usually from conversations that didn't happen at the start.

• Saying "at my old company we did it this way" repeatedly. Learn why things work as they do before suggesting changes.
• Trying to change too much too fast.
• Staying silent when stuck.
• Ignoring the soft side: greetings, thanks, helping teammates.
• Overworking from day one. You can't sustain it, and it sets expectations you'll struggle to meet.
• Gossip and taking sides. You don't yet know the history.
• Neglecting your finances. A new salary structure can surprise you. See CTC vs in-hand salary.

Sometimes you'll realise within weeks that the role isn't what was described. Don't panic and don't quit on impulse.

1. Give it a fair chance of a few weeks.
2. Raise the mismatch with your manager with specifics.
3. Keep your skills and resume updated.
4. If nothing changes, read when to switch jobs before you decide.

Every Friday, spend ten minutes writing:

• What I learnt this week
• What I shipped or helped with
• What confused me
• Who I should talk to next week

By day 90 you'll have a record that makes review conversations easy.

Be punctual, reliable and curious. Ask good questions, finish what you start and thank people who help.

Write your own 30-60-90 plan and ask for feedback on it. Many managers appreciate this.

Ask about how performance and growth are judged in the first weeks. Save compensation discussions for the review cycle unless the offer terms said otherwise.

Terms depend on your offer letter and company policy. Read them, and ask HR if anything is unclear.

It's common. Keep your log of wins, ask for feedback and remember that being new means not knowing things, which is expected.

Employment terms such as probation and notice periods differ between companies. Always check your offer letter.