How I Built a Tech Startup Without Being a Senior Developer

Where it started: quitting finance with no CS degree

I still remember deciding to leave a comfortable job in finance to chase a crazy dream. It was 2020. I had no computer science degree and no Silicon Valley pedigree. I was a typical business graduate who felt lost in my career, and I had watched technology transform every industry and thought, why not me? The only problem was that I did not know how to code.

So I locked myself in my room and crammed code like my life depended on it, and honestly it felt like it did, because I was unemployed. Day after day I wrestled with HTML, JavaScript, React, Vue, Express. I was excited by what those skills could unlock, and terrified at the same time. What if this was too difficult? What if I was too old? What if I was not smart enough?

Those early months were some of the hardest of my life. No income, burning through savings, and I basically vanished from my social life. While friends were building careers in what they had studied and enjoying a balanced life, I was debugging until 2am with bloodshot eyes. At my lowest point I seriously considered giving up and going back, because I felt like an impostor. If that sounds familiar, I wrote about feeling like you are not smart enough for tech.

About a year in, I tested my skills against real algorithm challenges and solved four out of five. It hit me that I had become good enough to be useful at an entry level. I did not need to be a Google-level engineer to build my dream. I needed to know just enough to get started, and to attract the right people around me.

The myth that you must be a coding prodigy

There is a rampant myth that you need to be a coding prodigy to start a tech company. Look at Steve Jobs. As Apple co-founder Steve Wozniak recalled, Jobs never wrote code and was never an engineer. He was technical enough to understand and shape designs, and he obsessed over product, users and experience while Wozniak and the engineering team did the hardcore engineering.

He is not alone. Jack Ma was an English teacher, not a programmer. Airbnb was founded by two designers and one engineer, and it was a designer CEO who came up with the idea. Companies like Revolut and Robinhood were not started by a lone coding wizard either.

Do not misunderstand me: technical skill absolutely matters. The point is that you personally do not need a decade of experience or a FAANG background, as long as you fill the gap with your own learning or with technical talent you trust. At its simplest, a startup is a group of people solving a core problem with a product or service. Nowhere in that definition does it say you must write the software yourself. Your job as a founder is to make sure the software gets built, reaches users, and that those users actually want it.

Become dangerous enough, and T-shaped

There are two main paths: learn to code just enough, or find someone who can code while you focus on the rest of the business. I did both. In my year of self-taught bootcamp I did not become a senior developer, not even close. But I became what I call dangerous enough: enough to build simple applications, speak the language and not get misled by engineers. It is like learning the basics of a language before moving country. You do not need fluency, but you should be able to get around and not get fooled.

I am a big believer in being T-shaped: broad knowledge with one deep skill. I went broad in business, product and marketing, and deep enough in code to understand how software is made, picking up Vue, React, Express, Hasura, Supabase and GCP as I needed them to build prototypes. Later I found this matched Naval Ravikant's advice: learn to sell, learn to build, and if you can do both you will be unstoppable. Building means creating value, not only code. Selling means getting others to see that value.

You do not need to be Elon Musk. Stack the skills: a marketer who learns Python at weekends, a project manager who picks up HTML and CSS. And it compounds. James Clear's idea in Atomic Habits is that getting 1% better every day for a year makes you about 37 times better. I was not levelling up that fast, but one more JavaScript function today and one new database query tomorrow added up like compound interest. Over six to twelve months you can go from zero to building basic apps. Our guide on how long it takes to learn coding goes into the realistic timeline.

Finding a technical co-founder the right way

Once I had proved I could learn tech, I knew there were people light years ahead of me, so I looked for a technical co-founder who lived and breathed code. This is where many non-technical founders struggle. They say, "I have a great idea, I just need someone to build it." But ideas are everywhere. Execution is what matters, and in a software startup execution means great engineers. A mentor once told me that starting a software company without a strong technical person is like building a rocket to the moon with nobody on the team who knows physics. You are not even in the game.

How you pitch matters. Do not treat a technical partner as someone who just implements your genius idea. Great engineers have their own ideas. I approached my future co-founder as an equal: here is the vision, here is an MVP and evidence of demand, I will handle business, marketing, sales, fundraising and customers, I know some code, and I would love to build this together and both own it. I offered an adventure and ownership, not a one-sided gig.

Start from the problem, then build scrappy

Because I had learned the basics, my co-founder and I communicated well. I could sit in product meetings and understand trade-offs: if feature X takes three days and feature Y takes one, let us do Y first. I earned his respect by speaking his language and not over-promising things that were not technically feasible.

I also leaned on first principles thinking: what are the fundamental truths, and what do users actually need? For Sigmaschool, the core problem was that traditional coding education was expensive, slow and often ineffective. I did not start with "I need this programming language" or some fancy AI. I started with the problem and the outcome, and that guided every technical decision.

Early on we stitched things together: a landing page builder, a Typeform survey, some Airtable, some Zapier, a little custom script. The goal was to prove the concept and get real feedback. You can go a long way with no-code, low-code and AI tools today. Build a scrappy version 0.1 by any means. Once you have users and data, it is much easier to bring in a great engineer or raise money to build something scalable. Investors are usually more impressed by a founder who held a working product together with duct tape than by someone with an idea and nothing started. If you want to try this yourself, see how to build a SaaS with AI.

Obsess over the user experience

Inspired by people like Steve Jobs and DHH, I am obsessed with product quality. I believe that if you build something great that solves a real need, the money follows. Not being a veteran engineer turned into a strength here. I was not building a bootcamp for elite coders. I was building it for people like me: newcomers who felt lost and wanted a way into tech. That gave me real insight into how to design the curriculum and platform in a user-friendly way.

If you are not coding every feature, your job is to be the voice of the customer and the guardian of quality. I personally onboarded early students, sat in classes, gathered feedback and huddled with the team to tweak things. We applied the 1% idea to the product: every cohort we asked what one thing we could improve. The onboarding email was confusing, so we fixed it. Students felt overwhelmed in week two, so we adjusted the pacing. None of these were earth-shattering, but dozens of small tweaks made the product dramatically better.

Credibility comes from results, not pedigree

As a founder who was not a senior developer, my impostor syndrome was at an all-time high. What I discovered is that when your product and customers speak for you, people respect you. When people are paying, giving testimonials and coming back, that is proof the thing works, regardless of your background.

Investors, partners and employees care less about your CV and more about whether it works, whether it is growing and whether people love it. So focus on the metrics that matter: user success, revenue, growth and retention. You build authority by being the person who deeply understands the customer and the solution, even when you are not the one typing the code.

Why this matters even more in the AI era

You might think this was a 2020 story and the world has moved on. I think it is more relevant now. AI coding assistants like GitHub Copilot and Cursor, and platforms that generate apps from a description, mean someone starting today has far more tools than I did. Competition is higher too, but nobody cares how you built it. They care whether it adds value.

And while AI can help write code, it cannot replace vision, leadership or empathy. It will not tell you which problem is worth solving for real people. Yuval Noah Harari has argued that in a world of advanced AI, human qualities like creativity, ethics and multidisciplinary thinking matter more. Finally, continuous learning is the superpower. I never imagined I would need to understand AI for HR tech, yet here I am learning machine learning basics. Keep the beginner mindset.

If you want to become dangerous enough yourself, the first step is learning how software actually works. That is what our free trial is for: a structured taste of real coding with AI, so you can see whether building is for you before committing to anything bigger.