(Reached out by Recruiter)
Started with a recruiter phone screen covering fairly standard backend topics:
AI note-taking was being used during the call, and those notes were apparently shared with the hiring manager afterward.
If you clear this round, you move into the actual engineering interview loop.
They share a fairly long problem statement (around 1–2 pages of requirements/details). The expectation is that you solve it using an AI-assisted IDE/workflow.
A few things worth noting:
You use your own IDE/subscription/tools. (They don't give any subscription)
Heavy focus on:
The round felt less about typing speed and more about engineering judgment + ability to work with AI tooling effectively. Also, use single-prompt to make the project at once, to finish the assignment in the given time (1 hour)
Followed a fairly structured format.
DSA
Design Patterns / System Design
API Design
Event-Driven Architecture
CI/CD + DevOps
After Round 1 + Round 2, they decide whether to move you forward.
Mostly behavioral with a mix of engineering scenarios.
The interviewer 'literally' read a predefined set of questions.
Examples:
This round felt fairly conventional. Prepare from internet, do not follow instincts, seemed like expectation was of typical answers.
Short (~15 min) discussion.
Mostly focused on:
Overall, the process felt smooth and fairly organized. The company seems quite aligned with modern engineering interview trends, especially around AI-assisted development workflows. Round 1-4 happen on the same day.
One thing recommended: for bar-raiser discussions and behavioral rounds, prepare somewhat “structured” or internet-style answers rather than being overly honest/raw. Interviewers seemed to prefer polished textbook-style responses.
Hope this helps someone preparing.