My Roadmap: Self-Taught Developer to Full Stack Engineer
Four years ago I shared how I broke into tech. A lot has changed. Here's the updated roadmap I'd use today.
Four years ago, I wrote "Becoming a Self-Taught Frontend Developer." I was nervous, filled with imposter syndrome, and figuring it out as I went. I'm writing this update because the map has changed.
The tech world of 2021 feels like a different era. Back then I was laser-focused on the frontend. Today I'm a Full Stack Software Engineer in financial services, working on secure, scalable, cloud-native platforms. My toolkit has grown from JavaScript and React to include .NET, C#, TypeScript, SQL, and Microsoft Azure.
This isn't a success story. I learn something new every single day. But I feel a responsibility to update the map.
My Path Wasn't a Straight Line
Looking back, I can see three distinct chapters.
Junior contractor at a London consultancy. Theory met reality fast. Client deadlines, existing codebases, refactoring React and Next.js apps I didn't write. One of the most valuable things I did wasn't building something new it was making something old better.
TechSwitch bootcamp. You might ask: why do a bootcamp after already working as a junior? For me it was a strategic decision. I had practical experience but gaps in foundational, team-based workflows. The program simulated a real development environment version control best practices, full-stack methodologies, the kind of complex problems that don't show up in online tutorials. It formalised my self-taught skills and landed me my first full-time role at People's Partnership.
People's Partnership. This is where I truly pivoted to full stack. Financial services means security, scalability, and reliability are non-negotiable. It also taught me that engineering isn't just technical communication and collaboration matter just as much.
The Roadmap I'd Follow Today
The number of technologies out there is paralyzing. You don't need to learn ten frameworks before landing a job. You need a focused, battle-tested path.
#0 CS50 (Core Foundation)
Start here. Harvard's Introduction to Computer Science on edX teaches you how to think, not just how to write code. The problem sets are hard. That's the point. It gave me a framework for turning abstract ideas into concrete reality.
#1 HTML, CSS, JavaScript
Non-negotiable. Don't rush through them. In 2025, deep knowledge of modern JavaScript Promises, async/await, modules, array methods is more critical than ever.
Resources: The Odin Project · freeCodeCamp · MDN
#2 React
Learn React to learn JavaScript. Reading the React source code to understand the why behind the library makes the whole thing click. Without real-world context, learning is a draining experience.
#3 TypeScript
This is the single biggest change from my 2021 advice. TypeScript is no longer optional. It's a requirement for any professional role. Catch errors during development, not when your users do.
Resources: Beginner's TypeScript · freeCodeCamp TypeScript
#4 Git
Master your tools. Git is the industry standard you need to know it to collaborate, track changes, and manage a codebase.
#5 Backend (Node.js or .NET Core)
Going full stack means choosing a backend. I've used both. The core concepts of building APIs are transferable it doesn't matter which you pick first. My journey led from TypeScript/Node.js to .NET Core because of enterprise demands, but Node.js is equally marketable.
#6 Databases (SQL first)
SQL is the foundation. I started with MySQL, moved to PostgreSQL, and now use T-SQL in a financial environment where data integrity is critical. Learn SQL thoroughly before worrying about NoSQL.
#7 Cloud (Azure, AWS, or GCP)
It doesn't matter which you pick. The core concepts virtual machines, storage, databases, networking are transferable across all three. My path led to Azure. The AZ-900 certification is an excellent entry point.
Wrap Up
If this feels overwhelming, that's valid. Imposter syndrome is real. I still feel it. Every developer does, at every level.
The secret is understanding you'll never know everything. The most important skill isn't mastery of a specific framework it's learning how to learn.
Focus on growth, not perfection. Code a little every day. Build small things. Break them. Fix them. Ask for help.
Your journey begins with that first problem you solve.
Comments