The process was very fast: a code-review exercise was completed, followed by three one-hour interviews back-to-back. An offer was extended the same day.

The interviews themselves were surprisingly old-fashioned. All technical questions were knowledge-based (e.g., "Describe X feature of Java," "Describe Y feature of React...") with no problem-solving or design/architecture elements.

Behavioral questions were slightly better, allowing me to guide the conversation. However, I didn't observe them asking meaningful follow-up questions or quantifying the impact of my actions.

Everyone was very pleasant, but the quality of the interview process was one of my primary reasons for declining this offer.

Various superficial, technology-specific questions, such as those found when searching for "Java interview questions" or similar.

Topics covered include:

• The difference between == and equals()
• Interfaces vs. Abstract Classes
• Why you would implement a getter rather than have a public field.