Stitch Fix Software Engineer Interview Questions
& Process

The interview started with a recruiter call. After that, there was an interview with someone who wasn't a recruiter. This person's questions were a bit vague, and I wish they'd been more direct about what they were looking for. A major red flag for me was being asked for my home address right after the recruiter interview. That feels really off, and it's not something they should be asking until they're ready to make an offer.

So, it was a pretty standard interview process. Started with a recruiter phone screen. Then, I had a behavioral interview with an engineering manager. After that, it went to the technical rounds. The first technical part involved a product design problem they had actually worked on. They wanted to see my solution and asked about validation and potential improvements. Then, there was a pair programming session where I had to add features to an app while sharing my screen and explaining my steps. After that, another behavioral interview with a different manager, focusing on conflict, teamwork, and tough conversations. Finally, I met with the recruiter again to discuss benefits, compensation details, and ask any remaining company questions. Overall, it was a smooth and professional experience, and you could tell the people there enjoyed their jobs.

Okay, so first off, be warned, they don't seem to value your time much. It was weird, they had me sign an NDA before we even started talking about interviews. Anyway, after that, I had a one-hour tech screen on Bluejeans. It was pretty standard, they asked me some basic design questions and then I did a coding exercise. Things seemed to go well, and they then gave me a take-home project. I really put in the effort here, spending 48 hours to build a really impressive app that met all their specs, complete with working code, unit tests, and UI tests. I was getting a bit impatient waiting ten days with no word, but eventually, twenty days after submitting, they got back to me wanting another remote interview. This one was supposed to be 2-3 hours long for pair programming and to go over my project. They also mentioned I needed to come up with 2-3 ideas for a new feature to add to my project, and we'd build it together. I spent a few hours brainstorming and came up with some solid ideas. The pair session itself was a real letdown. It wasn't just me and a senior engineer, but also another new hire observing for training, which was distracting. The senior engineer hadn't even looked at my project beforehand! He had me walk him through my code, and then we moved on to the new feature. Despite being told there were no wrong answers, he shot down all my ideas and insisted we do it his way. It was incredibly frustrating because he kept saying 'no wrong way' but every approach I suggested was 'wrong'. He seemed to be deliberately giving bad advice to see if I'd catch it, but even when I did, he'd just cast doubt. After wasting 45 minutes, we finally agreed on a direction, but then he kept changing the requirements, forcing me to rewrite code constantly. It felt like they expected perfection on the spot in a remote setting, which is odd for this type of interview. After all that, we ran out of time before I could finish, and I could tell it was a no-go. I got a rejection email a few days later, which wasn't a surprise. It felt like a waste of time after all the effort on the take-home and prep, especially since he hadn't even reviewed my project. Honestly, I'd avoid this place. The reviews online echo my experience - poor interview process.