The interview process was well organized and consisted of four rounds covering coding, system design, backend concepts, and a hiring manager discussion. The interviewers were professional and friendly, and the conversations were engaging and technically challenging. Overall, it was a positive interview experience and a great opportunity to discuss distributed systems and backend engineering.

6 steps in total. 1st is the recruiter's talk. After that, 1 coding question with an engineer. Later on, back-to-back 4 interviews: 2 code interviews and 2 behavioral. Coding questions are about algorithms and data structures. The behavioral ones are "tell me about a time..." kind of questions. Mainly focusing on OCI values.

No information was provided before the technical screen about the interview structure or what would be assessed. I was told it would be a coding round, but the question required writing code within a large existing Java project rather than solving a standalone programming problem. I was not informed beforehand that familiarity with a specific project structure, framework, and libraries would be required, nor was I given the option to use my preferred programming language. A significant portion of the interview was spent understanding an unfamiliar codebase, navigating project files, figuring out dependencies, and interpreting framework-specific code instead of demonstrating problem-solving or coding ability. Success depended heavily on prior exposure to that particular ecosystem rather than on universal software engineering skills. Technical interviews should assess transferable skills such as logical reasoning, coding ability, debugging methodology, and algorithmic thinking. If expertise in a specific language, framework, or project setup is expected, candidates should be informed in advance so they can prepare accordingly.