r/node • u/nian2326076 • 16d ago
Five years of Node.js backend work. Would you stick with Node or learn Java or Go?
A backend engineer has spent about five years building systems with Node.js, Express, Fastify, and Kafka. Their salary growth hasn’t kept up with their experience.
Is Node.js still a strong career choice, or would learning Java, Go, or another stack open up better opportunities?
For anyone testing out another backend stack, try working through the same rate limiter design in both languages. PracHub has system design interview questions for that.
For experienced backend engineers and recruiters, what would you learn or change in their position?
If you’re already applying across stacks, LandOffer’s autofill can fill in the work history you keep typing into application forms.
Would love to hear your honest advice!
64
u/Historical_Friend725 16d ago
I have been doing Node.JS for 10 years now, I have Done Java, C# .Net, C++, Python in the past.
In the real world the language does not matter, especially with AI assisted development.
It would help to use and understand other languages just to gain the experience, but Node.js is not goign anywhere and it works for most SaaS and cloud development needs, the fact that it shares JS with front end web helps it stick around.
What matters is your experience and aptitude.
5
u/AlsonTeteuil-84 15d ago
yeah the fundamentals matter way more than the specific syntax at that level.
5
u/Jamiemufu 15d ago
Right and go fundamentally different from node. With goroutines and channels and such. You can’t tell me someone who doesn’t know the language can just ask AI to do something that is as good as someone with language fundamentals.
You have people saying I just use ai for languages I don’t even know. And they think that totally acceptable.
They are basically vibe coding. And the industry will catch on. AI should be used to enhance not replace.
Many many people here are doing themselves out of the market.
11
u/tzohnys 15d ago
Tech stacks do matter but not for their architecture and performance but for their ecosystem.
There's a good reason that big corporations choose C#, Java. It's because of Microsoft and Oracle. They know who to ask for when things are not working.
They don't have money problems. They don't care about free and open source. They want someone to be legally bound to help them ASAP when they want to.
7
u/jammy192 16d ago
I’d suggest a different direction and maybe get a bit of cloud experience. If you know node most likely you can pick up other languages easily and companies know that. Especially golang, Java might more challenging but still. Soft skills should not be underestimated too
1
u/koenigsbier 15d ago
and companies know that
Well, I'm not so sure about it. I've 10 YOE mostly backend in .NET but also fullstack with several different frameworks. Also been learning Rust for 5 years on my free time and for the life of me it was really hard to find a job with something else than .NET on the backend.
In my experience, recruiters just try to find matching keywords between your CV and the job offer and if it doesn't match you're rejected right away without even a chance to have an interview.
1
u/jammy192 15d ago
Fair point although usually I have the opposite issue - recruiters reach out with roles which don’t really match my profile. Actually one of the jobs I got I initially did not meet the requirements. They liked me during the intro interview so they gave me time to prepare for the coding one. I sturdied python for 2 weeks and passed it.
In my latest interview they did not care about the language at all. You could choose whatever you wished
1
u/koenigsbier 15d ago
Consider yourself very lucky then.
It was super hard to get rid of my ".NET sticker". Even after having passed the beginner lever in Rust, companies wouldn't even hire me to develop in Go even though I think I can be productive very fast. I only very recently found a job involving Node.js
2
u/jammy192 15d ago
Sorry to hear that. The golang rejection is absolutely non-sensical since the idea behind go is that anyone can pick it up very fast.
7
u/SmackYoTitty 15d ago
Language is irrelevant IMO. Sure, know the basics of each language. But with AI, you can code in anything these days. You don’t need to be a expert in said languages anymore. Coding fundamentals are what matters most and thats transferable across languages
5
u/skidmark_zuckerberg 15d ago edited 15d ago
Ehhh as much as some might not agree, with LLMs these days, on the job learning of the ins and outs of multiple languages and tech stacks is not as important as understanding the core fundamentals and the why behind what you are doing. As long as you have strong foundational knowledge, you can ramp up on just about anything in short order.
You can apply all of your knowledge of the backend and engineering experience easily to other stacks nowadays. I haven't worried about this for a couple years now. I jump around between different projects at work with very little ramp up time initially. Python, Go, Typescript, Node, React, etc etc, I don't even care about that part of it anymore. The main thing I really focus on is architecture, scalability, maintainability, product planning and managing expectations.
If you want a job and you need something on your resume, just spend a couple weeks building out a project at home. Commit the time to really learn it and then just mention on your resume how you've used it at a past job. As long as you can answer all questions around it, who cares. It's how I jumped from UI focused roles years ago into more backend leaning roles with Node and Typescript. Don't wait for a job to give you permission to do something.
7
u/lol_wut12 16d ago
Java and C# likely have more job opportunities. Go is great for improving your skillset, but there are fewer jobs available.
I would recommend learning ASP.NET Core (C#); the newer changes to this framework take inspiration from Express.js, so it may be easier to pick up than Spring Boot or whatever Go HTTP framework you reach for.
2
u/LowLifeArcade 15d ago
"the newer changes to this framework take inspiration from Express.js" That's only true for their minimal API. You're still going to be writing the same boilerplate and classes for everything going the .NET route.
1
u/lol_wut12 15d ago
Yes, minimal API is the newer change i am referring to. Using classes is not "boilerplate" in and of itself, and you end up with a similar amount of boilerplate with either Node.js or .NET for a sufficiently complex app. The main difference is that the .NET base class library includes many of the utilities you'd have to install Node dependencies for (database driver, structured logger, metrics collection, HTTP router and basic middleware, etc.)
3
u/DickBrainTime 16d ago
I'd test the market before switching stacks. Pull up 20–30 backend jobs at the salary you want, see what they actually require, and apply for the Node/TypeScript ones now. If your target roles repeatedly ask for Java, Go or .NET, pick one and build a small service with a DB, queues and monitoring. On your CV, show the systems you owned and results you improved (latency, reliability, scale), not just Express/Fastify names. A new language is useful, but the job data should drive which one.
3
u/Dreadmaker 15d ago
So for reference, I worked with node for 5 years and then started to learn Go as a hobby. Got a Go job just a few months later, been there ever since. Love the language, and would recommend it highly.
But also it straight doesn’t matter - they’re all good; more on your CV is just better. Wider experience is a good thing.
3
u/takitus 15d ago
Go is functionally a good language. It’s error handling syntax sucks, but it’s performant.
I still chose node over go a lot.
3
u/Rechenplaner 15d ago
Well, it’s a matter of taste. To me, Go feels like C with a garbage collector; with the added "benefit" that even basic conveniences, like the ternary operator, have been stripped away; it’s just awful.
1
u/takitus 15d ago
That’s why I mostly have ai just refactor projects into go. I like its performance. I don’t like writing it.
1
1
3
3
u/Rechenplaner 15d ago
Java is a hideous OOP language. Yes, the JVM is faster, but in practice, V8 has become so performant that the differences really don’t matter anymore.
Go is faster, but it also has a GC. To me, it just feels like archaic C with a garbage collector tacked on, while the creator forgot to remove the pointers…
Honestly, with JS + types, you have an excellent system in Node; a great compromise between productivity and performance. Especially since the TypeScript type system is so much more powerful than that of any other imperative language!
3
u/MrDilbert 14d ago
I never tried Go. I started my backend journey with Java. I went Typescript/Node and would Never. Go. Back.
2
2
u/luckyincode 14d ago
Go. Keep nodejs. I did a lot of nodejs/java/python and go is making another round.
But really - the fundamentals.
5
u/__brealx 15d ago
Learn AI. I haven’t written a line of code in a year. And created so many tools n languages that I never knew.
4
u/stuckinmotion 15d ago
Yeah language choice seems less relevant, other than it should be typed so the agents can benefit from compiler errors. I just built my first kotlin app, don't really know anything about kotlin..
2
1
u/lulcasalves 11d ago
What to learn in AI? (genuine question) IMO most things in that space are quite easy/fast to pick up
0
2
u/a1454a 15d ago
If you had to ask that question it means you haven’t really advanced to senior engineer capacity. Your experience building app using that stack is rich no doubt, but engineering goes beyond a single stack, can you explain why something should be build using Java or Go instead of node? And vice versa?
There should come a point where you realize coding is the easiest part of your day, especially in the era of AI. Deciding what should be built, how it should be built should become the bulk of your day to day responsibility, not thinking about experiences in a single stack.
1
1
u/Pale_Height_1251 15d ago
Just look for jobs near you, paying what you want, and learn what they're asking for.
1
1
u/Phosphorus-Moscu 14d ago
IMHO learn about Rust, that have a lot of future, I think is obvious that all the ecosystem in JS ins moving to that and the big companies are following that movement changing all their stack to rust directly, it is something progressive but it is happening, with AI or without AI is really important learn about that.
1
1
1
1
u/Sislar 15d ago
I think asking the question shows a lack of understanding of the industry.
When there is a software project to do, find the best tool for the job. If I hired you I’d always get a node solution as if that was the only option.
Learn at least one other language then you’ll start to see it really not about the language.
-2
u/theGlitchedSide 16d ago
Low salary but always work? Java New possibilities in new web and crypto? GO and Python
Become a legend? C++ and become a real dev 🤣
0
0
0
134
u/horizon_games 16d ago
After five years you should know the stack doesn't as matter as much as what you're building and the value you're providing to the company, plus the visibility to higher ups that it's you doing it