The process started with a CV screening, which I passed, followed by a technical screening call with a recruiter.

The technical part covered Android/Kotlin topics such as:

• concurrency
• architecture
• testing
• basic system design

My impression was that the interview relied heavily on a predefined checklist of expected signals. In several cases, giving the correct high-level concept did not appear to be sufficient unless I also explicitly mentioned the specific implementation details expected by the rubric.

I was rejected after this stage without speaking to an engineer. I later received internal feedback stating that I “needed a bit of a push to answer the questions correctly” and that the performance was considered average or mid, but “a bit weak and not very convincing.”

I generally like structured interviews, but I think there is a limitation when a technical screening becomes too dependent on matching predefined keywords rather than exploring the reasoning behind an answer.