Your First 90 Days in a New Job: A Fresher's Guide

Before you start, reread your offer letter. Your probation period, notice period, working hours and leave policy are all in there, and knowing them now spares you awkward questions later. If a clause confused you when you signed, our guide on how to read an offer letter explains the common ones.

Week one: first day at work tips

Expect week one to be mostly paperwork and setup. That's normal.

On day one, carry everything HR asked for: original certificates, ID proof, PAN card, bank details, passport photos, and the signed offer letter, plus photocopies. One missing mark sheet can hold up your joining formalities by days.

Laptop, email and system access take time to arrive. At a large company in Bengaluru or Pune, a new joiner can spend the first few days in induction sessions before touching real work. At a 25-person firm in Indore, you might get a task by lunch. Neither is a bad sign.

What to do in week one

Learn names: your manager, your buddy if you've been given one, the people on your immediate team, and whoever handles IT or admin. Write each one down with what they do.

Set up properly: email signature, calendar, the team's chat tool, shared drives. Ask which tool the team uses for what, because plenty of teams have an official tool and a different one they actually use.

Start a work notebook: paper or a document, either works. Every login, process step, acronym and instruction goes in it. You'll be told a lot in week one and you'll forget half of it.

Have a first conversation with your manager: ask what a good first month looks like for you, how they like to be contacted, and who to go to when they're busy.

Don't try to impress anyone yet. Be on time, be pleasant, pay attention.

Month one: learning the systems

Real tasks start arriving around week two or three. This is when freshers either settle in or start to struggle, and what separates them is how they learn, not how clever they are.

Learn how work moves

Every team has its own system: where tasks come from, who approves what, where files live, how things get named. A BCom graduate joining an accounts team in Kolkata might find that every invoice passes through three people before it's posted. A CSE graduate on a product team in Gurugram has to learn how a code change gets reviewed and deployed. Understand the flow before you try to change any part of it.

Go through the old emails, documents and tickets your team shares with you. They show you how things really get done.

How to ask good questions

You'll need to ask a lot, so learn to ask well.

Try first. Spend 15 to 20 minutes searching the shared drive, past emails or your notes, and then ask with context:

"I'm updating the vendor report. I found last month's file in the shared folder, but the GST column is calculated differently in two tabs. Which one should I follow?"

Someone can answer that in one line, and it shows what you've already tried. Now compare it with "How do I do the vendor report?"

Group your small questions. Five separate pings in an hour interrupt someone five times; one message with three questions interrupts them once.

And never ask the same thing twice. That's what the notebook is for.

Writing work emails

In Indian workplaces, email still carries most formal communication, especially with clients and other departments. A few habits make yours easier to read.

Put the point in the subject line. "Vendor report for October: draft for review" tells the reader what's coming; "Report" doesn't.

Open with what you need and give the background after. Keep it short. Use the person's name and a plain greeting. "Dear Sir" suits a client but sounds stiff to a teammate.

Hit reply-all only when everyone on the thread needs your answer. Check attachments, and read every email through once before you send it, out loud in your head if that helps.

Meetings

For the first month you'll mostly listen in meetings, and nobody minds. Take notes. When you're given an action item, repeat it back at the end ("So I'll send the updated sheet by Thursday?") so nobody's confused.

Say a meeting runs in English and you follow most of it but not all. Don't nod along. Ask your buddy afterwards. A missed instruction in week three is easy to fix. Two days spent on the wrong task isn't.

Month three: how to succeed in your first job

By the end of month three your manager has made up their mind about you. Many companies hold probation reviews around this point, so find out where you stand before the review, not during it.

Ask for feedback early and often

Don't wait for the formal review. Once you've finished your first real piece of work, ask your manager directly:

"Could you tell me one thing I did well on the onboarding tracker and one thing I should do differently next time?"

Ask something specific and you'll get a specific answer. "Any feedback?" mostly gets you "All good, keep it up," which tells you nothing.

Take criticism with a thank you, ask a clarifying question if you need one, and then show the change in your next task. Don't argue on the spot. If the feedback felt unfair, raise it calmly a day later, with facts.

A short check-in with your manager every two weeks or so keeps small problems small. Bring a list of what you've finished, what's stuck and what you're unsure about.

Become reliable before you become impressive

Plenty of freshers try to stand out with big ideas in month two. Managers notice something else first. Do you deliver what you said you would, on time, without being chased? If a deadline is going to slip, tell them early and give a new date. That habit earns you more trust than any presentation.

Once you're reliable, offer to take something extra on: documenting a process nobody has written down, sorting out a messy shared folder, or helping the next fresher who joins.

Tips for freshers at work: early mistakes to avoid

These come up again and again in the first three months.

Staying silent when stuck: a mechanical engineering trainee at a plant near Chennai who doesn't understand a drawing and guesses creates a far bigger problem than one who asks. So ask.

Treating chat like texting a friend: professional chat is still work. Write full sentences and skip the slang. Never send "hi" on its own and wait; put your question in the first message.

Comparing packages and complaining: your batchmate's offer is none of your business at work, and griping to colleagues about pay travels fast.

Over-promising: saying "I'll have it done in an hour" about a task you've never done. Give yourself a realistic time, then finish early.

Ignoring the boring rules: attendance, leave approvals, timesheets, data access. They feel minor. Slip on them during probation, though, and you start out with a bad record.

Posting about work online: keep screenshots, client names and internal details off social media, even in a casual post. Most companies have a policy on this, and breaking it can cost you the job.

First job tips as a 90-day plan

Print the table, stick it in your notebook, and check yourself against it every Friday.

Still looking for that first role? Our Jobs listings carry fresher openings.