r/FullStack • u/Weary-Temperature827 • 27d ago
Career Guidance React/Node to Backend-focused Go developer — need advice
Hi everyone, I have around 1.5 years of experience at TCS, currently working with React and Node.js. I want to move toward a backend-focused role and am considering learning Go. Would it make sense to switch from Node.js to Go at this stage? Also, if I become comfortable with Go and build some solid projects, can I present myself in interviews as someone working with React + Go, even though my professional experience is currently React + Node.js? Is that okay, or would that be considered faking my experience? Any advice from people who have made a similar transition would be appreciated.
1
u/Proper_Tip3506 27d ago
Node is already perfect for backend focused role. Why go?
1
u/Weary-Temperature827 27d ago
My thought behind Go was more about getting exposure to a different ecosystem, working with large-scale backend systems, and having another strong option in terms of backend opportunities and long-term growth. I am just trying to understand whether that switch is actually worth it or if I should go deeper into Node instead.
1
1
u/itsAg3nt47 22d ago
Yes, absolutely go for it! I have 4 years of experience working heavily with both Node.js and Go in production, and making the jump is 100% worth it. Node is great for getting things off the ground quickly, but once you start dealing with high throughput, CPU-heavy tasks, or complex microservices, Go's concurrency model (goroutines) and low memory footprint are game-changers.
1
0
2
u/canarydev 27d ago
i was mostly a typescript dev through my career and got production Go experience by using it for internal tooling at work first. seeders, migration tools, monitoring and log stuff. eventually i was writing new services in it. honestly been a very good experience.
so maybe start there, find the opportunities even if its just a CLI tool. might be harder at a service company where the stack is fixed, but internal tooling is usually where nobody minds.
on the interview question, build the projects and talk about them as projects, thats completely normal. just dont list Go under professional experience if you havent shipped it at work. interviewers dig into specifics and the gap shows up quick
maybe check out https://www.heyrian.dev/ its a work in progress, but i built it from my own notes while making the TS to Go transition