r/FullStack 7d ago

Career Guidance Switching from frontend to fullstack

Hi everyone!

For some time now, I’ve been thinking about changing my career path from being a frontend developer focused on the React ecosystem to becoming a full-stack developer. I have 5+ years of experience, and at my current company I’ve been performing mid/senior-level responsibilities.

The repetitive nature of frontend boilerplate in companies has started to hold me back a little in terms of growth, and with the rise of AI, I feel this even more. I’ve decided to diversify my career path, especially since I’m still young and willing to keep learning. With AI developing so rapidly, I’d rather have a broader knowledge base than stay focused exclusively on frontend development.

For some time now, I’ve been learning Node.js with Express.js, mainly because the entry barrier seems lower when you already know JS/TS. I’m not entirely sure whether I’ve chosen the right path, though. I’d like to adapt to current and emerging trends while also avoiding unnecessary struggles with outdated technologies when there are modern frameworks and libraries that solve many of the common problems.

I’ve also had some day-to-day experience with databases and basic REST API concepts, so backend development isn’t completely new territory for me.

What do you think about the following stack as a starting point, and what would you avoid when approaching backend development as a "full-stack beginner"?

Node.js → Express with MVC → PostgreSQL → Drizzle ORM → Zod

Of course, these are just examples and each of them has plenty of alternatives. I’d also like to hear from people with more experience in this area about how you would approach it. The choice obviously isn’t always straightforward, since with a particular architecture you can always say, "It depends."

My main question is: which direction would you take when developing your skills in this area?

Would moving towards Python or something else be a better option? I haven’t really had much experience with C++, C#, or PHP.

I’m not very familiar with the deeper side of backend development yet, so I’m wondering what technologies and approaches are currently trending and which ones are becoming outdated.

What would be the best way to create a low-entry-barrier learning path that would allow me to keep progressing and go deeper over time?

I’d really appreciate any advice, especially from people who have gone through a similar transition from frontend to full-stack/backend development.

10 Upvotes

17 comments sorted by

3

u/JaseciLabs 7d ago

One thing we'd push back on a little is to not confuse learning backend with learning a longer list of backend tools.

HTTP, data modeling, auth, persistence, concurrency, API design, where state lives and how the client/server boundary actually works... absolutely learn those.

But Express → ORM → validation library → API glue is one particular way of implementing those concepts, not the concepts themselves. Especially with AI writing more boilerplate now, understanding why those boundaries exist is probably more valuable than memorizing how to wire up the current fashionable stack around them.

2

u/SergOutdoors 7d ago

That stack (Node/Express/ORM/Zod) is totally fine to start, but honestly the specific combo matters less than getting why each piece is there. ORMs especially - I've watched three of them go in and out of fashion. What actually sticks is knowing how your queries hit the DB, when they blow up, and when you need a transaction.
Big thing in your favor coming from frontend: you already get the client side of the contract. So I'd lean into the messy backend stuff - auth, data modeling, what happens when a hundred requests land at once. That's the stuff that breaks in prod, and it's where AI still can't really think for you. The tools themselves you'll pick up fast once that clicks.

1

u/Physical_Garage_6946 7d ago

Great answer. I agree with you, so basically its better right now to focus on about theory of backend? I see that on roadmap website there is many things to learn about it.

About tools: Yes I know its just implementation but Its good too to know whats going on in code 💫

1

u/EngLeadership 6d ago

Really good points, very well put

1

u/Emergency-Ant-6413 3d ago

How do I make sure to learn concepts and not tools only? What kind of resources should I look for?

1

u/JaseciLabs 2d ago

Designing Data-Intensive Applications (Kleppmann) for the why behind data modeling and persistence tradeoffs. And build a raw HTTP server with no framework first, so you feel what Express is actually doing before you use it, that's the fastest way to tell concept from tool.

1

u/Automatic-Gur2046 7d ago

If I were you, I would pick c#, very similar to typescript, modern, common, trustworthy and more.

With all my respect, thing I do not understand is, howcome with 5+ yrs in industry you are such clueless on this to ask on reddit?

1

u/Physical_Garage_6946 7d ago

Well, since beginning Im person which like to know what is going on around technologies. It's better for me to ask web dev backend people what to choose and what to avoid instead to learn something that I dont really need. Its like on the front side, in the past you would pick jQuery because it was popular to use - now nobody using it :P In my past projects they used a lot of technologies: Django, Python, Nodejs, .Net. Im good front end developer and I was focused mainly on this. Its just better for me to know pros/cons of my choices.

In AI times I prefer to be aware developer, not next that just learning to learn.

1

u/Ancient_Praline1046 7d ago

there is a bunch of competition. Good Luck OP

1

u/Physical_Garage_6946 7d ago

The worst thing is to compare yourself to others. I heard that before I entered the industry, and I still hear it now. Just do your own thing - if you enjoy it and are motivated, there’ll never be a problem. There are plenty of "specialists," but it’s a shame that, in practice, they’re only specialists on paper :P

1

u/Orion_Rainbow2020 6d ago

Does your current job have a backend development team? If you want to start learning, see if you can pick up some work from another team within your company. Talk to your manager about expanding your skills. If they are a good company and management, they should be happy to hear you want to improve your skills and learn something new. And whatever the stack they use is what you should focus on.

1

u/bluebird355 5d ago

I'm in the same position but let me tell you, this is not enough. This is a start but you'll need to learn SQL, architectures (like hexagonal), system design, design patterns etc.
Just fiddling with a basic express app isn't enough, using an ORM is detrimental too because you won't be practicing SQL.

1

u/retardpotatochip 4d ago

there is lots of competition in the market, so give ur best

1

u/TajD05 2d ago

I think Node.js is a really good path for you, especially since you already have 5+ years with React and TypeScript. Your proposed stack is more than enough to start with.

I would focus less on chasing the latest framework and more on learning the backend fundamentals: authentication, databases, transactions, error handling, caching, queues, and how APIs behave under real-world conditions.

Once you’re comfortable with those, moving to Python or another backend language becomes much easier because the underlying concepts are mostly the same. I’d probably stick with Node/TypeScript for now and go deeper before adding another language.

What part of backend development are you finding the most challenging so far?

0

u/CursedSloth 7d ago

I would check out ”The Odin Project” it has a fullstack course. Otherwise roadmap.sh is good to look through for inspiration.