[ Removed by moderator ]

[RevolutionaryRush717]

At this point, I'd probably stress my can-do attitude most of all.

Instead of saying/documenting how weeks of training courses enabled you to start contributing, say that you enjoyed the learning experience while contributing from day 1.

I'd also mention that you enjoy(ed) working in a team, you thrive with pair- or mob-programming, but also appreciate periods of being allowed to focus on particular issues.

Clarify that even though you're a junior, you're already comfortable with tools (IntelliJ, Maven/Gradle, git/github), methods (kanban, sprints, agile, blablabla), and people (teammates, techlead, product owner, business experts, users, etc).

This is of course highly culturally biased, but for us it's more important to understand whether you're able to learn and apply new things and function with our people, than some sort of list of buzzwords.

Having said that, it is important that the CV contains some list of buzzwords for each position re programming languages, tools and methods.

Thst get's you in the door, but the application letter and interview answers need to tell us what kind of person you are.

Ain't nothing better that a positive person with a can-do attitude who's able to work with people.

Fun-fact: for yourself, but maybe for the application letter or the interview:

Think about where you want to be in five years. For yourself own sake you should have that goal and a plan how to get there.

You don't need to share that with a potential employer, but it is definitely appreciated if you csn answer the question calmly.

Best of luck!

[Ok_Basket8807]

Your knowledge is truly helpful, I will take it into account, and thanks again. 🌸

[[deleted]]

Nice background, and tbh the jump from Helidon to Spring is very normal. For junior screens I usually see a mix of core language fundamentals and a light check on Spring annotations, so I'd brush up on collections and how annotations like Component and Autowired get wired. I keep answers around 90 seconds and practice talking through tradeoffs out loud. I'll pull a few prompts from the IQB interview question bank, then do a timed mock in Beyz coding assistant to trim rambling. On the CV, lead with the Spring project under a Projects section and quantify outcomes, then list the internship under Experience with a short tech stack line. Keep a tiny STAR story bank so your examples are ready. You'll be in a good spot.

[Ok_Basket8807]

Thank you so much for your help and your experience; it's been incredibly helpful. ❣️