I applied online. The process took 3 weeks. I interviewed at Chess.com in Feb 2023
Interview
I had three rounds of interviews - first with a PM, then HR round, and then with the CTO . The whole process took ~3 weeks. Their PM was confused about me not talking to HR first. Nevertheless, he was friendly and made me feel comfortable during the whole process, and I believe I answered all his questions. The HR round was fine, too. Now, the CTO interview was very different, not friendly, and somewhat forced, with questions and examples that fall out of the scope of normal PM work (I would love to describe more, but glassdoor doesn't allow to go into such details). I received the rejection the next day and was ghosted upon requesting feedback.
Other Product Manager interview reviews for Chess.com
I applied online. The process took 1 week. I interviewed at Chess.com (Belgrade, Central Serbia) in Feb 2025
Interview
It felt quite informal and friendly, It was just an introduction meeting with a recruiter. He told me about the company and the position. He then asked me some questions about my past experience, my salary expectations, what I knew about the company, and he frequently asked if I had any questions. I asked multiple. It felt like the interview went very well.
I applied online. The process took 4 weeks. I interviewed at Chess.com in Mar 2023
Interview
Recruiter call: The recruiter was supportive and provided assistance with any questions or concerns I had about the interview process.
CTO call: During the call with the CTO, I was asked about my high-level experience and how it aligns with the company's goals and vision.
Product lead: The product lead focused on assessing my skills and knowledge in product management, asking detailed questions about specific product features, user experience, and discovery.
Engineering team: The engineering team asked about my experience with agile methodologies and how I collaborate with engineering teams to deliver successful projects. They also inquired about my problem-solving approach and how I handle technical challenges.
