Your First 90 Days at Work in India: What College Didn't Teach You

Nobody Tells You That Your First Job Will Feel Like a Completely Different Planet#

You aced the interview. You got the offer letter. You posted on LinkedIn with the caption "excited to announce" and got 200+ likes. Your parents are proud. Your relatives finally have something to say about you at family gatherings.

And then Day 1 happens.

You sit at your desk, open your laptop, and realize you have no idea what you are supposed to do. Your manager is in a meeting. The person sitting next to you is wearing headphones and looks busy. You have access to Slack channels with names that mean nothing to you. Someone sends you a calendar invite for a "sync" that is apparently different from a "meeting." Your onboarding document is 47 pages long and reads like it was written by a committee of lawyers.

Welcome to corporate India. Everything is different here, and college did not prepare you for any of it.

We surveyed 150 Indian professionals who started their first job within the last 3 years. Engineers, MBAs, designers, analysts, across service companies, startups, product companies, and MNCs. The responses were remarkably consistent: the first 90 days were disorienting, and the hardest parts had nothing to do with technical skills.

This guide covers the unwritten rules of corporate India that nobody teaches in college. Not the inspirational stuff. The practical, sometimes uncomfortable, always useful reality.

Week 1: Everything Feels Wrong (And That Is Normal)#

Day 1 Survival Guide

What actually happens on Day 1 at most Indian companies:

At a service company (TCS, Infosys, Wipro, etc.): You are part of a batch. There are 50 to 500 other freshers starting with you. The first day involves ID card photos, laptop distribution, HR paperwork, and maybe a welcome presentation by a senior VP you will never see again. You feel like a number. That is because, at this stage, you are.

At a startup: You walk in and someone (maybe the founder, maybe an HR person, maybe the office admin) shows you your desk. There might be a brief intro to the team over lunch. By afternoon, someone drops a task in your lap. At startups, onboarding is often "figure it out" dressed up as "we believe in learning by doing."

At an MNC (Google, Microsoft, Amazon, etc.): The onboarding is structured. There are orientation sessions, buddy assignments, scheduled 1-on-1s with your manager, and detailed documentation. You will have a Confluence page to read, a Jira board to understand, and a "starter project" designed to ramp you up.

Regardless of company type, here is what you should do on Day 1:

1. Dress appropriately. When in doubt, slightly overdress. Observe what others wear and calibrate on Day 2. The days of formal shirts and ties in Indian IT are mostly over, but showing up in a hoodie and flip-flops on Day 1 is still a bad move at most places.

2. Introduce yourself to people near your desk. A simple "Hi, I am [Name], just started today on [Team]. Nice to meet you" goes a long way. You do not need to be the most social person in the room. Just be warm and approachable.

3. Write down everything. Names, team structures, acronyms, processes. You will not remember any of it otherwise. Use a notebook, a notes app on your phone, or a document on your laptop.

4. Ask HR/admin about the basics. Where is the cafeteria? How do I apply for leave? What are the working hours? Is there a dress code? Where do I park? These are not stupid questions. They are practical necessities.

5. Set up your email signature, Slack profile, and internal tools. Do this before you need them. Include your full name, role, team, and phone number in your email signature.

The First Week Emotional Rollercoaster

Almost every fresher we talked to described a similar emotional arc in the first week:

Monday: Excited, nervous, overwhelmed Tuesday: Confused about what you should be doing, too afraid to ask Wednesday: Starting to feel like everyone is smarter and more competent than you Thursday: Wondering if you made a mistake, missing college Friday: Exhausted from doing almost nothing productive all week

This is normal. It happens to everyone. The people who look like they have everything figured out on their first week are either hiding their confusion well or have been briefed by someone who works there.

The Unwritten Rules of Corporate India#

Email Etiquette (Seriously, Learn This)

You probably think email is simple. You have been emailing professors for years. Corporate email is a different game. The way you write emails in your first job will shape how people perceive your professionalism, attention to detail, and communication skills.

Rule 1: Subject lines matter. "Question" is a bad subject line. "Question regarding Q3 deployment timeline for Project Atlas" is a good one. Be specific. People receive 50 to 100 emails a day. Your subject line determines whether they open yours now, later, or never.

Rule 2: Keep it concise. Most corporate emails should be 3 to 5 sentences. If it is longer than that, it probably should be a meeting or a document with a summary email.

Rule 3: Structure your asks. If you need something, make it crystal clear. Bad: "I was wondering about the status of the design review, and also I had some questions about the API endpoints, and by the way I have not received access to the staging server yet." Good: "Three quick items: (1) What is the status of the design review? (2) Are the API endpoints documented somewhere? (3) Could you help me get staging server access?"

Rule 4: CC and BCC are political tools. Every CC is a deliberate choice. When you CC someone's manager, you are sending a signal. When you reply-all, everyone sees it. Be intentional. When in doubt, CC fewer people rather than more.

Rule 5: Do not email when you can walk over. If the person sits 10 meters away and the question takes 30 seconds to answer, walk over and ask. Not everything needs a paper trail. Some things are resolved faster with a quick face-to-face chat.

Rule 6: Never email while angry. Write the email, save it as a draft, go get a coffee, come back, read it again, then decide if you still want to send it. Angry emails in corporate settings can derail your reputation permanently.

Meetings: What Nobody Explains

In college, meetings are rare and informal. In corporate India, meetings are the atomic unit of work. You will spend 30% to 60% of your time in meetings, depending on your role and company.

Types of meetings you will encounter:

• Standup / Daily Sync: 15 minutes, each person shares what they did yesterday, what they are doing today, and any blockers. Keep your update to 60 seconds.
• Sprint Planning: For engineering teams using Agile. This is where work for the next 1-2 weeks is decided.
• 1-on-1 with your manager: Usually weekly or biweekly. This is YOUR meeting. Come with updates, questions, and topics to discuss. Do not waste it by saying "nothing much to share."
• Design/Code Review: You present your work to the team for feedback. This feels intimidating the first few times. Prepare, present clearly, and do not get defensive about feedback.
• All-Hands/Town Hall: Company-wide or team-wide meeting with leadership. Usually monthly or quarterly. Attendance is expected but participation is optional.

Meeting survival tips for freshers:

1. Show up on time. In corporate India, "on time" means 2 minutes early, not "I will join in 5 minutes."
2. Have your camera on (for virtual meetings). It shows engagement.
3. Take notes. When your manager says something important in a meeting, write it down. When action items are assigned, write them down.
4. Ask questions. Contrary to what you might think, asking good questions in meetings makes you look engaged and intelligent, not ignorant. The caveat: make sure the question has not already been answered.
5. Do not check your phone. People notice.

Office Politics: It Exists, and You Cannot Ignore It

Here is the uncomfortable truth that corporate motivational speakers will not tell you: every organization has politics. Every single one. From a 5-person startup to a 500,000-person conglomerate.

What "office politics" actually means:

• People have different agendas, priorities, and incentives
• Some people have more influence than their title suggests
• Alliances form and shift based on projects, promotions, and personal relationships
• What gets communicated formally is not always the full picture

How to navigate politics as a fresher:

1. Observe before you act. Spend your first 2 to 3 months watching the dynamics. Who defers to whom? Who has the real decision-making power? Which teams collaborate well and which have friction? Do not form strong opinions about people or teams in your first month.

2. Stay neutral. You will inevitably hear complaints and gossip. "This manager is terrible." "That team always delays things." "HR is useless." Listen politely but do not take sides publicly. You do not have enough context yet to know who is right.

3. Build relationships across teams. Do not limit your network to your immediate team. The person in the testing team, the designer on the other floor, the ops manager in a different building might all become valuable allies later. Have lunch with different people.

4. Avoid badmouthing anyone. In corporate India (and everywhere else), what you say about people will get back to them. Assume every conversation you have will be relayed to the person you are talking about. If that thought makes you uncomfortable, do not say it.

5. Understand your manager's priorities. Your manager has goals, pressures, and a boss of their own. Understanding what they care about and what they are measured on helps you do work that matters to them. This is not manipulation. It is alignment.

How to Ask Questions Without Annoying Your Manager#

This is the number one anxiety for Indian freshers. You need to ask questions to learn, but you are terrified of seeming incompetent. So you oscillate between two extremes: asking too many questions (annoying) or asking too few questions (making avoidable mistakes).

Here is the framework that works:

The 15-Minute Rule

When you are stuck on something, try to solve it yourself for 15 minutes. Google it. Check the documentation. Ask ChatGPT. Look at previous code/work for reference. Set a timer if you have to.

If after 15 minutes you are still stuck, ask for help. But when you ask, show your work:

Bad: "I do not know how to set up the database connection."

Good: "I have been trying to set up the database connection for the past 15 minutes. I followed the README, got it to connect locally, but I am getting a timeout error when connecting to the staging database. I checked the firewall rules and they seem fine. I think it might be a credentials issue but I am not sure where the staging credentials are stored. Could you point me in the right direction?"

The second version shows that you tried, you have context on what you have done, and you are asking a specific question. This makes it easy for the other person to help you quickly and makes them respect your effort.

Batch Your Questions

Instead of pinging your manager every 30 minutes with a new question, keep a running list of questions and ask 3 to 5 at once during your 1-on-1 or a dedicated slot. This is more respectful of their time and shows that you can work independently.

Exception: if the question is blocking your work and you cannot make progress without the answer, ask immediately. Do not sit idle for 4 hours because you wanted to be polite.

Choose the Right Channel

• Quick, low-stakes questions: Slack/Teams message
• More complex questions needing discussion: Schedule a 10-minute call or walk over to their desk
• Questions needing documentation: Email
• Feedback on your work: 1-on-1 meeting

The Difference Between College Deadlines and Work Deadlines#

In college, deadlines are suggestions. You submit an assignment 2 days late and get a minor penalty. You skip a lecture and nothing happens. You procrastinate until the night before the exam and somehow pass.

In corporate India, deadlines are commitments. When you tell your manager "I will have the feature ready by Thursday," they plan around that. They tell their manager. Their manager tells the client. A chain of expectations is set.

When you miss a deadline at work, it does not just affect you. It affects your team, your manager, and potentially the client. This is the single biggest mindset shift that freshers need to make.

How to Manage Deadlines

1. Estimate conservatively. If you think something will take 2 days, say 3. Things always take longer than you think, especially when you are new. Under-promise and over-deliver is not just a cliche. It is a survival strategy.

2. Communicate early if you will miss a deadline. If you realize on Wednesday that you will not make the Thursday deadline, tell your manager on Wednesday. Not on Thursday evening. Not on Friday morning. The earlier you flag a delay, the more options your manager has to adjust plans.

3. Break big tasks into smaller milestones. Instead of "I will build the entire feature by Friday," try "I will finish the database schema by Tuesday, the API endpoints by Wednesday, and the frontend integration by Friday." This makes your progress visible and catches delays early.

4. Track your commitments. Use a tool (Notion, Google Tasks, a physical notebook) to track what you have committed to and when. Do not rely on memory.

Your First Appraisal: Expectations vs. Reality#

Every Indian fresher imagines their first appraisal going something like: "You have been amazing. Here is a 30% raise and a promotion."

Here is what actually happens at most companies:

The Typical Fresher Appraisal Cycle

At service companies (TCS, Infosys, Wipro, etc.): Appraisals happen annually. Freshers in their first year typically get a 5 to 10% raise, sometimes less. Promotions happen after 2 to 3 years on a relatively fixed timeline. Your manager fills out a rating form, and the actual raise is decided by HR based on company performance and budget.

At startups: Appraisals are less structured. Some startups do formal reviews every 6 months. Others are ad hoc. Raises can be anywhere from 0% to 30% depending on company stage, your performance, and how much they want to retain you. The good thing about startups: if you perform well, raises and title bumps can come faster.

At MNCs: Structured annual or semi-annual reviews with clear rating systems (1-5, "Exceeds Expectations" / "Meets Expectations" / "Below Expectations"). Raises for freshers are typically 8 to 15%. FAANG companies have well-defined promotion timelines (typically 2 years for first promotion at Google).

How to Prepare for Your First Appraisal

1. Keep a "brag document." Starting from your first week, maintain a document where you list every accomplishment, project delivered, positive feedback received, and skill learned. When appraisal time comes 6 to 12 months later, you will not remember what you did in month 2. This document is your evidence file.

According to Julia Evans' popular blog post on brag documents, this is a practice that senior engineers at top companies swear by. Start it as a fresher and you will be ahead of most people.

2. Ask for feedback before the formal review. Do not wait 12 months to find out how you are doing. Ask your manager every month or two: "Is there anything I should be doing differently? Am I meeting your expectations for someone at my level?" This gives you time to course-correct.

3. Know what "good" looks like. Ask your manager at the beginning: "What would a successful first year look like for someone in my role? What are the key things you would want me to achieve?" This sets clear goalposts.

4. Do not compare yourself to others. Your colleague might get a higher rating. It might feel unfair. It might actually be unfair. But obsessing over it will not help. Focus on your own growth trajectory.

The Impostor Syndrome Phase (Everyone Goes Through It)#

Somewhere around week 3 to 6, most freshers hit a wall. You look at your colleagues and think: "Everyone here is so much better than me. They write cleaner code. They speak more confidently in meetings. They seem to understand everything instantly. I do not belong here."

This is impostor syndrome, and it is almost universal among freshers entering the workforce.

Why It Hits Indian Freshers Especially Hard

1. The gap between college and work is massive. Indian engineering colleges (with some exceptions) teach outdated syllabi with minimal practical application. When you show up at work and your colleagues are talking about Docker, Kubernetes, CI/CD pipelines, and microservices, and your college taught you Java servlets and C++, the gap feels insurmountable.

2. The comparison trap. In college, your competition was visible and bounded. You ranked against 60 classmates. At work, you are surrounded by people with 2, 5, 10 years of experience who obviously know more than you. Comparing yourself to them is like a first-year medical student comparing themselves to a practicing surgeon.

3. Cultural pressure to know everything. Indian education rewards knowing the answer. Admitting "I do not know" is seen as weakness. In a good workplace, admitting what you do not know is seen as maturity and self-awareness.

How to Deal With It

1. Remember that you were hired. The company interviewed you, evaluated you, and decided to pay you a salary. They know you are a fresher. They are not expecting you to be a senior engineer on Day 1.

2. Set a realistic ramp-up timeline. Most managers expect freshers to take 3 to 6 months to become fully productive. In the first month, your job is to learn, not to deliver at the level of experienced team members.

3. Talk to other freshers. If your company has a fresher cohort, connect with them. You will discover that everyone is going through the same confusion and self-doubt. Shared suffering is remarkably comforting.

4. Focus on learning rate, not current skill level. Your manager does not expect you to know everything. They expect you to learn quickly. Show that you learn from mistakes, incorporate feedback, and get better over time, and you will be fine.

Making Friends at Work#

This section might seem trivial, but our survey data says otherwise. When we asked "What was the hardest part of your first 90 days?", "social adjustment" was the second most common answer after "technical ramp-up."

The Lunch Table Problem

In college, your social group formed naturally over years. At work, you are suddenly surrounded by people you do not know, many of whom are older than you. The lunch table, the chai break, and the post-work hangout all require intentional effort.

Practical tips:

1. Say yes to social invitations for the first month. Team lunches, after-work outings, weekend plans. Even if you are tired. The first month is when social bonds form, and being absent signals that you are not interested.

2. Find your people. You do not need to be best friends with everyone. Find 2 to 3 people whose company you genuinely enjoy. These might be teammates, fellow freshers from other teams, or people you bonded with during onboarding.

3. Be helpful. Bring snacks to share. Help a colleague debug a problem. Offer to pick up coffee when you are going. Small gestures of generosity build goodwill faster than any social skill.

4. Do not eat lunch alone at your desk every day. Unless you genuinely need alone time (and some days you will), make the effort to eat with people. In Indian corporate culture, the lunch table is where a surprising amount of relationship-building and information-sharing happens.

When to Say Yes and When to Say No#

Freshers default to "yes." Someone asks you to help with their task? Yes. Manager asks if you can work on Saturday? Yes. Another team asks if you can build a quick report? Yes.

Six months in, you are doing three people's work, your actual project is behind schedule, and you are burning out.

The Framework

Say yes to:

• Opportunities to learn new skills relevant to your growth
• High-visibility projects, even if they require extra effort
• Requests from your direct manager (within reason)
• Helping colleagues when you genuinely have the bandwidth

Say no to (diplomatically):

• Work that is not your responsibility AND does not help you learn or grow
• Unreasonable timelines when you are already overloaded
• Tasks that other people should be doing but are delegating to the "new person"
• Weekend work that is not genuinely urgent

How to say no without burning bridges:

"I would love to help with that, but I am currently committed to [Project X] with a deadline on [date]. Could we discuss prioritization with [manager's name]? I want to make sure I deliver on my current commitments first."

This is professional, honest, and shows that your "no" is about prioritization, not unwillingness.

Practical Tips That Nobody Mentions#

Here is a rapid-fire list of practical tips from our survey respondents:

1. Learn keyboard shortcuts. Seriously. Alt+Tab, Ctrl+Shift+T, Ctrl+K (in Slack). These save hours per week and make you look proficient.

2. Read the company's wiki/Confluence. Most companies have internal documentation that nobody reads. The fresher who actually reads it starts with more context than half the team.

3. Set up your development environment properly in week 1. Get all the tools, access, and configurations sorted early. Do not be the person who cannot run the codebase in week 3 because they did not set up Docker.

4. Learn to write a good status update. Your manager should never have to ask "What are you working on?" Send a brief weekly update: what you did, what you are doing next, any blockers. This builds trust and visibility.

5. Understand your benefits. Health insurance, leave policy, learning budget, gym membership, whatever your company offers. Many freshers do not use benefits they are entitled to simply because they did not read the policy document.

6. Start a savings habit on your first salary. Put 20-30% aside before you spend anything. Open a mutual fund SIP. Future you will thank present you. Check Zerodha Varsity for free financial literacy content.

7. Keep your LinkedIn updated. Add your new role, skills, and projects as you go. Do not wait until you are looking for your next job.

8. Join the internal Slack/Teams channels for your team, adjacent teams, and the company-wide social channels. This is how information flows in modern companies. Being out of the loop because you did not join the right channel is entirely preventable.

The 90-Day Checklist#

Here is a concrete checklist for your first 90 days:

Month 1: Learn and Adapt

• Complete all onboarding tasks and paperwork
• Set up your development/work environment completely
• Meet everyone on your immediate team
• Understand your team's current projects and priorities
• Have your first 1-on-1 with your manager and ask about expectations
• Start your brag document
• Join relevant Slack channels and mailing lists
• Find 2-3 people you connect with socially

Month 2: Contribute

• Deliver your first meaningful piece of work
• Ask for feedback from your manager ("How am I doing?")
• Start building relationships with people outside your team
• Learn 1-2 tools or technologies the team uses that you did not know before
• Attend a company social event or team outing

Month 3: Establish Yourself

• Own a small project or feature end-to-end
• Give your first presentation to the team (even if it is a small knowledge-sharing session)
• Have a career development conversation with your manager
• Identify areas where you want to grow and start investing in them
• Feel less like a stranger and more like a team member

Before You Start: Get Your Resume Right#

If you are reading this guide before you have landed your first job, the most important thing you can do right now is get your resume in shape. A strong resume gets you through the door. Everything else in this guide is about what happens after you walk through it.

Your resume should be clean, ATS-optimized, and tailored for the roles you are applying to. Check out our guide on building a resume with no experience for specific advice on how freshers can create compelling resumes even without work history.

Also read our post on common resume mistakes Indian freshers make to avoid the pitfalls that get most applications rejected.

The Bottom Line#

Your first 90 days at work will be confusing, tiring, and occasionally demoralizing. That is not a sign that something is wrong. It is a sign that you are in a steep learning environment, which is exactly where you want to be.

The freshers who thrive are not the most technically brilliant. They are the ones who communicate well, ask smart questions, take feedback without being defensive, build relationships across teams, and show up consistently. Intelligence matters, but attitude and adaptability matter more in the first year.

College gave you technical foundations. Your first job teaches you everything else: how organizations work, how people collaborate, how decisions get made, and how to build a reputation as someone who is reliable, competent, and good to work with.

It gets easier. The confusion fades. The impostor syndrome quiets down. And somewhere around month 3 or 4, you will realize that you actually know what you are doing. Not everything, not even close. But enough to contribute, enough to be useful, and enough to start building a career.

Frequently Asked Questions#

How long does it take to feel comfortable at a new job? Based on our survey, most Indian freshers reported feeling "reasonably comfortable" by month 3 to 4. Fully confident and independent usually takes 6 to 12 months. The timeline varies by company, role, and individual, but if you still feel lost after 6 months, it might be worth talking to your manager about additional support.

What should I do if my manager does not give me enough work? This is more common than you think, especially at large service companies. Proactively ask for work: "I have completed [task]. What should I pick up next?" If work is genuinely scarce, use the time to upskill, take internal courses, or explore internal projects. Do not just sit idle.

Is it okay to job switch within the first year? It is not ideal, but it is not a career-ender. If you are genuinely miserable, being treated poorly, or the role is fundamentally different from what was promised, switching is valid. Just make sure you have a clear reason that you can articulate in future interviews, and try to stay at least 6 months if possible.

How do I handle a difficult manager? Document everything. Meet expectations. Communicate in writing. Seek mentorship from other seniors. If the situation is genuinely toxic, talk to HR (though be realistic about what HR can and cannot do). And start exploring internal transfers or external options if things do not improve.

Should I do an MBA or get work experience first? In general, 2 to 3 years of work experience before an MBA is the recommended path. MBA programs value work experience in admissions, and you will get more out of the MBA curriculum if you can relate it to real workplace scenarios. Unless you have a very specific reason to do an MBA immediately (like a guaranteed placement at a top B-school), work first.