Typical Bay Area, 2 recruiter calls, tech screen, then an “on site” (remote) interview. What is interesting is that they split their on site over two days, making it less draining, but requiring more time away from your current job. The recruiting sourcer told me that the team had been looking to fill this role for a while, and either all the candidates that he found were not good, or the hiring team was very picky. This should have raised a red flag for me, but I tried anyways. During my tech screen interview, the interviewer seemed to tuned out 1/2 into the interview. I could not figure out why they became disengaged. I spoke my decisions every step of the way, asked for feedback and suggestions and didn’t receive much substantive/actionable feedback. So, I focused on writing clear code, well named variables and methods, and had almost complete test coverage. However, the company decided to pass on me and didn’t provide feedback. This kind of thing happens a lot in Tech, but a friend of mine interviewed for the same position and had a nearly identical experience as me. We both worked for a Bay Area competitor to Color for many years, so it feels strange that we both failed at the tech screen stage, perhaps the first recruiter was right and the interviewing team is a bit too quick to disqualify.