Your CEO's Old Job Is Your New Problem

Find out what your CEO used to be

Two founders raise the same Series A. Same headcount, same burn, same mission slide on the wall. You get an offer from each. The only real difference is what they did before this: one used to write code, the other used to run campaigns.

That one fact will shape your next two years more than the salary, the title, or the OKRs. And almost nobody screens for it.

People get the question wrong from the start. They ask which kind of CEO is better. Wrong question. The question is which kind of CEO is better for you, for the specific work you actually do all day.

TL;DR

The claim: A CEO leads hardest through the lens of the job they used to have. Match that lens to your function and you get trust and autonomy. Mismatch it and you spend the year explaining why the obvious thing is not actually obvious.

What you'll walk away with:

• Why an engineer-CEO and a marketing-CEO break their teams in opposite, predictable ways
• The one signal that matters more than their background: whether they respect the function they didn't come from
• A short list of questions to read any CEO before you sign

Everyone Asks the Wrong Question

Search "technical vs non-technical founder" and you'll drown in takes. Jason Lemkin of SaaStr has written that he now invests almost only in engineer-CEOs, or business CEOs with a real technical co-founder, and that the non-technical ones need three to five times more money to get off the ground. Maybe he's right. For an investor.

But you're not writing the check. You're taking the job. And whether that job is good has nothing to do with whether your CEO can pass a system design interview. It comes down to whether your CEO understands the work you were hired to do.

That flips the whole thing. Stop asking "is this a good CEO." Ask "is this a good CEO for what I do."

What an Engineer-Turned-CEO Does to a Marketing Team

I've worked for one, so this is from the inside.

An engineer-turned-CEO treats growth like a feature. There's an input, there's an output, and if the output is wrong there must be a bug in the function. Clean. Logical. Completely wrong about how distribution works.

Here's the loop. They read a viral thread on Saturday, some founder posting "we 10x'd signups with this one channel." Monday morning, in your 1:1: "Why aren't we doing that?"

You explain that the channel doesn't map to our audience. That the case study is survivorship bias with a dashboard attached. That the tactic which worked for them in January is saturated by June. None of it lands, because in their model GTM is deterministic. You wrote the code, you should get the output. They don't feel the thing you feel: that channels decay, that brand is a lag indicator, that the same campaign run twice gives you different numbers for reasons nobody fully controls.

So you spend the week not running experiments. You spend it defending why the article on their screen is not a roadmap.

This isn't stupidity, and it's worth being fair about that. It's a different sense of what's hard. To them, building the product was the brutal part, and distribution is "just" telling people it exists. A marketer makes the identical mistake going the other direction.

What a Marketing-Turned-CEO Does to an Engineering Team

Now run it backwards. I've worked for one of these too.

A marketing-turned-CEO sells the demo before it exists. They saw a competitor's feature, promised it to a customer on a call, and now there's a date on it. "How hard can it be? It's just a toggle."

It is never just a toggle.

The marketer-CEO feels distribution in their bones and treats engineering like a vending machine. Put the requirement in, get the feature out, and if it's slow the machine must be broken. They don't feel what the engineer feels: that "small" changes touch ten other systems, that the toggle needs a migration and a backfill and a way to roll it back, that tech debt is real interest and you're asking to borrow again.

Ask an engineer for the impossible and you don't get the impossible. You get burnout, shortcuts, and a team that quietly stops telling you what things actually cost.

So Match the Origin. Mostly.

The simple version of this advice writes itself. If you're an engineer, working for an engineer-turned-CEO is easier. You share a model of what's hard. When you say "this'll take three weeks," they believe you, because they've been the person who had to say it. If you're a marketer, a marketing-turned-CEO already gets why the funnel is leaking and won't ask you to fix it by Friday with one clever tweet.

Shared origin buys you the most valuable thing you can have at work: being believed without a deck. And being believed is what turns into autonomy. Autonomy is where you do the work that's actually worth doing.

If that's all you take from this, you'll pick better than most people do.

But it's not the whole story.

The Real Test Isn't the Background. It's the Respect.

You don't need a CEO who came from your function. You need one who respects it enough to be wrong about it out loud.

Here's where the clean rule breaks. I've worked for an engineer-CEO who was a dream to run marketing for, because they knew what they didn't know and handed me the keys. I've also watched same-origin matches go sour: the marketing-CEO who micromanages every marketer on the team because they're certain they already have the answer.

So background is the starting odds, not the verdict. What actually decides your two years is whether the CEO respects the function they didn't come from.

A CEO who respects it asks questions instead of issuing answers. They get curious when you push back, not annoyed. They'll say "I don't understand how this works, walk me through it" about the exact thing they aren't from. The "why aren't we doing that?" still shows up. But it shows up as a real question, not a verdict you have to spend a week overturning.

A CEO who doesn't respect it treats your entire field as common sense they happen to be too busy to do themselves. That's the one to run from, and it's worse than any background mismatch. A respectful CEO from the wrong field will learn. A disrespectful one from any field won't.

How to Read a CEO Before You Sign

The interview is your only cheap data. Most people use it to ask about equity and free lunch. Use it for this instead.

1. Ask what they got wrong. "Tell me about a time the marketing team, or the engineering team, pushed back and you changed your mind." A respectful CEO has a real story ready. A disrespectful one can't find one, because it never happened.
2. Watch how they describe the other function. Is it a craft with its own logic, or a cost center that's "pretty straightforward"? The verbs give it away. "We just need someone to crank out content" tells you everything you need to know.
3. Find the senior person from your function. If you do growth and there's no marketing leader the CEO genuinely listens to, you are the experiment, and the person with veto power doesn't practice your craft.
4. Ask who owns the call. When your team and another team disagree, who decides, and on what basis? If the answer is always "the CEO, by gut," and that gut was trained in one field, you already know which field tends to lose.
5. Listen for "I don't know." The best thing you can hear in a founder interview is a confident "I don't know, that's why we'd hire you." The worst is a rigid answer about a job they have never done.

If You're the CEO Reading This

Your blind spot is invisible to you by definition. The function you came from feels like skill. The function you didn't feels like common sense. That second feeling is the bug.

The fix isn't to go learn the other craft. You won't, not deeply, and that's fine. The fix is to hire a real peer for it and then actually lose arguments to them. If the person leading the function you're not from has never once changed your mind, you don't have a leader there. You have an expensive executor of your guesses.

The engineer-CEO who trusts a marketer they believe, and the marketer-CEO who trusts an engineer they believe, both beat the founder who quietly thinks the other half of the company is easy.

The Bottom Line

Before you take the job, find out what the CEO used to be. It tells you which half of the company they'll grasp in their gut and which half they'll underestimate.

Match it to your function if you can. That's the cleanest version of a good bet.

But there's a quieter question underneath all of it. Watch how the CEO talks about the work they have never done. If it's with respect, the background barely matters. If it's with a shrug, no title, salary, or mission slide is going to save your next two years.

So ask the thing everyone forgets to ask. Not "is this a great CEO," but "is this a great CEO for me."

FAQs

Should I work for a technical or non-technical CEO?

It depends on what you do, not on which background is better in the abstract. If you're an engineer, a technical CEO usually shares your sense of what's hard, which buys you trust and autonomy. If you work in go-to-market, a CEO from a marketing or sales background is more likely to understand why distribution is messy. The bigger factor than background is whether the CEO respects the function they didn't come from.

Is an engineer-turned-CEO better than a marketing-turned-CEO?

Neither is better on its own. Investors like Jason Lemkin of SaaStr lean toward engineer-CEOs for capital efficiency, but that's an investing view, not a guide to whether you'll enjoy the job. An engineer-CEO tends to underestimate go-to-market. A marketing-CEO tends to underestimate engineering effort. The one who respects the function they didn't come from beats a same-background CEO who micromanages.

How do I evaluate a CEO's background before joining a startup?

Use the interview. Ask for a specific time the work you do pushed back and the CEO changed their mind. Listen to how they describe your function: as a real craft, or as something "straightforward." Check whether there's a senior leader from your discipline the CEO actually defers to. Those three signals tell you more than the founder's resume does.

What if the CEO comes from a different function than mine?

It can still be a great job, as long as the CEO respects your function. A CEO from a different background who asks questions, defers to your expertise, and is willing to be wrong out loud is often better than a same-background boss who assumes they already know your job. The danger sign is a CEO who treats your field as common sense.

Why do engineer-CEOs and marketing-CEOs clash with the opposite team?

Each one leads through the lens of the job they used to have and underestimates the one they didn't. An engineer-CEO can treat go-to-market as a deterministic system and ask why a tactic from a viral post isn't shipped yet. A marketing-CEO can treat engineering as a vending machine and promise features before checking what they cost. The friction comes from not feeling what the other function feels.

What interview questions reveal how a CEO treats other functions?

Three work well. "Tell me about a time the other team changed your mind." "When two teams disagree, who decides, and how?" "What's the hardest part of the work my team does?" A CEO who respects the function answers with specifics and a little humility. One who doesn't will wave the question off, which is the answer you were looking for.