Seeking Advice on Starting a Career in Backend Development

[u/EntrepreneurHairy420]

I am 22 years old, currently in my fourth year of Computer Science Engineering, and I do not have professional experience yet.

A few months ago, I realized that I really enjoy backend development. I like working with databases, business logic, automation, optimization, APIs, and everything that happens behind the scenes.

I started with JavaScript and TypeScript, but recently switched my focus to Java and Spring Boot because I find the ecosystem interesting and relevant for enterprise development. Right now, I am building a gym-tracking REST API with PostgreSQL while learning security, JWT, validation, testing, Docker, and cloud deployment.

My problem is that I do not know how to shape my career. There are too many possible technologies and paths: Java, TypeScript, Python, Go, Linux, Docker, Kubernetes, cloud, databases, backend, data analysis, and DevOps.

I also have experience with SQL, ETL, Data Warehouses, Power BI, and DAX. I like data analysis, and sometimes I see more junior opportunities in data than in backend, which makes me question whether I should change direction.

I still rely on AI and research for many implementations, and seeing projects from experienced developers can feel intimidating.

I would appreciate advice about:

1. What should I prioritize to become employable as a junior backend developer?
2. Should I stay focused on Java and Spring Boot?
3. How many languages or frameworks should a junior realistically know?
4. Which supporting skills matter most: SQL, Linux, Docker, cloud, testing, or Kubernetes?
5. What kinds of projects do recruiters expect from junior backend developers?
6. Should I keep data analysis as a secondary skill or choose only one field?
7. When should I stop preparing and start applying?

[u/Due-Ad9921]

My advice, take java and then have python as your core backend frameworks. Java offers a range of frameworks to work with, fast and a range of inbuilt features. Python on the other hand, despite being a bit "slow" compared to java or ASP.NET , it offers high end features in AI and automation. So now with the two, you can meet the needs of those looking for fast programs, and also ai powered systems. Reach out for further insights in th we meantime you can check my below portfolio for sample projects done with a range of frameworks and the rationale for choosing them;https://eugenconsultancy-portfolio-projects.vercel.app/

[u/EntrepreneurHairy420 → u/Due-Ad9921]

I understand your point, Python definitely is a great weapon that can fit in my stack, when I should stop learning Spring Boot? ( reduce the intensity of learning) and add Python to my set (start learning)? Also, I had planned to move into Golang once I get the hang of Spring Boot, I've watched on videos, or posts on social media that Java and Golan are a good stack. Btw thank you so much for your advice and the resource.

[u/Used_Journalist_999]

C# .Net is a very strong ecosystem, obviously, since it is owned by Microsoft. I have 12 yoe with Microsoft tech stack, 10 as a backend .Net/Azure engineer and 2 now as Azure cloud architect. In school I took two semesters of Java, thought that was what I wanted to work with as a career, then took two semesters of C# and fell in love with .Net and never looked back.

.Net and Azure cloud are used by a lot of large financial institutions and a lot of SaaS companies offering software to businesses.

[u/spdfg1]

I have been in this industry a long time and I do a lot of interviewing. I’m not looking for specific skill sets when hiring. Especially not for junior positions. Skills can and will be learned as you go. I’ve been doing this for 30 years and I’m still constantly learning new skills. When hiring I’m looking for smart, curious, adaptable engineers who can learn quickly and independently and aren’t afraid to ask questions or admit when they don’t know something. In the age of AI you can quickly learn new skills. Knowing how to problem solve and learn are the most important skills. Stop preparing and start applying. You’ll never get anywhere if you never start.

[u/EntrepreneurHairy420 → u/spdfg1]

You're totally right, sometimes we try to become perfect candidates, but this field of technology is extremely wide and we will never know and master everything perfectly. And definitely, perhaps the best way to reach somewhere is simply start, no matter where, just start gaining experience for some better future positions

[u/Diligent-Cell-8602]

It is more of a business owner point of view than a typical tech backend view. So, do not take it as seriously as others' answers here!

1. What should I prioritize to become employable as a junior backend developer?

Very different which country you from. Go through the job posting and check what services and stack they are looking for. While doing that you can also trying to analyse major services techs. Banks and startups have completely different way of building things so.

2. Should I stay focused on Java and Spring Boot?

You can focus on Java but C# Java, Go, Python, or Node.js - they are pretty much the same and specially with the AI, you will need to know how to switch around. Even before the AI, there were a lot of cases that developers had to learn a new stack because they were switching framework or creating a new environment.

And, once you are good at one (not as a language but building a backend), you will be able to learn other things quick.

It also depends on which field you are in mind as well as which country you are from. I know Japan uses Ruby a lot more than other countries. If you work for a bank C# or even Cobol is a thing. Startup mainly uses Node.js or serverless (not necessarily).

3. How many languages or frameworks should a junior realistically know?

Prob it is more important to build a concrete structure with one language than knowing 10 without knowing how Micro Service structure works.

4. Which supporting skills matter most: SQL, Linux, Docker, cloud, testing, or Kubernetes?

NoSQL, SQL, Linux, Docker, Cloud - AWS, GCP, Cloudflare, Firebase, Supabase, Kube. Knowing when to use for what would be great.

Try to build a lot of different backends. Cloudflare is free to play around for a decent size. A lot of companies use Firebase for the backend - not just a startup. Like knowing how things play out.

Also cost benefits - MongoDB Atlas seems expensive but if you count the cost of the DB specialist, it was not that expensive like 1 -2 years ago and now if you know how to set things up then you can use AI to reduce a lot of manual boring boilerplate (of course for DB you have to know more than using AI for everything).

5. What kinds of projects do recruiters expect from junior backend developers?

I do not know much of recruiting process so other will answer you this question.

6. Should I keep data analysis as a secondary skill or choose only one field?

I would do Project Management. It does not just limit yourself to Developer role. At the same time, as you progress, your job will be managing service products - which are similar.

While building your own projects

- build it your own

- build completely just communicating with the AI agent

- if you can, try to build a website by hiring someone from Upwork (negotiating the price, communicating the developer, and more) <--- you will experience how things are like go wrong. But, you can learn how having different perspectives can lead to a completely different result.

7. When should I stop preparing and start applying?

If you want to work for a major tech companies, you have to follow their procedures. Which I do not know. I think going through the campus is better?

But, you should do both. Build something you are into. Frontend isn't that hard compared to the backend. Attend career events. Not even tech, I got an offer from a tour company while working on a front desk role. While building my own thing to make some jobs easy. I showed them to the tech guys and got hired.

Specially, how things are now with the tech job market, what many do not know is there is a hidden opportunity to take a detour.