Applied/interviewed for a software engineer position. The process included two consecutive 1-hour live coding interviews, both focused on algorithmic/coding exercises. The exercises became progressively more complex and included follow-up constraints.
I was able to solve the first parts and reason about complexity, but I did not complete the later parts within the allotted time. The feedback I received focused heavily on implementation speed, autonomy, and the amount of interviewer guidance required.
My main criticism was the interview format and experience. Given that my background is primarily backend/distributed systems, I found two consecutive coding rounds without a system-design or architecture discussion somewhat narrow as an assessment of engineering level.
I also found the interviewer interaction quite limited, particularly in the second interview. There was very little back-and-forth discussion, which made the experience feel more like a standardized assessment than a technical conversation. This made it harder to demonstrate how I normally reason about engineering problems in a collaborative environment.
Overall, the process may be appropriate for candidates whose strengths are primarily algorithmic coding, but I personally found it poorly matched to my profile and came away with a less positive impression of the engineering interview experience than I had before interviewing.
The process was mainly optimizing with HashMaps and changing constraints or inputs.
The following metrics were computed from 9 interview experiences for the Algolia Software Engineer role in France.
Algolia's interview process for their Software Engineer roles in France is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Algolia's Software Engineer interview process in France.