Backend Engineer 2 @ Atlys

Atlys Interview Experience - Backend Engineer 2

The recruiter described the round as an AI Coding Round (1 hour), where candidates would use an AI agent of their choice to build a product from a vague problem statement, explain the AI's decisions, and demonstrate that they weren't overly dependent on AI.

However, the actual interview was completely different. I was asked to solve a Splitwise-like app with smart settlement without using AI.

I approached it as an LLD problem, starting with functional and non-functional requirements, API design, core entities, and HLD. More than halfway through the interview, the interviewer shifted the focus to implementing two methods:

• settle() - Calculate the number of transactions required to settle everyone's expenses.
• settle_optimally() - Minimize the number of transactions required to settle all expenses.

I was moving in the right direction, but a significant portion of the interview time had already been spent on system design rather than implementation. With the remaining time, it became difficult to demonstrate my coding ability properly.

Verdict: Rejected.

My feedback:

1. Please train interviewers properly and ensure they understand the objectives and evaluation criteria for the round they're conducting.
2. Match interviewers to the level they're expected to assess. Interviewers need sufficient technical depth and experience to evaluate candidates fairly, rather than judging them solely on whether they arrive at a particular solution.
3. If the round is advertised as an AI Coding Round, please conduct an AI Coding Round. Candidates prepare and approach interviews based on the format communicated by the recruiter.

I'm completely fine with being rejected when my technical skills don't meet the bar. But the interview format should match what was communicated, and candidates should be evaluated on the skills the round is intended to assess.

Sharing this so future candidates have a clearer understanding of what to expect.