Cricut Software Engineer Interview Questions
& Process

The interview process was pretty standard. I first chatted with a technical recruiter to make sure I met the basic requirements. Then, I got a small coding assignment to show my coding style. After that, there were two in-person interviews: one with the technical team to check my basic skills, and another with HR to see if I'd be a good fit for the company. Lastly, I went through a background check.

Had a good first chat with the recruiter, she knew her stuff. Then I went into the office to meet the team. The interview was good, they asked some get-to-know-you questions and gave me whiteboard problems. After about an hour with the team, they showed me around. They said I should hear about an offer that same evening or the next day. But I never heard back. I emailed and called but still nothing. It's been over a month. I really liked the company until that point. Super unprofessional!

The recruiter did the initial call, which was kind of technical but easy. Then I got a link to a timed online assessment on devskiller.com. It had 4 parts and 85 minutes. It felt like only the last question counted. I didn't pass because I ran out of time on the last part. The first part was multiple choice and fill-in-the-blank coding questions. Parts two and three involved writing SQL queries based on given tables and problems. Part four was a code review of sample code, which was really long for the time given. The recruiter had advised me to save time for part 4 and to comment on every line, which was odd, but maybe that was the key. I spent a good amount of time trying to understand the code deeply enough to comment meaningfully. Perhaps a different approach of just short comments on each line would have been better than trying to assess the code comprehensively.