How should you handle misaligned interviews?
Quick Overview
This question evaluates communication and professionalism in handling misaligned interview expectations, along with the ability to surface relevant technical competencies such as concurrency, programming language familiarity, and problem scoping during a backend engineering interview.
A backend engineer prepared for a coding interview after the recruiter explicitly said the round would assess concurrency. The candidate chose Java as the interview language. During the interview, however, the interviewer gave a web-crawler problem, insisted on a single-threaded implementation first, and did not allow time to implement the concurrent version even after the single-threaded solution passed the basic tests. The interviewer also said they were not comfortable reading Java. The candidate was later rejected.
How should a candidate handle this situation professionally?
Please address all of the following:
- How to politely push back when the interviewer’s guidance appears to conflict with the stated evaluation focus.
- How to make concurrency skills visible without openly ignoring the interviewer’s instructions.
- What to do if the interviewer is unfamiliar with the chosen programming language.
- Whether it is worth sending post-interview feedback or an appeal, and how to frame it.
- For well-known coding problems such as a web crawler, whether the candidate should first clarify requirements and edge cases (for example URL normalization, fragments, schemes, and stopping conditions) or start coding immediately to avoid appearing slow or overly rehearsed.