Constructor Software Engineer Interview Questions
& Process

I had 6 interviews in total. The first was a recruiter call, which was pretty chill. Then there were 5 more interviews: System Design, Product, Backend, and Algorithms. The first screening was fine, the interviewer was nice. But from the second screening onwards, it felt like the interviewers were losing interest. They'd just give a task and then wait silently, sometimes even with cameras off. The System Design interview was the only good one; the interviewer was engaged and clear. The Product interview was awful. It was full of analytics and business questions about increasing metrics like ROI and ROAS, with verbal explanations of formulas that were hard to follow. The Backend interview was weird, with an algorithm task and then another system design task, which felt redundant after just doing one. The interviewer was also late. They asked a lot about cryptography, which was strange given the recent system design interview, and even stranger since the algorithm interview was scheduled right after. The Algorithm interview involved two people watching me do data engineering work for an hour, cameras and mics off, total silence. Honestly, I'm glad I didn't get the job; they seem to want someone who can do everything from business and analytics to data engineering, backend, frontend, account management, and security.

The interview process has 7 steps, with each step challenging me with a medium-complexity problem. It was exhausting but fun, meeting new people. The last 2 stages were unclear; interviewers didn't explain the context well, making it hard to understand the tasks. I was rejected via a generic email stating my experience wasn't a fit, despite reaching the final stage with the VP of technology. The feedback felt weak considering the time and resources spent. 7 interviews shouldn't be needed to determine this; a thorough CV review and a complete first interview would suffice. My email to HR for detailed feedback went unanswered.

The team was professional, friendly, and efficient. We started with a couple of intro calls, both involving some coding. Then came a virtual onsite with about 5 interviews, each lasting 30 minutes. While it was nice to meet different people from the company, 30 minutes felt too short to cover coding, their questions, and my questions. Maybe they wanted to see how I'd handle pressure? It felt a bit much since we'd already coded twice. None of the challenges were overly difficult, except for one question that was unclear, kept changing, and seemed too big to finish in 10 minutes. Overall, it's not a process that should deter candidates.