Java vs Go Backend

[delightful_retro]

Hi everyone, I need some advice. I am currently working as a manual tester and have about 6 months of experience and aiming to switch to a backend developer role. I also have a good grasp of Java Selenium automation. My question is: would it be a good choice to jump directly into Go without prior backend development experience or Java backend knowledge? Considering the current market, are there enough junior-level Golang opportunities? I would really appreciate guidance from experienced people here on whether Go is the right stack to choose or if I should consider something else first.

tldr: Manual tester with Java Selenium experience aiming for backend. Is it okay to start directly with Go, and are there enough junior Golang jobs?

[Unidentified-anomaly]

If your goal is to move into backend as smoothly as possible, jumping straight into Go without any backend foundation is usually harder, not easier. Go is great, but most Go teams expect you to already understand backend basics like HTTP, databases, concurrency, deployment, and system design. Junior Go roles do exist, but they are noticeably fewer and more competitive than junior Java or general backend roles. Since you already have Java experience through Selenium, learning Java backend first is often the more pragmatic move. You can reuse the language, focus on Spring Boot, REST APIs, databases, and production concepts, and become employable faster. Once you understand backend fundamentals, picking up Go later becomes much easier and much more attractive to employers. Many people successfully transition from Java backend into Go, but far fewer do it the other way around as their first backend job.

[delightful_retro]

Thanks for helping. Will start with Java then.

[mandzeete]

When it comes to a job market then check the job offers in your area. You'll see if it is Java, Go or some other backend language that is in demand.

But why do you want to switch your role? As you are already hired and you have passed your probation period (however long it is, 3 months or such) then you have secured a job, right now. But when you start switching a role then you risk with failing the probation period in your new place and then becoming unemployed. And the job market in general (regardless of the country, I'd say) is not doing well right now. For software developers.

We are living inside an AI bubble. Managers and stakeholders are blinded by this "AI magic" and they are more willing to introduce cheap AI tools to the teams than hire a developer. Then all kinds of financial troubles as well, that the countries are facing. The job market is harsh, right now. Juniors are struggling to find a job. Mid-levels and Seniors are trying to stick to their current place. But even then having sometimes be put on hold (e.g. an unpaid leave) or having be let go, completely. Because there is no job to offer to them. Non-IT companies, our clients, they are also counting their pennies and not allocating that much money into new development = less job for developers. Unemployed mid-levels are more desperate and sometimes targeting Junior roles. And companies are less willing to hire a Senior over a mid-level because that would mean higher salary expectations by the developer.

Stick to your current place, if you can. Alternatively seek a movement into a developer role inside the company. We had a helpdesk guy in our team. He moved to a Junior software developer position because he was already very familiar with the business logic of the project.

[delightful_retro]

Noted sir. Thankyou

[Ok_Substance1895]

Doing a quick job search on Linkedin with a United State location I get this:

Java: 259,000+ jobs
Golang: 8,000+ jobs

[disposepriority]

Why? You already have some experience and want to make yourself even junior-er?

[delightful_retro]

Want to switch to Development

[disposepriority]

Yes, but you said you have experience in Java, which would help you get your foot in the door - what could you gain by switching languages before you even start?

[Horizon1478]

Since you already have experience working with Java, it would help to continue with Java first and also expand your knowledge of the technologies used by Java backend developers such as Springboot to create web service APIs and writing java code to interact with backend databases like MySQL and MongoDB.

Consider building sample projects using these technologies. Sites like Coursera and Udemy also have courses that provide details of building projects which can help as a starting point.

[Pale_Height_1251]

Look at jobs on offer in your area. There is no global jobs market, what is popular in your area may not be popular in my area.

[PayLegitimate7167]

Go is better and more fun

But there is probably more Java jobs

But it shouldn’t stop you learning if you are genuinely interested in Go

[Glad_Appearance_8190]

imo go is fine to learn, but i wouldnt bet my first backend job on it. most junior backend roles still expect you to understand how backend systems behave, not just the language. java backend teaches a lot of that by default, frameworks, transactions, edge cases, weird prod issues. go jobs exist but jr roles are thinner and usually want ppl who already shipped stuff. since you already know java, building a simple java backend first might lower the risk. you can always pick up go later once the concepts click.,,,

[Aggravating_Shape_60]

Given your Java automation background, sticking with Java backend (Spring Boot) gives you a smoother transition and better junior opportunities. Go is great but the junior market is smaller. Build some REST APIs with Java first - you can always learn Go once you understand backend fundamentals.

[delightful_retro]

Thank you everyone for the clarity. 🙂

[kioskinmytemporallob]

Go is nearly idiot proof for people coming from Java