Your CEO's Old Job Is Your New Problem

Imagine two founders who raised the same Series A. Same headcount, same burn, same mission slide on the wall. You have an offer from both. One founder used to write code and the other used to run campaigns. That difference will shape your next two years more than the title, salary, or OKRs, and almost nobody screens for it.

Search "technical vs non-technical founder" and most of the answers are written for investors. Jason Lemkin of SaaStr has said he now invests almost only in engineer-CEOs, or business CEOs with a real technical co-founder, and that non-technical founders need three to five times more money to get started. Maybe he's right if you're writing the check. But if you're taking the job, whether the CEO can pass a system-design interview isn't the useful question. Stop asking "is this a good CEO." Ask "is this a good CEO for what I do."

I've worked for an engineer-turned-CEO, so I know what this can feel like from inside marketing. Growth becomes a feature: input, output, and a bug somewhere if the output is wrong. Then they read a viral thread on Saturday from a founder saying "we 10x'd signups with this one channel." Monday morning, in your 1:1, the question arrives: "Why aren't we doing that?"

You explain that the channel doesn't map to your audience, the case study is survivorship bias with a dashboard attached, and the January tactic is saturated by June. It doesn't land because their model of go-to-market is deterministic. They don't feel channels decaying, brand behaving like a lag indicator, or the same campaign producing different numbers for reasons nobody fully controls. So the week goes into proving why the article on their screen isn't a roadmap instead of running experiments.

That isn't stupidity. It's a different sense of what's hard. The product was the brutal part, so distribution can look like "just" telling people it exists. And marketers make the same mistake in reverse. I've worked for a marketing-turned-CEO too. They see a competitor's feature, sell the demo before it exists, promise a date to a customer, and ask, "How hard can it be? It's just a toggle."

It's never just a toggle. The marketer-CEO can treat engineering like a vending machine: requirement in, feature out. They don't feel how a "small" change can touch ten other systems, need a migration and backfill, require a rollback path, and add more interest to the technical-debt loan. Ask a team for the impossible and you don't get the impossible. You get burnout, shortcuts, and engineers who quietly stop telling you what work really costs.

The clean advice, then, is to match origins. An engineer working for an engineer-CEO shares a model of difficulty. When they say "this'll take three weeks," the CEO believes them because they have been the person saying it. A marketer working for a marketing-CEO doesn't need a deck to explain why a funnel leaks or why one clever tweet won't fix it by Friday. Being believed creates autonomy, and autonomy is where the worthwhile work happens. If that were the whole rule, it would already be useful. It just isn't the whole rule.

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.

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 a marketing-CEO micromanage marketers because they were sure they already had the answer. Background changes the starting odds. Respect decides much more. A respectful CEO asks instead of announcing. The "why aren't we doing that?" can still appear, but as a question. They can say, "I don't understand how this works, walk me through it" and stay curious when you push back. A disrespectful CEO treats your craft as common sense they're too busy to do. A respectful CEO from the wrong field will learn. A disrespectful one from any field won't.

The interview is the cheapest chance to tell which one you're meeting. Ask, "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. A disrespectful one can't find one because it never happened. Then listen to how they describe the function they didn't come from. Is it a craft with its own logic, or "pretty straightforward" work where "We just need someone to crank out content"? The verbs usually give it away.

I would also find the senior person from my function. If you're joining growth and there's no marketing leader the CEO genuinely listens to, you're the experiment, while somebody outside your craft keeps veto power. Ask who owns the call when teams disagree and what the decision rests on. If it's always "the CEO, by gut," you already know which function that gut will favor. And listen for "I don't know." The best version is a confident "I don't know, that's why we'd hire you." The worst is certainty about a job they have never done.

If you're the CEO, the blind spot runs the other way. The function you came from feels like skill; the function you didn't come from feels like common sense. You don't need to become an expert in the other craft. Hire a real peer for it and then actually lose arguments to them. If that leader has never changed your mind, you hired an expensive executor for your guesses. An engineer-CEO who trusts a marketer and a marketing-CEO who trusts an engineer both beat the founder who quietly believes half the company is easy.

That leaves me with a different question at the end of the interview. Not "is this a great CEO," but "is this a great CEO for me."