All video posts

Career change · Getting hired · Roadmap

Breaking Into Tech From Zero: My 90-Day Plan

Imagine I lost everything today: my businesses, my network, my reputation. If I had to break into tech again from scratch, with no CS degree and no years of experience, this is exactly how I would do it. Three 30-day phases: build the foundation, get real-world proof, then land the job.

Deric YeeDeric Yee 16 November 2026 6 min read 7 min video

Prefer to read? The full article is below. Watch on YouTube.

The short version

  1. 1Pick one path, not ten. Choose by demand, leverage and entry barrier.
  2. 2Learn with a 70/30 split: 30% courses, 70% building and breaking things.
  3. 3Build hireable projects that solve a real problem end to end and are deployed publicly, then document them properly.
  4. 4Stop spamming applications. Target 10 companies, tailor 10 applications and reach out to 10 people.
  5. 5Prepare real stories, not memorised answers, and act like you are already in tech.

Why most people fail before they start

I have spent years building tech businesses, mentoring students and hiring developers. The pattern I see most is people failing in the very first phase. They pick the wrong path, chase certifications or binge tutorials without ever doing anything.

So this plan is built from first principles: what actually matters, what does not, and how to avoid spending years spinning your wheels. Ninety days is an aggressive timeline that needs focus and consistent action every single day, and everyone's pace is different. The structure is what matters: foundation, proof, then closing.

Days 1 to 30: Choose one path

There are hundreds of roles in tech. You need one. Choose it based on demand, leverage and the barrier to entry. If I were starting today, these are the three I would consider.

01

Software engineering with cloud

AWS, Azure or Google Cloud. You help businesses deploy, scale and manage infrastructure. High demand, high leverage and good pay. This is how I started, and it opened doors for me.

02

QA engineering

You test products, find bugs and protect quality. It is a quiet way into development teams, and you learn how software actually works from the inside.

03

IT support or sysadmin

Not glamorous, but stable, with plenty of remote roles, and excellent for learning fundamentals.

Days 1 to 30: Learn with the 70/30 rule

Forget 100% tutorial bingeing. When I learned, about 30% of my time went on learning and 70% on doing. The 30% was Udemy, YouTube and freeCodeCamp, for example an AWS Cloud Practitioner course. The 70% was spinning up EC2 instances, deploying apps and breaking things left and right. I believe retention only really happens when you build. The AWS free tier, Codecademy and freeCodeCamp were my main tools.

Then build yourself a learning operating system. Use Notion or similar to track what you are learning, what you are stuck on and what to build next. I keep a personal dashboard of links, project ideas and concepts I do not yet understand, so I can come back to them. You do not need a perfect memory. You need a system to recall and reapply. If you are still choosing a language, start with picking your first programming language.

Days 31 to 60: Build hireable projects

Skills are close to useless without proof. Companies do not care what you know; they care what you have done. This phase is where you make yourself undeniable.

Anybody can build a web app, so do not be that person. Build what I call hireable projects: based on a real business problem, solving it end to end, and deployed publicly. Do not send a GitHub link and expect someone to spin it up. Deploy it so anyone can use it immediately.

For a cloud path, that might be a three-tier web app on AWS: front end on S3, back end on EC2, database on RDS, with IAM roles, logging and cost monitoring. Now you are not just clicking buttons; you are showing real-world competence. For more ideas, see portfolio projects that get interviews.

Days 31 to 60: Document like a pro

Most people build something and then ghost their own work. Huge mistake. If you do not document it, nobody understands what you built. I use what I call the BUILD framework:

Background: what problem are you solving? Understanding: what was your thinking process? Implementation: how did you build it? Lessons: what went wrong and what did you learn? Deliverables: where can I see it, on GitHub or a live site?

Write it up on GitHub, Notion, LinkedIn or Medium. Of everything in this plan, writing about your projects is one of the shifts I have seen make the biggest difference to whether people get interviews. Your project is not real until it is public.

“People are drowning in resources, but they're starving in clarity.”

Deric Yee, in the video

Days 61 to 90: Stop spamming, start targeting

Most people are told to apply to 200 or 300 jobs, and they hear back from almost none. The reason is that mass applications are lazy. I recommend the 10/10/10 method: pick 10 companies you genuinely want to work for, send 10 tailored applications with a custom CV and message, and reach out to 10 people who work there or the hiring managers. Most people never do this, which is exactly why it works.

Network like a founder. When I was hiring, I did not care about fancy CVs. I cared about people who showed up in my inbox with curiosity, clarity and some proof. On LinkedIn, do not just send "hi". Send a short intro saying who you are and what you are building, a portfolio link that looks good, and a thoughtful question about the company or role. People love helping builders, so be one.

Days 61 to 90: Prepare with context, not scripts

Do not memorise interview answers. Understand the problem they give you and what they actually care about. Hiring managers usually want to know three things: can you solve problems, can you work in a team, and can you learn fast?

So prepare real stories. The deployment issue you fixed at 2am. The scrappy dashboard you built that saved someone hours of manual work every week. Stories create emotion, and emotion makes you memorable when they are speaking to dozens of candidates who all sound the same. Use Glassdoor reviews and practice platforms to prepare. Our junior developer interview questions guide is a good starting point.

Bonus: act like you are already in tech

If you act like a student, people treat you like a student. If you act like a peer, they treat you like a peer. Contribute on GitHub, join Discord, Slack or Facebook communities, and write weekly posts about your progress. You do not need permission to build a presence.

The tech industry does not have a gatekeeper problem. It has an action problem. Everyone does the same projects, reaches out to the same people and sends the same AI-written cover letter. Follow a clear path and you have clarity and momentum that most people lack.

Start small, move fast and keep iterating. You are not waiting for opportunity; you are building it. If you want a guided way to build that foundation and those projects, start with our free trial.

Questions people ask

  • Can I really break into tech in 90 days?

    Ninety days is an aggressive target that needs focused, daily effort, and many people take longer, especially while working. The value of the plan is its structure: one chosen path, mostly hands-on learning, deployed projects that solve real problems, and targeted applications. Follow that order and you avoid the years many people lose to tutorials and scattered effort.

  • Which tech role is easiest to start with?

    It depends on your background, but roles with clear demand and a reasonable entry barrier include cloud-focused software engineering, QA engineering and IT support or sysadmin work. QA in particular is a practical way into development teams because you learn how software is built while testing it. Pick one role and commit rather than dabbling in several.

  • What makes a project hireable?

    A hireable project solves a real business problem end to end and is deployed publicly so anyone can try it with one click. It should be documented clearly: the problem, your thinking, how you built it, what went wrong and where to see it. That combination shows practical competence far better than tutorial apps or an unexplained GitHub link.

  • How many jobs should I apply for?

    Fewer, better applications usually beat mass applying. Try picking 10 companies you genuinely want to join, tailoring your CV and message for each, and reaching out directly to people who work there or the hiring manager with a short intro, a portfolio link and a thoughtful question. Personal, specific outreach stands out because so few applicants do it.

Your next step

Our 12-week AI-Native Software Development Programme is a live, mentor-reviewed cohort where you build and ship real products with AI, and learn to explain every line. Start with the free trial to see how we teach, then decide.

Watch next

All videos

Learn the fundamentals that pay off in any direction.
Coding plus AI, taught properly.

Whatever you end up doing, the people who understand how software and AI actually work get to direct them. Try the first lessons free, no card needed, or see the full 12-week AI-Native Software Development Programme.