How do you explain leaving for a competitor in interviews?

Why does leaving for a competitor make hiring managers nervous?

Hiring managers worry about two things when you move to a direct rival: whether you'll carry information you shouldn't, and whether you'll leave them the same way you left the last place. On 30 September 2026, that anxiety got a very public demonstration. Matan Grinberg, co-founder and CEO of the AI coding startup Factory, posted on X that he had removed board advisor Chris Degnan over allegedly undisclosed, recurring conversations with Factory's rival Cognition. Within about an hour, Degnan announced he had joined Cognition as chief revenue officer. Degnan disputed the account — he said he resigned rather than being fired, hadn't spoken to Cognition while attending board meetings, and shared nothing proprietary. Prominent investors took opposing sides in public before the day was out.

Nothing about that story is unusual except the volume. People move between rivals constantly, and in most industries the pool of employers who need your exact skills is small. The reason a fight like this matters to you is that it sets the frame your interviewer is carrying into the room. They've watched a competitor move turn into a confidentiality argument on a public timeline, and some fraction of that suspicion lands on the next candidate who says, in effect, I currently work for the company you're trying to beat. You don't get to argue the frame away. You get to answer inside it, calmly, and remove the doubt early.

Here's the part most candidates get wrong: the interviewer is not testing your loyalty. They know you're leaving someone to come to them — that's the whole transaction. What they're assessing is your judgement about information and relationships. Do you speak carelessly about your current employer's roadmap? Do you hint that you'd bring a client list? Do you understand what you signed? A candidate who answers with discretion reads as someone who'll show the same discretion about them later. A candidate who dishes on internal politics to impress the room has just shown exactly how they'll behave after the next offer.

How do you script the answer without badmouthing anyone?

Build the answer in three parts: the problem you want to work on next, why this company is the place to work on it, and a clean, unemotional line about why your current role can't get you there. Never make a person the reason. Scope, problem and product are safe ground; managers, politics and pay grievances are not. A workable shape sounds like this: "I've spent three years on billing infrastructure at a firm where that system is basically finished. You're rebuilding yours from scratch, and I want to be in the room for the design decisions rather than maintaining someone else's." That's honest, specific and impossible to hold against you.

Make the answer concrete enough to be checkable. Vague ambition — growth, new challenges, a better culture — reads as either a cover story or a lack of thought. Name the thing. A sales candidate might say they've been selling a mature product into a saturated mid-market segment and want to build enterprise motion from an earlier stage. An engineer might point to a stack decision, a scale problem, or a shift from maintenance to greenfield. When you attach the move to a technical or commercial problem, the interviewer stops hearing "escape" and starts hearing "appetite." Two sentences is usually the right length. Longer answers start to sound defensive, and defensiveness invites follow-ups you don't want.

Rehearse the negative half too, because you will be probed. Expect "what would have kept you?" and "how did your manager take it?" Prepare a line that's true but closed: "A greenfield project would have kept me, and there wasn't one on the roadmap. My manager and I talked it through; there's no drama there." Say it once, don't elaborate, and return to the work. If your exit genuinely was ugly — a reorg, a bad boss, a layoff — you still don't relitigate it in the interview. Neutral facts, no adjectives. Nobody has ever been hired for winning an argument about a former employer in a room where that employer wasn't present.

What should you never imply about clients, code or inside knowledge?

Never imply that part of your value is the confidential material you can carry over. No roadmap details, no pricing tables, no client lists, no code, no internal metrics that aren't public. Candidates offer these up thinking they're proving relevance, and they're actually handing the employer a legal problem and a character read at the same time. The strongest interviewers will shut it down on the spot. The weaker ones will let you talk, note it, and quietly decline. Either way, the moment you say "I could probably get you their churn numbers," you've stopped being a candidate and become a liability with a CV attached.

Sales candidates face the sharpest version of this, because the temptation is enormous. A book of business feels like leverage. But a non-solicitation covenant is far more commonly enforced than a full non-compete, and hiring managers know it. Promising to bring accounts is the fastest way to turn an offer into a conversation with the legal team. Talk about buyer knowledge instead: how that market evaluates, what objections come up in month two, where deals stall. Market fluency is yours. Named relationships and contact data belong to your employer's systems. The distinction sounds fine-grained in the abstract and is completely obvious in a courtroom.

You can still prove impact without disclosing anything. Raise the level of abstraction: describe the method, the scale and the outcome in ranges or percentages rather than absolute internal figures. "Cut onboarding time for enterprise accounts by roughly 40%" is a defensible, useful claim. "We went from 312 to 189 support tickets a week after the March release" is an internal number, and stating it tells the interviewer you don't have a filter. If a figure appeared in a public filing, press release or conference talk, it's fair game. If you only know it because you have a login, round it, generalise it, or leave it out.

How do you answer non-compete and confidentiality questions honestly?

Say plainly whether you've signed anything, describe its scope as you understand it, and offer to share the document with the employer's counsel. Do not claim it's unenforceable, and do not pretend it doesn't exist. Employers ask because they want to price the risk, not because a covenant automatically disqualifies you — plenty of hires happen with a restriction in place, adjusted start dates, or a carved-out remit for the first few months. What sinks candidates is discovering the agreement after the offer. A sentence like "I have a twelve-month non-solicit and a standard confidentiality clause; happy to send both over" costs you nothing and buys real credibility.

Know the legal landscape before you speak, because it shifted. There is no federal ban on non-competes in effect in the United States: the Federal Trade Commission's rule was vacated by a federal court in August 2024, the agency dropped its appeals in September 2025, and the rule was formally removed from the Code of Federal Regulations in February 2026. Enforceability is now purely a matter of state law, and the states diverge sharply. California, Oklahoma, North Dakota and Minnesota ban them outright. Florida's CHOICE Act, by contrast, allows enforceable covenants and garden leave of up to four years for high earners.

Then get advice that's actually yours. An interviewer's reassurance that "we've never enforced one of those" is not legal protection, and neither is a recruiter's opinion. Pull your signed agreement out of your email archive — most people have never reread it — and check three things: the definition of a competitor, the duration, and whether it covers customers and colleagues as well as employment. If the restriction is meaningful and your state enforces it, an hour with an employment lawyer is the cheapest insurance in your whole job search. Bring the summary into the interview. Candidates who can describe their own obligations accurately sound like adults, and that impression carries well beyond this one question.

How should your CV read when you're joining a direct rival?

Write the CV so the jump reads as an escalation in scope, not a sideways hop for money. That means the numbers have to climb across roles: bigger territory, larger systems, more people, higher-value decisions. A recruiter scanning a same-industry move is subconsciously checking for a pattern — are you compounding, or circling? Put the trajectory in the bullets themselves. If you went from owning one module to owning a platform, from SMB accounts to enterprise, from running a team of three to a function of twelve, the progression does the persuading before anyone reads your summary line. Titles alone rarely carry it, because titles inflate differently at every company in your sector.

Your summary should name the domain, not the employer you're leaving. "Payments engineer, eight years across acquiring and fraud, currently scaling card-present volume in EMEA" travels cleanly to any rival. "Senior engineer at [your rival's name]" makes the reader think about the relationship rather than the work. Mirror the language of the specific job ad — same-industry moves are keyword-rich by nature, and the vocabulary gap between two competing employers is usually small but real, since each has its own internal names for shared concepts. Use theirs. If you're rebuilding the document rather than appending to it, the AI CV builder will hold that structure while you refine the wording by chat.

Then check that a parser actually reads it that way. Competitor moves generate close scrutiny at the screening stage, and none of your careful framing survives if the file itself breaks in extraction — dates in a text box, a two-column layout, a title buried in a header. Run the document through a free CV analysis to see your score out of 100, the ATS compatibility rating and a visual layout read before you send it anywhere. Paste in the job description too, and you'll get the missing skills for that specific ad plus ATS-friendly rewrites that echo its keywords. Fix the file first; the interview script only gets used if the CV clears the filter.

Frequently asked questions