I had an initial HR screening, followed by one or two technical interviews. You must know TDD, DDD, CQRS, and concurrency. The process is fast-paced, highly structured, and focused on practical problem-solving. They expect clear communication, strong engineering fundamentals, and the ability to reason about real-world systems under pressure.
I got contacted by a recruiter. As a first step, I had a call with another recruiter. He was also asking technical questions, but it felt strange. (A bit like talking to a wall.)
I was rejected with a generic message stating that I was not "aligned with the position". This is weird as it was inbound and based on my profile. No feedback, of course.
Waste of time.
Very kind. The questions weren’t easy, but with knowledge of database configurations, concurrency, locks, and some practical experience, you are able to answer them clearly, confidently, and effectively overall. It was good time.
Recruiter round, they’re basically looking for buzz words. They asked for my experiences in handling different scenarios, then other db and concurrent related questions . Overall it was straightforward, just go through other’s experiences here and you should be covered
Preguntas de entrevista [1]
Pregunta 1
Concurrency
Optimistic vs pessimistic locking
Db isolation levels