Robin Powered Software Engineer Interview Questions
& Process

The initial HR contact was great, they sent over company values and explained the process. Then we had a brief chat about details. The actual process involved an HR call, a chat with the hiring manager, and then a 2h+ meeting with the team. The next round was with the engineering manager and a solutions architect. It was a technical discussion about my background, AWS, DevOps, and problem-solving from a SA perspective. I didn't really like that session because the interviewers seemed disengaged. We didn't get to discuss solutions for questions that didn't have a single correct answer, it felt one-sided. I was rejected without feedback, and the role was closed. I had to reach out to the EM for feedback, which I eventually got in detail.

First I had a call with the recruiter, then a video call with the Director of Engineering. We chatted to get to know each other and they asked some general technical questions. It was a pretty fair process, but some questions were more specific to how JavaScript works.

The interview process was pretty long but I enjoyed it. All the interviewers were super nice and generous with their time. First, a 30-minute screening call with Robin’s Senior Documentation Specialist, who was really kind and passionate. We talked about my skills and Robin’s culture. Then, a 30-45 minute technical chat with the VP of Engineering, who answered all my initial questions about Robin. Next, a 3-hour take-home Technical Assessment focused on scheduling, similar to Google Calendars in functionality. Finally, a two-day interview day. Day 1 was 2.5 hours: I discussed collaboration, prioritizing work, and ownership with the Director of Engineering and a Sr. Product Manager. I then walked through my take-home assessment with a staff Engineer and an Engineering Manager. After that, I talked about complexity and innovation with a Principal Engineer and a Senior Product Designer. Day 2 was 2.25 hours: I spoke with an Engineering Manager and a Front End Engineer about how to approach and clarify ambiguity and communicate effectively to influence decisions. The last conversation was with the Director of Engineering, where we discussed our design philosophies, Robin’s history, vision, and company values. Throughout each interview, I asked everyone why they were passionate about Robin, and they all said the same things: 1. Amazing people 2. Finding interesting solutions to complex problems.