Stage 4 — CEO conversation
30 minutes with the founder/CEO. Not a technical interview. Not a culture-fit drill. It's a vibe check at altitude — would the CEO want to bet on you for the next several years? Match their energy. Ask big questions. Close the deal.
01What this stage is really about
By the time you reach the CEO, you've passed every other gate. They're not relitigating your skills. They're checking three things:
- Conviction — do you actually want to be here, or are you shopping?
- Trust — would they put you in a customer meeting? Would they be embarrassed?
- Resonance — do you "get" the business? Can you have a conversation about strategy without flinching?
This is the easiest stage if you treat it as a conversation, the hardest if you treat it as an interrogation.
02How to show up
Do
- Bring questions about the business, not the codebase
- Have a thoughtful take on their market
- Listen more than you'd think — let them talk about what they care about
- Be direct about wanting the role at the end
- Treat them as a peer in a conversation, not as someone to impress
Don't
- Re-pitch your technical skills
- Get into salary specifics here unless they raise it
- Be evasive about competing offers — but don't bluff either
- Sound like every other applicant — "I'm so excited about your mission!"
- Be afraid to disagree thoughtfully
03Questions they'll likely ask
"Tell me about yourself" (yes, again)
Different audience, different emphasis. The CEO doesn't need the tech stack list. Lead with the builder/entrepreneur side this time.
"I'm a senior frontend developer with about ten years in. I'm currently at Artlist, mostly working on performance and frontend infrastructure. What's probably more interesting to you is what I do outside of work — I run a couple of side products and a YouTube channel, all of which I built and operate solo. The reason I bring that up: I understand what it's like to ship things end-to-end, to own a product all the way from infrastructure to growth. That's what drew me to Omnesoft — the chance to do that at a real company, not just on the side."
"Why this role over others?"
Honest answer at this stage:
"Three things. First, the stage — Omnesoft is small enough that I'd see real surface area, not just one slice of a big codebase. Second, the domain — ERP for fabrication is a real-world problem with real customers, not a trend. And third, the technical match — modern React with TypeScript on complex data UIs is genuinely the work I want to be doing for the next few years."
"What would you want to accomplish in your first year here?"
"In the first 90 days, I'd want to be productive on real features without slowing the team down. Listen, ramp, build credibility through delivery. By 6 months, contribute to architectural decisions — the JD mentions 'help define how a growing engineering team builds software,' and that's the kind of work I'd want to be doing by then. By a year, I'd hope to have ownership of a meaningful piece of the frontend and to have measurably moved one important number — performance, reliability, dev velocity, something that matters."
The shape: quick contribution → expanding scope → measurable impact. Senior arc.
"What do you know about the ERP market / our competitors?"
Be honest without faking expertise. "I'm not a domain expert in ERP — I'd be ramping on that. What I do know: the existing landscape is dominated by legacy systems — SAP, Oracle, NetSuite — that are powerful but feel old, and there's been a wave of newer modern alternatives — Odoo on the open-source side, vertical-specific players like Katana for manufacturing. Your bet, as I read it from the site, is on modern, modular, fabrication-focused. The frontend craft and developer experience are differentiators legacy ERP can't match easily."
If they want to go deeper, that's good — let them tell you about their position.
"What's something you'd push back on?"
This is a senior-IC test. Don't say "nothing." Have a real opinion that's defensible.
Example: "I'd push back on shipping fast at the cost of basic accessibility. Especially for an enterprise tool people use 8 hours a day, accessibility isn't a 'nice to have' — it's ergonomics. I'd want it baked into the definition of done, not retrofitted later."
Or: "I'd push back on premature abstractions in code. Speculative reuse — building 'flexible' systems for needs that may never materialize — costs us velocity now and rarely pays off later. I'd lean toward concrete-first, refactor when the second case actually appears."
Either is a real position with reasoning. CEOs respect that.
"Do you have any concerns about joining us?"
This is a brave question — answer it bravely.
"I want to make sure I have a clear picture of where the company is — funding stage, runway, customer traction. Not a deal-breaker, just something I need to evaluate alongside everything else. And I'd want to be sure the role lives up to its description — a senior IC role with real architectural ownership rather than feature-shop work. Both of those are things I'd hope we can talk through."
Honest, direct, doesn't kill the conversation. They'll respect it.
"Where else are you in process?"
Don't lie. Don't manufacture pressure. The honest, neutral answer:
"I'm having a few early conversations to understand what's out there. I'm not committed to any particular process. If the fit is right at Omnesoft, I'd move forward seriously."
"How do we know you'll stay?"
Tough but fair question, especially for a remote hire.
"You don't, fully. No one ever does. What I'll say: I've been at Artlist for years now — I'm not someone who jumps around. When I commit to a place, I commit. The reason I'm even looking is that I want my next chapter to be intentional, not reactive. If I sign with you, it's because I see this as that next chapter — not as a stepping stone."
04Big questions to ask the CEO
The full list is on the questions page. The strongest for this stage:
Vision questions
- "Where do you see Omnesoft in 3 to 5 years?"
- "What's the personal 'why' that made you start or join this?"
- "How do you think about competing with the SAPs and NetSuites of the world?"
Reality questions
- "What's the hardest part of building Omnesoft right now?"
- "What would have to be true a year from now for you to call this hire a great one?"
- "What's the most important thing your team has gotten right so far? Wrong?"
Customer questions (CEOs love these)
- "What's a customer story that's stuck with you — someone you helped in a way that surprised you?"
- "What's the most common reason a prospect doesn't become a customer?"
Closing question
- "What's the next step from here?" — direct, professional, expected.
05Closing the conversation
Try something like:
This was a really useful conversation. Based on everything I've learned across these stages, I'd be excited to take this forward. What's the next step from here, and what do you need from me to keep things moving?
Direct, professional, signals interest without sounding desperate. Then let them respond.
06If they ask about salary at this stage
Some CEOs handle the offer directly at the end of stage 4. If they raise comp:
- Don't blurt a number. Take a breath.
- "Based on the seniority of the role and what we've discussed, I'm in the $70,000 to $90,000 USD range, depending on the structure of the package."
- Pause. Let them respond.
Full negotiation prep on the salary page.
07Mental frame walking in
You're a senior person with options, having a conversation with the founder of an interesting early-stage company. They've already decided they probably want to hire you — you wouldn't be in this room otherwise. The job here is to confirm the match, ask the questions only the CEO can answer, and decide whether you want to take this forward.
Drop the audition energy. Bring the peer-conversation energy.