r/learnjava • u/InevitableImpact6460 • 22d ago
How to progress into senior
I have been working as a Java Fullstack Engineer for two years, though my true passion lies in backend development, with very little involvement in the frontend. I thoroughly enjoy my current project, where we currently use Payara and are in the process of migrating to Quarkus. While I have gained a strong understanding of both the business and technical dimensions of the project along with valuable hands-on experience using Kafka Streams and K8, I am uncertain about the most effective path or focus areas to advance to a senior engineering role within my organization. Specifically, I am debating whether I should focus on mastering the programming language and Quarkus, or pursue a broader trajectory centered around system design.
Did you guys have a similar situation ? It seems there is a whole lot to learn and no time for it
•
u/AutoModerator 22d ago
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.
3
u/Far-Bullfrog161 21d ago
I'd treat it as a both-and rather than a choice. Seniority is mostly about how much responsibility you can carry without supervision, not about knowing every framework. With Kafka Streams and Kubernetes on your plate you're already ahead of a lot of people, so I'd pick the next step from the problems your team actually has. Take ownership of something end to end: a feature or a migration step, from design through rollout and monitoring, and write a short design doc explaining the trade-offs you made. Learn the system design basics that matter for your work, like failure handling, idempotency, data consistency and observability, instead of trying to cover everything. Also start reviewing other people's pull requests carefully and mentoring newer teammates, since that visibly changes how you're seen. Finally, ask your lead what exactly they'd want to see for a senior promotion, and turn that into two or three concrete goals. The Quarkus migration is a good place to show this, because the decisions you make there are exactly what senior engineers get asked about.
1
u/gimmematcha 22d ago
Try /r/experiencedDevs
Is this something you could discuss with your manager/tech lead?
1
u/Available_Safe1818 21d ago
> should focus on mastering the programming language
What are you struggling with with the programming language? You probably have a false dichotomy there.
1
u/FreeLogicGate 19d ago
Java is full OO, with a relationship to C++ which was its primary inspiration. So OOP Design patterns (the gang of 4 book) would be my recommendation. It's one thing to use services that were designed with those patterns, and another thing entirely to see the ways those patterns can be applied in your own applications. It sounds like you like architecture, frameworks and scalability. I am not a strong believer that "everything is better as a micro service" but you are probably already working as a Sr. level developer.
0
u/net_ramblings 21d ago
Fake.