Pretty typical interview process; phone screening with their recruiter, followed by a behavioral interview with an engineering manager. Once those were successful, it moved on to a round of technical interviews. The first was a product design scenario where I was presented with a past problem they had already solved and assessed what kind of solution I came up with and asked followup questions about how to validate the solution and potential improvements to it. The second was a pair programming exercise where I had to add features to a boilerplate app. I had to share my screen and explain what I was doing as I was doing it. Next was another, more in-depth behavioral with a different manager. I was asked to talk about how I dealt with conflict, worked with a team, and dealt with difficult discussions. To close it all out, I met with the recruiter again to go over benefits, detailed comp breakdown, and was given an opportunity to ask questions about the company. All in all, it was smooth, professional, and I could tell everyone along the way enjoys working there.

I interviewed with Stitch Fix in 2017. Twice. The first time around I received a phone call that led to a video conferencing interview over BlueJeans. The interviewer was distracted the entire time, and continually asked me follow up questions that I had literally just answered. I didn't feel like I was being listened to at all. I thought to myself, no biggie. I met a few developers at RailsConf and thought they were really nice. Let's give the next round a shot. The next "product" round was possibly the most awkward interview experience of my life. The interviewer had no idea how to propose their "thought experiment" in a way that lead to any meaningful conversation. I'm talking something that was a seriously easy problem to solve, and yet it was impossible to have a dialogue with this person. In the end, I was offered a position over the phone in the San Francisco office which I declined. Next interview... I did not reapply. A recruiter at Stitch Fix reached out to me and asked if I was still interested in working remotely for Stitch Fix. I hesitantly said that I would entertain the idea, and we scheduled another interview using BlueJeans. I attend the next meeting, and the interviewer was not told that I had already interviewed with the company. He was nice and actually listened, but he was completely thrown when I told him I had already gone through the process as answer to "What do you know about Stitch Fix?" He never really got back on track after getting blindsighted by this, and eventually we just talked about testing strategies that we'ved tried to use for service oriented design. I end up moving onto the next stage: completing a homework assignment. I spun up a private repo, made three pull-requests to build the features discussed in the assignments, and merged them as I went through. Ten days later, I get an email saying the reviewer of my homework assignment thought it was hard to review my git diffs (despite making three feature branches, squashing commits, and using pull-requests), and that unfortunately I wasn't a good fit. So yeah. There you go. Normally I'd say take these reviews with a grain of salt, but I've read a few others that are spot on and I have a close personal friend who also interviewed with Stitch Fix after RailsConf and had a similar experience. Honestly, you're better off.

Initial phone screening with a recruiter. Then a remote interview with another senior level developer, which honestly did not seem very thorough, the interviewer didn't really seem to care about what I was saying. Then a second remote "product" interview with another engineer, that was supposed to be deliberately non technical. Then a coding exercise, which apparently I received really positive feedback about. Finally an on sight interview with 3 engineers, 2 heads of engineering. During live interview they sat behind me and asked me to do live coding exercises on the spot. I tend to work better on my own without someone staring over my shoulder while I work. Not sure I really enjoyed this interview style. Seemed like the interviewer was deliberately leading me down the wrong path at times. Was a little disappointed didn't get an offer, I spent a good amount of time on their coding exercise and took a day off of work to go there, but from their interview style I'm not sure they ever intended to hire me. A couple things I didn't like: 1. They didn't explain that their compensation model was fixed to the market and not performance based until I got there which was shocking to find out. 2. Also surprised me by saying they hire based on contract position for 8 weeks before hiring full time. My gut tells me this one is a tease, I wouldn't waste your time on it.