The process includes an introductory phone screen, an over-the-phone A/B testing exercise, a 30 minute timed math test/business case, sharing product requirement documentation, and an in-person interview. I did not interview in-person at this company but completed their remote assessments. There were a couple of red flags indicating that they need to rethink how they evaluate for this role. CONS >While I know technical portions can be common, I am not sure if the timed case provided is close to a real-life scenario. I think it would be better to evaluate this in person as opposed to focusing on candidates that can do fast mental math under pressure. >I was asked to provide company product documents which was inappropriate and unnecessary. It wasn't explained specifically what they wanted (just anything you have) and why they wanted to evaluate these. I was eliminated from the process because I expressed concern over sharing company information with an outside party. While this was a requirement, if everyone is providing something different then by definition they are not being evaluated equally. The feedback I received from other recruiters is that this is inappropriate and easy to evaluate during an interview or via a project like most companies. >Recruiter never called me and would take several days to respond to emails. Didn't take the time to explain the process or explain why the information asked for was needed. Was very quick to dismiss my candidacy, had other candidates and didn't want to put any extra work in. PROS >Company sounded very interesting and are solving real life problems. Product itself has a lot of room for growth. >Product team seems to be empowered to make their own strategy and experimentation. They are trying to maintain a testing and learning culture. Although there seems to be a lack of alignment between teams.