Eltropy Software Engineer Interview Questions
& Process

The interviews involved 4 rounds. The interviewers were very self-proclaimed and would do anything to beat you down. If an interview is around system design, then you need to follow with the candidate around certain decisions not ask tool specific questions. it should not matter if someone has used aws lambda or not. if someone knows the working and fundamentals, lambda or any other tool is just a 2 hour job then. but they were all fixated upon tools. Very poor experience. classic case of frogs in a well.

It was a telephone screening first, then two rounds of face-to-face discussions. After that, there was a discussion with the VP. The whole process took about 10 days to complete.

The interview had 5 rounds. First was DS & Algo, where they asked about finding the median in a stream of numbers. The interviewer was nice and wanted to see my approach. Second was a design round. They asked about my resume projects, challenges faced, and scenarios like deadlock and failure handling. They also asked to design a low-level Amazon cart system. Third, I had a discussion with the VP of Engineering, which was a cultural fitment round. We talked about my past experience and salary expectations. Fourth was a discussion with the Co-founder, focused on HR negotiation. We talked about Eltropy, my salary expectations, and they felt it was beyond their budget. They accused me of chasing money and not believing in the company vision. They also wanted another machine coding round. Fifth was an offline machine coding round to build a banking system. I coded over the weekend, pushed to GitHub with details, but heard nothing back for a week. After following up, I was promised a response in 2 days, but again, no response for another week. I messaged again to follow up, and then they ghosted me. Overall, 3 out of 5 rounds were great, but the last two ruined it. They could have been professional about budget limitations, but instead used cheap tactics, wasting my time.