Every engineering leadership role I've looked at in the last six months wants the same person.
Zero hand-holding. Full ownership. Strong opinions that turn into shipped code. Product instincts, infrastructure instincts, architectural instincts, all in one seat. The job specs have gotten honest about it, which I appreciate. They're not hiring managers. They're hiring founders without equity.
I've written a couple of times now about why this shape has emerged and why it's the only engineering leadership mode that still makes sense. What I haven't written about is the trap underneath it, and I want to do that today because I think it's where a lot of good leaders are about to get broken.
Here it is. Most companies want founder-mode execution. Almost none of them want to grant founder-mode authority. The gap between those two is where the role eats people alive.
What founder authority actually is
I ran Elements Software for almost four years. Bootstrap, full-stack, wear-every-hat. What mattered about that experience wasn't the technical work, which in retrospect was fine but not extraordinary. What mattered was the authority.
When a regulator flagged a concern about our compliance posture, I decided how we responded. Not a committee. Not a product manager filing tickets for my team to investigate. Me. I read the regulation, I decided what we'd change, I implemented it, and I wrote back. The whole loop closed inside one person.
When a customer asked for a feature that I thought was the wrong direction for the product, I said no. Not "let me escalate that" or "we'll take it into consideration." No. I could do that because the product was mine. The consequences of the no were also mine, which is the part most hired leaders don't get to experience.
That's founder authority. It's not a title. It's the ability to decide, commit, and be accountable in a single continuous motion, without friction between the three.
Hired leaders at most companies have the accountability. They rarely have the other two. Decisions get staged through approval processes. Commitments get softened by "alignment" meetings. When something goes wrong, they're the ones who wear it, but the decision that caused it was rarely theirs alone.
What companies offer instead
The job spec says founder. The org chart says something else.
What you actually get, in most of these roles, is a narrow pocket of autonomy surrounded by a thick layer of stakeholder management. You can decide how to build the thing, maybe. You usually can't decide whether to build it. You definitely can't decide whether to not build something else to make room for it. You can execute fast inside your pocket. Outside the pocket, you're lobbying.
The tell is in the interview. Listen for how they describe decision-making. If it's "we work closely with product and design to align on the roadmap," that's a consensus organization. Consensus is fine, it's a legitimate way to run a company, but it's not founder mode. A founder doesn't align with product. A founder is the product, or they're not the founder.
Listen for who sets scope. If scope gets set by someone else and handed to you for execution, you're not owning a closed system. You're executing someone else's closed system from inside. That's a perfectly reasonable role. It's just not the role the job description is describing.
Listen for what happens when you want to say no. The right answer is "you say no and we deal with the consequences." The answer you'll often hear is some variant of "we'd discuss it and work through it together," which sounds collaborative but is usually code for "you don't actually get to say no."
Why the gap exists
I don't think most companies are doing this cynically. I think they genuinely don't know what they're asking for.
The job spec gets written by people who read a lot of tech Twitter and internalized the idea that modern engineering leadership is aggressive, opinionated, and founder-adjacent. They want that shape on the team. What they underestimate is that the shape can't be grafted on. It grows from authority. Give someone founder-mode responsibilities inside a consensus org and you haven't created a founder. You've created a person with impossible expectations and normal authority, which is a specific recipe for burnout.
The other piece is that actual founders, the ones running the company, are often reluctant to cede the authority required. Not because they're power-hungry. Because it feels risky. The decisions a founder-inside-a-company would make are the same decisions the actual founder is accustomed to making, and handing them over is hard. So they hire for the shape, fail to hand over the substance, and then wonder why the hire isn't working out.
Neither side is malicious. Both sides are often surprised when the role doesn't work.
The burnout pattern
I've watched this one play out enough times to describe it cleanly.
Month one is great. The new leader is energized. They have strong opinions. They're shipping. Everyone loves it.
Month three, the first real conflict happens. The leader makes a call that upstream stakeholders disagree with. The call gets reversed, or softened, or "discussed." The leader absorbs it, assumes it's a one-off, keeps going.
Month six, the pattern has repeated four or five times. The leader has started pre-softening their calls. They're still ostensibly owning things but the decisions they make are calibrated against what they think will get through, not what they think is right.
Month nine, the leader is exhausted. They're doing all the work of a founder, carrying all the accountability of a founder, and making decisions with maybe 60% of the authority of a founder. The 40% gap is the tax. The tax compounds. They're still shipping, the metrics look fine, but they've stopped bringing their real judgment to the job because their real judgment keeps getting overruled.
Month twelve, either they leave or they quietly become a different kind of employee, the kind who executes well and doesn't push anymore. The company often reads this as the hire "settling in." It's actually the hire giving up.
What to ask in the interview
If you're interviewing for one of these roles, here are the questions I'd ask. Not the technical questions, you'll have plenty of those. The authority questions.
Walk me through a decision your last engineering leader made that you disagreed with. What happened? Listen for whether the leader's decision stood or got overruled. If it got overruled, listen for how. "We talked it through and landed somewhere in the middle" is a consensus answer. "I pushed back and they made the call anyway" is a founder answer.
What's the last thing your team said no to? A real founder-mode team says no frequently, visibly, and without apology. If they can't name a specific no within the last quarter, the team doesn't have authority, they have influence. Those are different things.
If I want to rearchitect a production system, what does that look like? Listen for who signs off. The right answer is some version of "you make the call, you own the outcome." If there's a design review committee, a staff engineer approval chain, and a product sign-off, you're not owning the system. You're shepherding a proposal through it.
What authority did you hire this role to have that the previous person didn't? This one tells you whether they've actually thought about authority as a dimension of the role, or whether they've only thought about responsibility. If they can't answer concretely, they haven't thought about it.
You'll know within one conversation whether the role has the authority to match the job description. Most of them don't. That's not a reason to not take the role, necessarily. It's a reason to take it with clear eyes, which is very different from taking it hoping the authority will show up later. It won't.
The takeaway
If you're an engineering leader reading a job spec that sounds like founder mode, read it twice. The first time for what they're asking you to do. The second time for what authority they're giving you to do it with.
Then ask about decision authority before you ask about the tech stack. Ask about it before you ask about compensation. Ask about it before you ask about remote policy or team size or any of the things that feel more concrete. Those things all matter less than this one, and this one is the thing you'll wish you'd asked about twelve months in.
Founder-mode execution with founder-mode authority is the role that still makes sense. Founder-mode execution with manager-mode authority is the role that grinds people down.
Know which one you're signing up for.