Six months into your first job, the Sunday-evening dread starts. You tell yourself it is normal. Everyone hates Mondays. But by month eight, the dread has a schedule. You know exactly which Slack messages will ruin your Tuesday, which meeting will waste your Wednesday, and which "urgent" task on Friday will cancel your weekend plans. You are not burned out. You are bored, underpaid, and quietly furious. And you have no idea if leaving now will destroy your career.
This piece is for the First-Job Stayer: 0.5 to 2.5 years in, software engineer or analyst or associate consultant, unhappy or bored, unsure if leaving too early hurts you more than staying too long. There is no LinkedIn bro-speak here. Just a framework, India-specific traps, and a checklist.
The "minimum 1 year" rule — and when to break it
Six months into your first job, someone will tell you: "Stay at least one year. Otherwise it looks bad on your resume." This advice is not wrong. It is just incomplete.
The one-year rule exists because recruiters use tenure as a cheap filter. A 6-month stint raises questions. But the rule assumes you are learning, growing, and at least tolerating the job. It does not account for the job that is actively damaging you.
Here is the truth: one year is a heuristic, not a law. If you are in a role where you write zero code, learn nothing, and spend your days updating Excel sheets no one reads, staying 12 months does not make you more employable. It makes you a year older with nothing to show.
The question is not "Have I completed one year?" The question is "What will I say about this year in an interview?" If the answer is "I stayed because I was told to," that is not a credential. That is a confession.
There are two exceptions where the rule is real:
- You are in a prestigious company (Google, Microsoft, top-tier consulting) where the brand itself is a credential. Leaving at 8 months wastes the signal.
- You have no idea what you want next. If you cannot articulate why the next job is better, stay 3 more months and figure it out. "Anything but this" is not a strategy.
The 3-factor test: learning, pay, health
Every valid reason to leave your first job falls into one of three buckets. If two of the three are broken, and there is no credible plan to fix either within 3 months, it is time to go.
Learning
Are you learning something that makes you more valuable in your next job? Not "Are there training sessions?" Are you shipping code, owning features, talking to customers, debugging production, or mentoring someone?
If your day-to-day is 80% work that could be done by someone with 6 months less experience, your learning curve is flat. A flat learning curve in year one is a career emergency. You are not building equity. You are burning time.
Pay
Is your pay at market rate for your role, city, and YOE? Not "Is it enough to survive?" Is it competitive? In India, first-job salaries are often 20-40% below market because companies know you have no leverage. That is fine for 6 months. It is not fine for 18 months.
If you have asked for a raise and been told "next cycle," and the next cycle is 9 months away, your pay is broken. If you are in Bangalore earning ₹4.5 LPA as a software engineer, you are being exploited, not employed.
Health
Are you sleeping enough? Do you dread Sunday evening? Is your manager's feedback style leaving you anxious? Is the commute 3 hours a day? Health is not just burnout. It is the slow erosion of confidence, curiosity, and energy. If you are becoming someone you do not like, that is a health problem.
The test in practice: Priya, 11 months at a mid-tier IT services firm in Hyderabad. She writes test cases, not code. Her salary is ₹4.2 LPA in a city where juniors at product companies start at ₹8 LPA. She wakes up at 5 AM for a 7 AM cab, gets home at 8 PM, and has not had a weekend without work messages in 4 months.
Learning: broken. Pay: broken. Health: broken. Three for three. The one-year rule would tell her to stay. The 3-factor test tells her to leave — and to never take a job like this again.
India-specific timing traps
Leaving a job in India is not the same as leaving a job in the US. There are four traps that can cost you money, time, or peace of mind.
Appraisal season (March-April)
Most Indian companies run annual appraisals in March-April, with payouts in April-May. If you leave in January or February, you forfeit the raise and the bonus you spent a year earning. If you are planning to leave, time your exit for after the appraisal payout. The exception: if the job is destroying your health, no raise is worth 3 more months.
Notice period (30-90 days)
Indian notice periods are longer than most countries. 30 days is standard for junior roles. 60-90 days is common in IT services and consulting. A 90-day notice period can kill an offer from a startup that needs someone in 30 days.
Negotiate. Some companies accept a buyout (you pay for the remaining days). Some will let you go early if your manager likes you. Start the conversation before you have an offer, not after.
PF and relieving letter
Your Provident Fund (PF) account stays with you across jobs, but transfers can take months if your previous employer delays the paperwork. More importantly: the relieving letter. In India, many companies require a relieving letter from your previous employer as proof that you did not abscond. If you leave without serving notice, or on bad terms, you may not get one. That can block your next job.
Do not burn bridges. Even if your manager is incompetent, serve your notice, document everything, and leave professionally. The world is smaller than you think.
The "bench" trap in IT services
If you work at an Indian IT services company, you may spend months on the "bench" — paid, but with no project. The bench is not rest. It is a slow career death. If you have been on the bench for 3+ months with no project in sight, your learning is zero and your resume is stagnating. That is a valid reason to leave, even at 6 months.
Signs you're leaving too early
Not every bad day is a reason to quit. Here are the signs that you are leaving too early, not too late.
- You have not had a real conversation with your manager about what is wrong. You have not asked for different work, a different team, or a clear growth plan.
- You are leaving because of one bad week, not a sustained pattern.
- You do not know what you want next. "Anything but this" is not a career strategy.
- You have not been there long enough to have a single achievement to talk about in interviews.
If two or more of these are true, stay 3 more months. Use that time to fix what you can and build an exit plan. Read our career decision framework for a structured way to think through your next move.
Signs you're staying too long
The opposite problem is harder to spot because it looks like responsibility.
- You have stopped learning 6+ months ago and you are just "waiting for the right time."
- You have been promised a raise or promotion "next cycle" twice.
- You are making excuses for your manager's behaviour to your friends.
- Your health metrics are declining: sleep, mood, energy, relationships.
- You are afraid to interview because you think no one will hire you.
That last one is the real trap. The longer you stay in a role that erodes your confidence, the more you believe the erosion is your fault. It is not.
The smart exit strategy
Leaving is not about rage-quitting. It is about engineering a better next step.
Step 1: Fix what you can. Ask for a different project. Ask for a skip-level meeting. Document your asks in email. If nothing changes in 6 weeks, you have your answer.
Step 2: Build the next thing while you are still employed. Start interviewing before you resign. The "I need to focus on my job search" resignation is a luxury most people cannot afford. If you are weighing multiple offers, our guide on how to choose between two job offers in India has a framework that works.
Step 3: Time your exit around appraisals and notice periods. If you are in IT services, avoid the bench by leaving before you land on it.
Step 4: Leave on good terms. Serve your notice. Train your replacement. Write a handover doc. The world is smaller than you think.
Step 5: Do not accept the first offer out of desperation. If you hated your first job because it was boring, do not take a second job because it pays 20% more. Use the same 3-factor test before you say yes. If you are considering a bigger shift, read our piece on career change at 30 in India for the longer-term view.
Stuck in your first job and need clarity?
Talk to a working pro who has been exactly where you are. On Amigzo, book 20 minutes with a Guide in your domain and get honest, specific advice.
The decision checklist
Use this checklist before you hand in your resignation. If you check 6 or more, you are ready to leave. If you check fewer than 4, stay and fix what you can first.
| Check | Statement |
|---|---|
| ☐ | I have not learned anything new in 6+ months. |
| ☐ | My pay is 20%+ below market for my role, city, and YOE. |
| ☐ | My health (sleep, mood, energy) has declined since I joined. |
| ☐ | I have asked for a change and been told "next cycle" with no action. |
| ☐ | I know what I want in my next role and can articulate it in one sentence. |
| ☐ | I have at least one interview lined up or a strong referral. |
| ☐ | I have 3+ months of expenses saved (or family support). |
| ☐ | I can serve my notice period without damaging my health further. |
| ☐ | I have at least one achievement from this job I can talk about in interviews. |
| ☐ | I am not leaving because of one bad week or one bad manager. |
Key takeaways
- The one-year rule is a heuristic, not a law. If two of three factors are broken, you have a valid reason to leave.
- In India, timing matters. Appraisals, notice periods, PF, and relieving letters can all cost you if you ignore them.
- Do not rage-quit. Engineer your exit: fix what you can, interview while employed, and leave on good terms.
- Use the decision checklist. Six or more checks means you are ready. Fewer than four means stay and build a plan first.
Frequently asked questions
Quick answers about leaving your first job in India.
Should I leave my first job if I have only been there 6 months?
If two of the three factors — learning, pay, health — are broken with no fix in sight, yes. Frame the 6 months as "I realised the role was not aligned with my growth and made a deliberate decision to find a better fit." Do not apologise. Do not overshare.
How do I explain a short first job on my resume?
Be honest and brief. "Joined as a graduate trainee. Realised the role was primarily manual testing, not development. Left to find a role where I could ship code." The key is showing the decision was deliberate, not impulsive.
Will leaving my first job early hurt my future salary?
Sometimes. Recruiters may anchor on your current CTC. The fix: negotiate based on market data, not your current pay. If you are underpaid, say so. "My current salary is below market for this role and city. I am looking for ₹X, which is the median for someone with my skills."
What if my company has a 90-day notice period and my new offer needs me in 30 days?
Negotiate. Ask your current employer for an early release. Offer to work weekends, finish a specific deliverable, or pay a buyout. If they refuse, ask your new employer for a delayed start. Most companies will wait 30-60 days for the right candidate.
Is it okay to leave without a job offer?
Only if you have 6+ months of expenses saved and a clear plan. In India, the job market is competitive. Going unemployed for 3 months is stressful. Going unemployed for 6 months is dangerous. The parallel path rule applies: do not quit until you have an offer signed.