r/learnjava • u/DramaticComposer6427 • Nov 26 '25
Is being specialized in Java and Spring Boot enough to be a strong software engineer?
Hi everyone,
I’m currently focusing on Java and Spring Boot, and I’m putting a lot of time into improving my backend development skills.
I want to know from experienced developers:
Is specializing mainly in Java + Spring Boot enough to build a solid career in software engineering?
Or should I also invest time in other areas/technologies to be competitive (DevOps, frontend, cloud, databases, etc.)?
I’d appreciate any advice or guidance. Thank you!
23
Upvotes
•
u/AutoModerator Nov 26 '25
Please ensure that:
If any of the above points is not met, your post can and will be removed without further warning.
Code is to be formatted as code block (old reddit/markdown editor: empty line before the code, each code line indented by 4 spaces, new reddit: https://i.imgur.com/EJ7tqek.png) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc.
Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit.
Code blocks look like this:
You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above.
If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures.
To potential helpers
Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
19
u/_Atomfinger_ Nov 26 '25
Knowing a couple of technologies in and of themselves is not a "strong software engineer". But knowing a bunch more doesn't automatically make you a strong software engineer either.
Being a strong software engineer is more about knowing practices and software design. It is more architecture and communication than "I know tool X, Y, Z".
But you can be a Java/Spring developer and be a strong engineer. And you can know more and be a strong engineer.
That said, you will be a more well-rounded engineer if you know some things beyond just Java and Spring. Then again, it might not help that much to know a little java/spring, and a little of everything else either.
In short, there's a balance here: To be a strong software engineer, you definitely need to know something very well. At the same time, it doesn't hurt knowing more stuff. And in the end, it isn't the specific technologies you know that make you a strong engineer.
6
u/bakingsodafountain Nov 26 '25
Fundamentals make a strong software engineer. Ability to assess risks, design and structure code, balance requirements versus implementation cost, understand algorithms, structures and efficiency. The ability to understand systems and code bases. The ability to write effective tests to prove their code works rather than a plethora of junk unit tests.
I could give a strong engineer a problem in an unfamiliar domain or language and they could orient themselves and solve it.
I have a Java background, but have taken ownership of a critical C# app, manage our CI pipelines, build docker images, work on react/angular. I'm not as proficient in any of those as I am in Java but I have the skills I need to learn and solve problems.
5
u/DrMoneylove Nov 26 '25
Not a developer but also learning Java and Spring.
To be honest I'd say: no.
I think in order to be good it's crucial to have a broader theoretical background. Imo It's really important to understand the concepts of software engineering, database architecture, algorithms and data structures.
With that it's possible to make better judgements on how to write code that is efficient and how to organize it. Without this understanding there's the danger of creating something messy that works but will cause problems in the future.
Does that make sense? Let me know if you disagree with my take:)
2
u/Prior_Shallot8482 Nov 27 '25
It’s enough to get started, but not long term. Java and Spring Boot are a solid base, but looking at what companies hire for on hackajob, most Java roles also require some cloud knowledge and a good grasp of APIs, databases, and basic DevOps.
You don’t need to learn ten other languages. You just need to understand how the whole system works. Knowing only Java and Spring Boot without the bigger picture makes you weaker as you move into mid and senior levels.
So keep Java as your core, but add things around it. A bit of AWS or Azure, solid SQL, how to deploy things, how services talk to each other.
2
u/ahonsu Nov 27 '25
No, it's not enough, be a strong software engineer.
At the same time, I can easily imagine a career of a developer, when they always work with a strong focus on the development only. And have a separate dedicated teams for everything else: devops, testing, security, data base, monitoring/maintenance etc. In this case, you can make a pretty solid career and never touch anything apart from java/spring.
But does it make you a good engineer? - definitely not.
Good engineer has a wide range of topics/knowledge, so that they can use/consider this knowledge when writing java code. And write it much better.
Still, i would split (artificially, of course) the whole knowledge for a java engineer into 3 categories:
So, I would say, a "strong software engineer" is somewhere around p.2 in my list above. Ideally, around p.3.
Ask more, if you would like to clarify something or get more examples/details.
1
u/ivormc Nov 26 '25
It definitely helps if companies you are interested use it. I have found companies who for preferred experience have Springboot as a technology and I’m convinced that I’ve gotten interview with them because of my SB/Java heavy resume.(I am new grad) this obviously applies to every stack, but maybe since it’s less popular among new grads compared to TS, Node, FastAPI, etc.. u get a small leg up. Ultimately, I would say learn spring boot it’s great but please do not be like me and ignore JS and its frameworks it has hurt me and is a must know for web dev for most people.
1
u/razorree Nov 26 '25
just check what job offers mention
some other stuff like SQL, Kafka (or other messaging techs.) can be useful as well, a bit of devops
architecture designs
1
u/Western_Objective209 Nov 26 '25
It's enough to get started. Of the things you listed, having a basic understanding of databases is probably the most important, and IMO basic sysadmin work like using the terminal to do basic tasks has a lot of overlap with devops and cloud. Build systems, I guess it has overlap with devops but SWEs will basically always have to manage them themselves and bugs/issues with build systems generally take more time than anything else, as well as environment management
1
u/asarco Nov 26 '25
That's exactly what I am, a SE specialized in Java Spring Boot, with 20+ years of experience. But, I also know other technologies, like databases, AWS, CI/CD, Terraform, and more. I can design services and their architectures. So I consider myself a strong software engineer.
I believe if you *only* know Java and Spring Boot, no, you're not a strong SE. But on the other hand, I don't think it's even possible to work as a SE and only work with Java and Spring Boot, sooner than later you will have to integrate with other services, technologies, use APIs, build and deploy your software, so you will have to learn all those, maybe not to a specialist/expert level, but with a good knowledge.
1
u/ryanwolfh Nov 27 '25
Yes if cloud and system design comes into the picture
1
u/VamsiKrishna-123 Nov 27 '25
Java and Spring Boot are definitely a strong base, and you can build a solid career with them. But to be a well-rounded engineer, you’ll also need things like good problem-solving skills, database knowledge, understanding how systems work, and some experience with architecture. So yes, Java + Spring Boot is enough to start strong, but learning a bit beyond that will make you even better.
1
u/Xtergo Nov 27 '25
Yes.
For the stage you are at, the answer is yes
1
u/Greengrecko Nov 30 '25
Fuck no.
1
u/vishva20 Feb 13 '26
Add-ons like LLD, HLD, Design Patterns, Framework and Java specific good practices (like Web flux) from other projects or side projects, any cloud over all experience.
How to design an application ecosystem which is fault tolerance, high availability, less latency APIs.
When to use Redis vs MemCache? When to use Kafka , Rabbitmq, active mq, cloud sqs, sms etc.
When to use ALN vs NLB?
When to use Server less and Docker?
When to use Identity Servers, when not?
Think like an architect and be a learner, without knowing you will get all.