DEV Community

Cover image for My Journey from Front-End to Full Stack Developer
Shankara Perumal Arunachalam
Shankara Perumal Arunachalam

Posted on

My Journey from Front-End to Full Stack Developer

When I started out, my world was mostly HTML, CSS, and getting pixel-perfect designs to work across browsers (RIP old Mozilla/Internet Explorer bugs 😅). I didn't touch a backend for a long time — the idea of servers, databases, and APIs felt like a different universe.

Over the last 6+ years, that changed one project at a time.

The early days

I started as a front-end-focused developer back in 2020, and even something like Bootstrap 4 was brand new to me at the time — I was still getting comfortable with grids, breakpoints, and making things responsive without everything falling apart. Later on, Bootstrap 5 came along and felt like a big shift to learn all over again.

Looking back, that's honestly a good reminder — even the "basics" keep evolving, so there's no real finish line where you stop learning even the fundamentals.

It was satisfying work — seeing a design come to life in the browser — but I kept running into a wall: I could build the "what you see," but not the "how it actually works" underneath.

Crossing over to the backend

The shift happened gradually rather than overnight. I started picking up Node.js and Express to understand how APIs were built, then MongoDB to see how data actually gets stored and queried. Every new piece I learned made the previous piece make more sense — REST APIs suddenly explained why my front-end calls behaved the way they did, and understanding databases changed how I thought about state on the client side too.

Somewhere in there, React became my main tool for the front-end, and the pieces started connecting into something that felt like a full stack rather than isolated skills.

Where I am now

Today I work across the MERN stack — React, Node.js, Express, MongoDB — along with TypeScript, Next.js, PostgreSQL, and Redis, depending on what a project needs. I've also picked up things like building personal projects end-to-end, from the database schema to the deployed app, which taught me more than any single course could.

What I'd tell my earlier self
You don't need to master the backend before you start touching it — build small things and let the confusion guide what to learn next
Front-end skills aren't wasted when you go full stack — understanding the UI deeply makes you better at designing APIs that actually serve it well
Even the "basics" (like Bootstrap versions) keep changing — staying comfortable with being a beginner again is part of the job
The "full stack" label isn't a finish line, it's just... more surface area to keep learning

Still learning something new every week

Top comments (0)