The process started with a typical one-hour technical screening call, followed by a separate one-hour non-technical leadership call to verify I can actually work with people. And finally a 30-minute call with the lead recruiter to discuss the actual in-person interview process. The in-person interview gauntlet was a 6 hour process. It began with a technical one-on-one interview discussion. Followed by lunch with a higher-up (they tell you this is so you can get to know the company, and it's not really part of the interview, but come on -- of course it is). For me, this was a culture-fit interview. Next is another series of one-on-one interviews that gauge your experience. One of these is with the hiring manager -- probably the most important one. This is the most difficult part of the interview process. Everything is 'Tell me about a time when...', and you need to have specific examples that answer each question. Here they look for answers in the STAR method. The second to last interview was a two-on-one interaction. One guy with a laptop that took notes and another that poses a programming problem and discusses it with you. This was my favorite part, and the part I was most nervous about. This is where you have an opportunity to write code out on a whiteboard and explain your process as you go. The last interview was a follow-up with the original phone screener again. Since he was located in Seattle and I was interviewing in Irvine, CA, this was done via video conference. More technical questions were asked, mostly related to JavaScript, but some application design questions as well. One thing that really stood out to me was that the interview was really geared toward full-stack. I don't know if that's because it was tailored for me since I am a full-stack developer, or if they just really want to see that their front-end developers have well-rounded experience. At the end they made good on their promise to have a response to me by the end of the week. They decided not to make an offer, which I can only assume is because they could tell I wasn't really interested in being exclusive with the font-end. Overall it was a good experience, and good practice.