The interview process was quite disappointing.

The initial phone screen was conducted by a junior engineer, and the questions were exclusively Java trivia.

After passing that round, I proceeded to the onsite interviews.

For the onsite, I met with an entire team of engineers. There was no whiteboard coding, no problem-solving exercises, and no system design discussions. Most of the questions were extremely vague, such as 'How would you debug this issue?', and they were often inaccurately presented. Overall, the questions seemed unintelligent.

During one interview, an engineer with a thick Indian accent assertively stated, 'I see your resume; it looks good,' before asking a trivia question about an obscure Spring Boot annotation. This is the kind of information one can find with a quick 30-second Google search and reveals very little about a candidate.

It's a rather silly process. Asking framework-specific trivia questions will not help in identifying strong engineers.

I did not receive an offer. The reason cited for rejection was the inability to 'hit the ground running,' despite my current role utilizing a nearly identical tech stack. In any case, I would not have accepted the position, as it was evident that the team had many less capable engineers.

Name a Spring Boot annotation for doing XYZ.