Managed by Q Software Engineer Interview Questions
& Process

This was honestly the worst interview process I've ever experienced. So unprofessional. It started with a technical phone screen where they were 10 minutes late and gave me a simple linked list problem. I did it fine, but the interviewer seemed totally uninterested. Even though it went okay, I wasn't planning to continue, but then they offered an on-site with flights paid after 3 days, which made me give them another shot. After I agreed, it took them 6 more days to tell me it would be a video interview instead of an on-site. By this point, I was pretty offended, but I agreed to do the video interview anyway, thinking I'd get to practice some hard problems. The whole process took almost two weeks, longer than a Big-N interview I had. The first part of the video interview had two bootcamp engineers ask a Leetcode 'Hard' problem (problem #10). It's a DP problem, and while I could explain it on a whiteboard, they made me code it first, then let me use pseudocode when they saw the coding complexity. It felt like they lacked experience with how interviews should be run. After that was a typical behavioral interview, again with bootcamp engineers, asking about teamwork and getting along with others. Their response times were actually fast though, I got an offer from a Big-N company the same day they rejected me. Honestly, if you go to a good school, you can probably find better opportunities than this, considering their process and salary.

First, there's a self-introduction where they ask about your projects. Then, they'll pose two algorithm questions. After that, a significant part of the interview will focus on system design. I didn't make it through because I was lost when it came to the distributed system part of the system design question.

It started with a quick phone chat about my background. Then, I had a call with an engineer where we chatted more and they gave me a coding challenge. Later, I went in for a full day of interviews at the office. They kicked things off with a product demo that really showed the company's mission and future plans. After that, it was a bunch of coding challenges, two engineers per session. They were super helpful and gave good feedback on how I was approaching the problems. I got a few minutes after each interview to ask questions about the company, the culture, and work-life balance. By the end of the day, I'd met about half the engineering team. Overall, it was a great experience to learn about the company and for them to get to know me.