Should You Quit Your First Job? A Framework for the First Two Years

A young engineer wrote to me in March, eight months into her first job at a large services company. She was on a support project, her work consisted mostly of running the same checks each morning, and she had learned, by her own estimate, very little since January. A friend had joined a startup at a higher salary and she was, in her words, "watching my career not start".

Two months later I heard from someone else with an almost identical description of the symptoms — bored, underused, convinced they were falling behind. The difference was that in his case there was an internal transfer open on a team that did the work he wanted, and his manager had already told him he would support it.

Both of them wanted to quit. One of them was right to. The distinguishing question was not how bad it felt; it was whether the situation had a route out that did not require leaving.

The seven-month feeling is normal, and it is not always information

Something predictable happens between month six and month ten of a first job. The novelty has gone, the training period has ended, the initial goodwill of being new has worn off, and the actual shape of the work has become visible. Simultaneously, your batchmates have started posting about their own jobs, and social media presents you with their best days against your ordinary ones.

That combination produces a strong urge to leave that has very little to do with whether the job is good. It is worth knowing this because acting on it in month seven, when it peaks, produces some of the worst career decisions I see — a lateral move to an equivalent job at a different company, taken for a small raise, that resets the clock on learning without changing anything structural.

The test I would apply is whether the problem is with the phase or the position. Phases end. Positions do not, unless something changes.

The four questions that actually settle it

Rather than asking whether you are happy, ask four narrower questions. They are more answerable, and together they tell you what to do.

Are you learning things that will still be worth something in two years? Not whether the work is enjoyable — whether the skills compound. Learning a company's internal ticketing process is not compounding. Learning to design a schema, debug a production incident, or ship something users touch is. If you have learned nothing that transfers in six months, that is the strongest single argument for moving.

Is there a path visible from where you are? Another team, another project, a manager who has told you what would need to be true for you to move. A visible path changes the calculation entirely, because internal moves are dramatically cheaper than external ones — no notice period, no interview loop, no reset on trust.

Have you actually asked? The number of people who want to leave a job without ever having told their manager what they want is remarkable. Managers are not clairvoyant, and a fresher who says "I would like to work on something closer to the product side, what would make that possible" is often surprised at how quickly the answer arrives.

Is the problem the job, or something the job is doing to you? A role that is dull is a career problem. A role that involves consistent abuse, unpaid overtime as a norm, or a pattern of delayed salaries is a different category. The first deserves a plan. The second deserves an exit as soon as you have somewhere to go.

When is it actually right to leave a first job?

There are a handful of situations where I would tell someone to go without much hesitation.

Your salary is delayed or unpaid, repeatedly. This is not a growth question, it is a solvency question, and the company's problems are not yours to absorb.

The work is genuinely non-technical and you were hired for a technical role, with no route back. Two years on a pure support rotation you cannot leave does real damage to a technical career, and it gets harder to explain the longer it runs.

The environment is abusive or unsafe — sustained hostility, harassment, or a manager who operates by humiliation. No compensation for that is adequate at any stage of a career.

The company is visibly failing, with layoffs already run and hiring frozen. Loyalty to an employer that will not exist in a year is not repaid.

Or you have a concrete, better offer in hand that changes the trajectory rather than just the salary. Note the word concrete. A hoped-for offer is not a reason to resign.

Everything else — boring project, indifferent manager, a friend earning more, a long commute, a stack you did not choose — belongs in the "fix it first, then decide" bucket.

The case for staying a little longer

Two things argue for a minimum tenure, and they are worth stating plainly because "never stay somewhere that does not serve you" makes for better social media than career advice.

The first is that short stints compound badly on a resume. One eight-month stint is easily explained. Two in a row invites the question of whether the pattern is the employers or the candidate, and recruiters do ask it. Roughly eighteen months to two years in a first role is the point at which the tenure stops being a question at all.

The second is that a great deal of the value of a first job arrives late. The first six months are onboarding, the next six are supervised work, and the period after that is where you finally do something end to end and own the outcome. Leaving at month eight means paying the full cost of ramping up and collecting almost none of the return. The arc of that is what we set out in your first ninety days in a tech job, and the part that matters is that it does not end at ninety days.

There is also the question of what you are optimising for. A modest raise for an equivalent role is not usually worth a reset, and the longer-term trade-off between compensation and momentum is exactly the one we take apart in a high starting package versus career momentum.

The six-month fix-it-first plan

If the honest answer to the four questions is "the job is dull but not damaging, and I have not really tried", give it two quarters of deliberate effort before you start applying. Most of the people who do this either find the job improves or leave later with a much stronger position.

Tell your manager, specifically, what work you want more of. Not a complaint — a request, with an example of the kind of task you mean.

Take the unglamorous thing nobody has volunteered for. In almost every team there is a piece of work that is important, slightly tedious, and unowned. Picking it up is the fastest route from "the new person" to "the person we give real things to", regardless of company size.

Build outside the job, deliberately, for five hours a week. If the role is not teaching you what you need, teach yourself in public — a project, an open-source contribution, something that exists at a URL. This does double duty: it keeps you employable and it often changes what you get given at work.

Find out what the good teams inside your company are and what it takes to move to one. Internal transfers usually require a minimum tenure and a manager's sign-off, both of which take planning.

And set a review date. Put a specific date six months out in your calendar, with the four questions written next to it. If the answers have not changed by then, you have a decision made with evidence rather than mood.

How do I explain leaving my first job so early?

This worry keeps people in bad roles longer than it should, and it is more manageable than it feels — provided the reason you give is forward-looking and consistent.

The version that works is short, factual, and about the work. "I joined a support project and after a year it was clear I would not get to build anything there. I have been learning backend development on my own and I am looking for a role where that is the job." That is one sentence of context, no blame, and a clear statement of what you are moving towards. Interviewers hear it constantly and it does not raise an eyebrow.

The version that does not work is a description of your manager. Even when it is entirely true, criticising a previous employer in an interview transfers the risk onto you, because the interviewer cannot verify the story and can easily imagine you telling a similar one about them. Say less than you want to.

Two practical notes. Keep the reason identical across your resume, the recruiter screen, and the final round, because inconsistency is noticed. And if the tenure is genuinely short — under a year — expect the question in every process and rehearse the answer in the same way you would rehearse any other, which is out loud, until it is forty seconds long instead of four minutes.

If you can point to something you built outside work in that period, the question mostly answers itself: the tenure was short because the role was wrong, and here is the evidence that you were not idle.

Leaving properly, if you are going

If the decision is to go, the manner of leaving matters more in Indian tech than students expect, because the industry is small and reference checks are routine.

Have the offer in writing before you resign, and read it against the same checklist you should have used the first time — notice period, bond or training clause, joining date, and what happens if the start date slips. Our guide to reading a fresher offer letter applies equally to a second offer.

Check your existing bond or service agreement, if you signed one, and know the actual exit cost rather than the rumoured one.

Serve the notice period properly and hand over your work in writing. The engineer who leaves a clean handover is remembered as someone worth rehiring; the one who disappears for the last month is remembered too, differently.

Resign to your manager first, verbally, before the formal email reaches anyone else. And do not use the resignation as an opportunity to deliver accumulated feedback. Say that you have accepted another role, thank them, and leave the relationship intact.

The thing to hold on to

The first job is not the career. It is the first two years of a very long sequence, and its main function is to convert you from a student into someone who can be trusted with real work. A dull first job that teaches you that is not a wasted one. A first job that teaches you nothing for two years is, and the distinction is worth the hour it takes to work out which one you are in.

Ask the four questions honestly, try the fix for six months if it is fixable, and if it is not, leave carefully rather than dramatically. Whether the underlying mismatch is the type of company rather than the specific job is worth a separate look — service company versus product roles covers what actually differs between them.

Wondering whether to stay or start applying? Talk to a Career Call counsellor. We will work through what you are actually learning, what your options inside the company are, and whether a move now helps or costs you.