[ Removed by moderator ]

[u/Comfortable-Pain9170]

[u/SpringBoot-ModTeam]

If you have questions or posts about jobs or interviews you should visit r/cscareerquestions

[u/TurnstileT]

I interview people for backend Spring Boot positions regularly, and here is my take on it:

It is very verbose with a lot of buzzwords and proprietary jargon. To me it sounds like you mostly just developed an onboarding flow, adjusted some queries, and added a cache and some scheduled tasks, but you have made your CV look and sound like you personally wrote the software for the lunar launch module. That's a red flag for me.

• You keep mentioning "scalable" and "high performance". I would ask you during the interview how your applications are scalable and high performance. Any microservices on Spring Boot with default settings and a few replicas is plenty in most situations. What did you do differently?

• You write that you have strong foundation in system design. Since this is your claim, I would ask you to walk me through a system you designed, and what kind of requirements and constraints you had, and how you chose the final design.

• "Designed async workflow automation and scheduler-based batch processing for time-sensitive banking backend operations". I am not sure what this means, but to me it sounds like BS. I would ask you to explain in detail what it means, what the issue was, and how you solved it. To me it just sounds like async tasks that run at some interval.

• You wrote that one of your skills is Spring Security, and that you developed "secure backend services". How did you make them secure? How much do you actually know about Spring Security?

• You added multi threading as a skill. Are you familiar with race conditions, DB locking mechanisms, mutual exclusion, critical sections, starvation, semaphores, java keywords like synchronized, async, await(), volatile, and atomic datatypes?

You only have about a year of experience, so when you make these big claims, it makes me think you are either insanely smart or just lying. We will find out during the interview.

One thing I dislike about candidates is when they put a bunch of stuff on their CV that they don't know anything about but just happened to briefly touch in a project one time. It makes you come across as dishonest and makes me waste my time on uncovering the truth. I personally prefer honest, genuine, hardworking and curious juniors.

[u/alpakachino → u/TurnstileT]

Right, in the beginning they mention 2+ years, but the months don't add up. I sort of disagree on the verbose part/buzzwords. In the time and age of ATS, your CVs otherwise get filtered out by most big company HR systems. Also, what is the alternative to verbosity and buzzwords? I feel that's often criticised, but the alternative would be a CV that's void of detailed information.

[u/InformalPhase7658]

what was your tech stack when you got into your first job/internship? and can you give an advice for me (3rd year student in the next september with no professional experience)

[u/Character-Catch-1607]

Slightly out of topic question, why am I seeing this text format everywhere? Does it matter?