Going back to employment after running your own business is one of the most common moves in a working life and one of the least discussed. People sell, wind down, get acquired, or decide they no longer want to be the person signing off payroll at 11pm on a Friday. None of that is failure; it is a change of structure. The job market has no vocabulary for it, so founders narrate the move badly, half apologising and half over-selling, and hiring managers pick up the wobble.
This article is about the search itself. For the document, see our guides on the CV after running your own business and the CV after self-employment. Get that done in a day; everything below is where the outcome is decided.
Decide what you are buying back
Founders who skip this drift, take the first offer, and are unhappy eight months later. Most people leaving their own business are buying back one of four things:
- Stability. A salary that arrives whether or not a client pays. If this is the driver, company stage and funding matter more than title.
- Scale. Something bigger than you could fund yourself: a real user base, a real budget, a distribution channel. That points to later-stage firms, and you accept process in exchange.
- Colleagues. Being the smartest person in a room of one gets old. Then team quality and the calibre of your manager outrank title and even money.
- Ending sole responsibility. Name this one honestly, because it argues against joining a five-person startup as employee number three, where you will be the last line of defence with less equity.
Timing and runway
While the business still runs. Your leverage is highest. You have income, you can decline a bad offer, and you speak in the present tense, which reads as confident rather than post-mortem. The cost is a part-time search plus the question of what happens to the business if you take the role. Have a clean answer ready: sold, wound down on a defined date, handed to a co-founder, or kept dormant. Vagueness here is what triggers the doubt about whether you will really let it go.
After it closes. Faster and more focused, but the clock runs on your savings and every week without income shaves off your ability to say no. Fix the date at which you would accept a role 20 percent below target well before you reach it, so the concession is a decision rather than a panic.
If you can choose, start three to four months before you are fully out.
The four worries in the hiring manager's head
They rarely say these out loud. Answer them anyway, early.
"You will leave in six months to start something else"
This kills more founder applications than any skills gap, and vague reassurance makes it worse. Give a concrete reason the change is durable: a co-founder split that clarified what you want, a family situation that reset your priorities, or finding you preferred building to selling. Then show horizon: say what you want shipped in two years here.
"You cannot take direction"
Especially from a manager younger or less experienced than you. Do not claim humility; show the mechanism. Describe a time you deferred to an investor or a client on something you disagreed with, and what came of it. Ask how decisions get made and how disagreement is handled, then stay calm about answers you would have played differently.
"You cannot work inside someone else's process"
Founders build the process, so they bend it. Interviewers probe with questions about documentation, ticketing and sign-off chains. The posture that works: constraints are a trade for scale, and you already lived with imposed process through client work, audits or regulation. Name a process you inherited and improved from inside rather than replaced.
"Your skills are solo skills"
Two people building quickly is a different discipline from thirty people building safely. If you are technical, this is the worry that costs offers. Say what tooling you used, what your review and release practice was, and where the gaps are. "I have not worked in a large codebase with formal review, but here is how I kept quality high alone" beats pretending the gap is not there. Before you search, get something visible done inside a team: an open-source contribution, a short contract.
Positioning: pick one thing
The most common founder mistake is presenting as a generalist. You ran everything, so you list everything, and the reader has no idea what you are for. Vaguely good at everything reads as unfocused at the moment someone has to slot you into a role and a budget line.
Pick the one capability your business made you unusually good at: not what you enjoyed most, but what you would objectively out-perform a normal candidate on. Common answers are selling to a specific buyer type, pricing, building product with no research budget, hiring under pressure, or retention in a churn-heavy category. Lead with it everywhere: your headline, your first CV line, your opening sentence in an interview, your LinkedIn About. Everything else is supporting evidence mentioned in passing.
Where founder experience helps and where it hurts
It helps at early-stage companies, in operations, in go-to-market and revenue functions, in customer-facing roles where judgement beats a script, in consulting, and in any job description containing "own" or "end to end". It helps most where the hiring manager has run something too.
It hurts on large-organisation specialist ladders with strict levelling. Where every band has defined behaviours and required tenure, independent experience does not map and recruiters genuinely cannot place you. There, target functions that hire for scarce skill rather than tenure, or accept an entry point one level down. Do not split your applications evenly between the two worlds.
Use the network you already built
You spent years talking to people who already know how you work, and most founders under-use them out of embarrassment. Approach in order: former customers, then suppliers and partners, then investors, then founder peers. Keep it short and specific:
"I am winding down the business at the end of the quarter and moving back into a role. I am focused on operations leadership in B2B software, ideally 50 to 200 people. You know how I work better than a CV does. If anyone comes to mind I would appreciate the introduction, and if not, no problem at all."
That works because it is a decision rather than a crisis, it says exactly what you want, and it is easy to decline. Never mass-send an "I am available" note. Former customers matter most: someone happy to pay you is a stronger reference than any manager, because they spent their own money on your judgement.
Revenue and outcomes, honestly
Use real numbers where you have them. If the business grew, say what it went from and to, over what period, and what you did to cause it. If it plateaued, say what you learned about why: usually a market or pricing lesson worth more than a curve.
If it closed, close the story properly, because closing well is evidence of judgement. Paying suppliers, migrating customers to alternatives, giving staff enough notice to land somewhere, and stopping before you burn other people's money are things competent operators do and weak ones avoid. Say it plainly: "the unit economics were never going to work at our cost of acquisition, so I closed while we could still pay everyone." That earns more respect than a rescued narrative. Do not inflate: a small consultancy described in scale-up language gets caught in the second interview.
Money and levelling
Two traps. The first is anchoring on what the business turned over: revenue is not salary, and a good year of profit distribution is not a market rate. Check what people doing the target role are paid in your market.
The second is expecting a title matching your independence. You ran the whole thing, so head-of feels right, but in a structured organisation that word comes with headcount and budget you have not managed inside a company. If you care about the work, take the level with the shorter path upwards and negotiate an explicit review at six months. If you care about the money, negotiate the money and let the title lag. A first salaried role often pays less in year one than a good year alone; what you get back is predictability.
The interview answer, and what to call yourself
For "why go back", give a short adult answer with a real reason and no bitterness. "I ran it for six years, took it to the point where growing further meant raising money I did not want to raise, and found the part I liked most was building the product, not running the entity. I want to do that with more resources than I could give myself." Stop there. Do not add a paragraph promising you will not leave.
On titles: if you were CEO of a two-person business, the word does more harm than good. It signals a level you were not operating at and invites the direction-taking doubt for free. Describe the work instead. "Founder and product lead", or "ran a two-person consultancy in industrial maintenance", tells a reader what you did. Keep the formal title for cases where there were genuinely layers under you.
Treat the move as a deliberate decision and spend the rest of the conversation on the job. People take you at the valuation you put on yourself, and the apologetic version of this story is the only one that reads as a failure.