I applied through a recruiter. The process took four weeks.The first contact was a cold email from a recruiter, followed by some back-and-forth emails to set up an intro call, then scheduling a technical interview, and finally a rejection email. More than a week elapsed between each step. The initial call pitched the company and then went on to explain the products they were looking to expand and roles to fill, but it was never clarified which team or role I would be interviewing for, or even for what level of software engineer. The process very much felt like being slowly moved along an assembly line. The developers who interviewed me for my technical round were very friendly and personable, but the technical interview itself left much to be desired.

There were a few brief introductions and then you're presented with a simple problem, write the code, and then presented with further constraints and requirements to the first problem to update your solution with. Prior to the technical interview, you're sent a quick prep email with the tip, "Your code should clearly demonstrate your understanding of as many advanced constructs as possible for the language you are using." The issue here is that the problem given is simple enough that it doesn't leave much room for demonstrating advanced constructs without needlessly fluffing things up.

I made an effort to do so, explaining how principles like SOLID, YAGNI, cohesion, and coupling would come into play, but I don't know if that was necessary, and doing so burned up a bunch of time. I sent a follow-up email to thank them and check in after a few days, but it wasn't until over a week later that I received a reply saying they're moving forward with other candidates. The feedback I received for the technical interview was terse, vague, and non-constructive.

Robot vacuum that others have mentioned.