Would you hire someone who cannot code but can build a working SaaS with AI?
Posted by Abdulhamid Mu'awiya Abdull in the Vibe Coding is Life group on September 28, 2026. 281 reactions, 499 comments, 3 shares.
The post asks whether members would hire someone who cannot write code but can build a working SaaS entirely with AI. It was the most discussed thread of the week with 499 comments. Answers ranged from a plain yes, on the view that directing AI well now counts for more than writing code by hand, to a firm no from engineers who expect a hire to debug, use a git workflow and work inside a team. Several replies landed in the middle: test how the person reasons through a problem, and keep a professional involved for the moments when something goes seriously wrong.
The post
Would you hire someone who can't code but can build a working SaaS entirely with AI?
Why it landed
- It is a yes or no question, so anyone could answer in a line.
- The scenario is concrete: a working SaaS, built entirely with AI, by someone who cannot code.
- It puts the value of coding skill up for debate, and both engineers and non-coders in the group answered.
The best answers from the thread
“Sure, you don’t need to be a programmer to build a SaaS. In the same way, you don’t need to be a doctor to perform surgery. The real question is whether you still want a professional involved when something goes seriously wrong.”
“Guaranteed they didn't build a working SaaS. It won't be scalable, it won't be secure.”
“A master interpreter is more valuable than a master builder in TODAY'S world. Maybe not one year ago but today, yes.”
“I'd like to see him work through a problem using pseudo-code, basically using logic to solve a problem. It's not specific to any language, but it shows me how he thinks, processes problems and gets things done. You don't have to be a programmer to do this.”
“No. They at a minimum have to be able to debug into the code, do some simple items by hand, understand how git workflow works and be able to work with a team of developers. If they have a good eye and want to be a BA and direct people after a rough prototype, maybe.”
What to take from it
- If you cannot code, be ready to show how you reason through a problem step by step. One member said that is what he would test.
- Learn the basics teams expect: reading and debugging code, a git workflow and working alongside developers.
- Expect doubts about security and scale, and be ready to show how your product handles both.
- Deep knowledge of a field can be the reason for a yes. One member would hire a subject matter expert.
Join the conversation
Post yours. The best ones land in this archive.
This post was shared publicly in the group and is credited to its author, with a link to the original. Want it corrected or taken down? Message the group admins on Facebook and it comes down.