when to change companies

Most PMs change companies for the wrong reasons. They leave because they are frustrated — with their manager, with the pace, with some political situation that feels intolerable. Three months into the new job, they discover they have carried every one of those frustrations with them, plus new ones they did not anticipate.

I have watched thousands of PMs navigate career transitions. The ones who made good moves had a clear answer to one question: what can I not learn here anymore? The ones who made bad moves had a clear answer to a different question: what am I running away from?

These are not the same question. The first one is strategic. The second is emotional. You need to know which one you are answering.

The five real signals

Not every frustration is a signal. Some frustrations are the job — product management is a discipline of operating under constraints, and discomfort is the default. But there are five signals that genuinely mean it is time to move.

Signal 1: You have stopped learning and it is not a phase. Every role has plateaus. You hit one after six months, another after eighteen months, a big one after three years. Plateaus are normal. What is not normal is when you have been on the same plateau for a year, you have asked for new scope, and the organisation cannot give it to you. If you are a PM3 doing PM3 work at a company that does not have PM4 problems, you have outgrown the company. This is not arrogance. It is a structural mismatch.

Signal 2: The product direction is something you fundamentally disagree with. Not tactically — every PM disagrees with individual decisions. Fundamentally. If the company is pivoting to a strategy you believe will fail, and you have raised your concerns, and leadership has decided to proceed anyway, you have two choices: commit fully to the new direction, or leave. Staying while silently disagreeing is the worst option. Your work will suffer, your team will sense it, and you will become the person who says “I told them so” at the post-mortem. That person has no future at any company.

Signal 3: Your manager is actively blocking your growth. Not every bad manager is a reason to leave — sometimes you can transfer teams, escalate, or wait them out. But if your manager is claiming credit for your work, giving you no visibility to leadership, and blocking your promotion conversations, and you have tried the internal channels, leaving is the rational move. In India’s tech ecosystem, where notice periods can be 60-90 days, waiting too long means you lose months of career momentum.

Signal 4: The company’s financial trajectory has changed. If you joined a Series B startup that was growing 3x annually and it is now flat, the nature of your PM role has changed even if your title has not. Growth-stage PM and survival-stage PM are different jobs. You might prefer survival-stage work — some PMs thrive in turnarounds. But if you joined for growth and the growth is gone, staying out of loyalty is not noble. It is a bad career decision.

Signal 5: You need a specific credential and this company cannot give it to you. If you want to move into AI product management and your company has no AI roadmap, no amount of internal manoeuvring will give you that experience. If you want to work at a global company and your current company only operates in India, you need to move. Credential gaps are the most legitimate reason to switch — they are strategic, not emotional.

The five false signals

These feel like reasons to leave. They are not.

False signal: “My compensation is below market.” Ask for a raise first. Seriously. I have seen PMs leave good roles — roles where they were learning, shipping, and growing — because they assumed the company would not match market rates. They never asked. Many Indian tech companies will adjust compensation if you have a credible case and a competing offer. Leaving over money without having the conversation is leaving over an assumption.

False signal: “The company is too slow.” Every company feels slow from the inside. The startup you are interviewing at also feels slow to the people who work there. Slowness is usually a symptom of something specific — approval layers, technical debt, understaffed teams, unclear ownership. If you can identify and fix the specific cause, that is a better career move than leaving. If you fix it and the slowness persists for structural reasons, that becomes signal 1 (stopped learning).

False signal: “I don’t get along with a cross-functional partner.” Conflict with sales, engineering leads, or designers is not a reason to leave. It is the job. If you cannot work with difficult stakeholders here, you will not be able to work with different difficult stakeholders there. The one exception is if the conflict is genuinely toxic — harassment, deliberate sabotage, retaliation. That is not a stakeholder problem. That is a safety problem, and leaving is appropriate.

False signal: “My friends at other companies have better titles.” Title inflation in Indian tech is extreme. A “Senior PM” at a 50-person startup and a “Senior PM” at Google are entirely different roles. Do not optimise for what your LinkedIn profile says. Optimise for what your next interviewer will ask you to demonstrate.

False signal: “I’m bored.” Boredom in PM is almost always a sign that you are not going deep enough, not that you need a new company. Are you running user research every month? Are you spending time in the data? Are you building relationships with customers? If you have done all of that and you are still bored, revisit signal 1. But most PMs who say “I’m bored” have not done the deep work. They have been doing the meeting-and-email version of PM and mistaken it for the whole job.

The scene you will recognise

This pattern plays out constantly. A PM is frustrated with something real — the VP of Sales overriding roadmap decisions is a genuine problem. But instead of treating it as a product problem (identify root cause, propose solutions, escalate if needed), they treat it as an emotional breaking point. The frustration is valid. The response is not strategic.

The timing question specific to India

India’s tech job market has structural features that affect when and how you move.

Notice periods are brutal. 60-90 day notice periods are standard. This means your decision-to-exit window is nearly three months. If you decide to leave in January, you are not starting the new job until March or April. Companies know this. Some will try to retain you during the notice period with counteroffers. Decide before you resign whether you will entertain a counteroffer, because deciding in the moment — with your manager in front of you, offering a 40% hike — is how people make bad decisions.

The hiring cycle is seasonal. Most Indian tech companies do heavy PM hiring in Q1 (January-March) and Q3 (July-September), aligned with budget cycles and the post-appraisal attrition wave. If you want maximum options, start your search 3-4 months before these windows.

The ecosystem is small. India’s PM community, especially at the senior level, is remarkably tight. Your former colleagues will be your future interviewers, stakeholders, or reports. Every exit is a reputation event. Burning bridges in Bangalore today means closed doors in Gurgaon tomorrow.

Counteroffers are a trap, usually. If your company did not value you enough to pay you fairly before you resigned, a counteroffer is a panic response, not a strategic investment in your career. Research across markets shows that 50-70% of people who accept counteroffers leave within 12 months anyway. The underlying issues — growth, direction, trust — do not change because your salary went up.

How to leave without burning bridges

The exit matters as much as the entry. Here is the protocol.

Give more notice than required. If your contract says 60 days, offer to stay 75 if it helps with the transition. This costs you two weeks. It buys you a permanent reputation as someone who leaves responsibly. In India’s tight ecosystem, this matters more than you think.

Write the handover document before you resign. Not after. Before. Walk into the resignation conversation with a transition plan ready. This signals professionalism and makes it nearly impossible for anyone to claim you left them stranded.

Have the conversation with your direct manager first. Always. Not with HR, not with a skip-level, not with a peer. Your manager should hear it from you, in person or on a video call, before anyone else. Even if your manager is the reason you are leaving. Especially if your manager is the reason you are leaving.

Do not badmouth the company during your notice period. You are still employed. Your team is watching how you handle the exit. If you spend your last 60 days telling everyone why the company is broken, you are not being honest — you are being unprofessional. Save your feedback for the exit interview, deliver it constructively, and move on.

Ship something before you go. Leave with a completed deliverable, not an abandoned one. If you are mid-project, either see it through or hand it off at a clean breakpoint. The last thing you ship is what people remember.

Test yourself

The two-year myth

There is a persistent belief in India’s tech ecosystem that you should stay at every company for at least two years. This is half-right.

Staying less than a year looks bad. It suggests you either made a poor decision joining, or you were unable to adapt. Unless the company did something genuinely wrong (layoffs, toxic environment, bait-and-switch on the role), a sub-year stint is a red flag that interviewers will probe.

But the two-year minimum is not a rule. It is a heuristic from a time when companies invested in structured onboarding and it took a year to become productive. In modern Indian tech, especially at startups, you are productive in 3-4 months and have a clear read on the company’s trajectory by month 8-10.

The real question is not “have I been here long enough?” It is “can I tell a compelling story about what I accomplished and what I learned?” If you shipped a major initiative, learned a new domain, and grew your scope in 15 months — that is a better narrative than “I stayed for three years because I thought I was supposed to.”

Product-manage your career

Greg Prickril said something in a Pragmatic Leaders session that has stuck with me: “Without a plan, you are just reactive. If it changes, it will be a matter of luck, even in a hot job market.”

He is right. Most PMs spend more time on their product roadmap than their career roadmap. They are deliberate about sequencing features and reactive about sequencing roles. Apply the same rigour you use at work:

• Have a 3-year direction. Not a plan — directions change. But know whether you are heading toward IC depth (principal PM, staff PM), people leadership (PM lead, Director, VP), or a domain bet (AI, fintech, healthtech). Each path requires different moves.
• Run experiments. Before committing to a domain switch, do side projects, take courses, talk to people who work in that domain. An experiment that costs you a weekend is cheaper than a move that costs you a year.
• Track your learning rate. If your learning curve has flattened and the company cannot steepen it, that is your leading indicator. Do not wait until you are miserable to start looking. Start when you notice the plateau.
• Build before you need it. Relationships, skills, reputation — all of these take time to compound. The PM who starts networking only when they need a job is already behind. The PM who has spent two years sharing work publicly, helping peers, and building cross-company relationships has options before they need them.

The best time to look for a job is when you do not need one. The second best time is when you have done the analysis and confirmed that staying is the wrong move. The worst time is when you are emotionally exhausted and will take the first offer that gets you out.

Do not be the PM who makes their most important product decision — their own career — with less rigour than they would bring to a sprint planning session.

Where to go next

• Understand the PM career ladder before you move: The PM Career Ladder
• If you are considering your first PM role: How to Break Into PM in India
• Nail the interview at your next company: PM Interview Types
• The behavioural interview will ask why you left: Behavioural and STAR Interviews
• Negotiate your offer with confidence: Tell Me About Yourself