Recruiter reached out and we went from there. Anyone who has been a PM for some time knows there are many variations and specifications, e.g. Growth, etc. If you aren't well-versed on the nuances of A/B testing, I suggest you pass on Indeed; the interview is extremely skewed toward that. You need to be able to discuss the specifics of your test structure and explain your rationale behind them. I found this exhausting (testing is cool, but there is a thing as testing too much and/or testing the wrong things). Mind you, I am a big fan of A/B testing and have years of experience running them. The situation presented in the case was such a minute feature with negligible impact on users that we were going into the weeds unnecessarily. I assume the interview reflects how they actually work (structure of approach, type of features), so it is not somewhere I'd want to work. Declined. Poor communication throughout, as well.