Beamery Software Engineer Interview Questions
& Process

We start with a phone screen to discuss the role. Then there's a behavioral part where you need to explain why you fit. After that, we dive into Data Structure and Algorithms, usually Leetcode style. There's also a System Design round where you'll design a small component. Finally, an HR interview wraps things up.

The hiring process took over 3 weeks and involved 6 to 7 interview stages. There were always delays between stages, even though they mentioned aiming for a quick, one-week finalization. I was expecting an offer, but after a significant delay, I was informed I didn't get the job. This was surprising because the interviews weren't difficult and were quite straightforward, and I had good conversations with all the interviewers. It was actually the best interview experience I've had, even better than when I got accepted by Google, which was much harder. I only got feedback from one out of the six interviewers, and it was shallow, stereotypical, and irrelevant to my background – it felt like an automated response. What's most surprising is that they offer a poor user experience despite promising the best with their product. Beamery's main features are supposed to improve recruitment efficiency and treat candidates like customers, but despite the outcome, this was the worst job application experience I've had, and the company claims to fix recruitment. I suggest they fix their own process before trying to fix others'.

After applying via StackOverflow, the whole process took around 2 weeks. It started with an HR Interview where they explained the product and my role. Next was an online coding challenge that took about 3 hours. Then, I had a General Interview with the Head of Engineering where they asked about software development. This was followed by a Technical interview with 2 engineers and finally an Interview with the CTO. After that, I received an offer.