Wrike Product Manager Interview Questions
& Process

So, a recruiter reached out to me on Linkedin and was like 'hey', but then ghosted me for 2 weeks after I said I might be interested. Then she finally scheduled a screening, and then an interview. Weirdly, all the interviewers were Russians, like 3 of them at once, and HR was there too. It was all on video chat, they were calling from St. Petersburg. Most questions were actually about my current job, which was a problem because of conflict of interest. Then, after they said I did well on the second interview, they sent me this PM exercise. The exercise was to improve Wrike for different teams and come up with product ideas, presenting them as a product brief. I told them that the task was too similar to my current job and their product, which felt like free consulting, and that I wasn't comfortable doing that. I also mentioned that they reached out to me, and I didn't apply. I said I'd rather do a generic product ideation exercise. The HR basically said they didn't understand and that the question was generic, which to me is a show-stopper, so I didn't follow up.

I was contacted twice by Wrike recruiters on LinkedIn. I initially declined because of relocation, but they later opened a remote position. The first step was a recruiter call with basic product expertise questions. The second phase was a 1.5-hour interview with two product managers. It had three parts: introductions, a discussion about product expertise, and a hypothetical scenario. The whole thing felt rushed, with not enough time to go deep. Recruiters seemed to jump to conclusions, interpreting things subjectively. The process wasn't structured, with random questions thrown out to probe specific areas. The hypothetical part involved picking a product and discussing it, including why I chose it, why it's right, how I'd improve it, and how I'd measure the impact. It's an open-ended question, but answers are judged by cognitive bias, so it's hit or miss. Cons include interviewers being passive-aggressive, trying to 'crack' me instead of collaborating, finding things funny and talking privately during my answers, asking repetitive 'Why' questions, and the overall experience feeling sub-par for a lead role, with interviewers seeming tired or bored.

This interview was for a first Product role and was a phone call directly with the CEO. It was quite technical, focusing on my past work on features and the metrics I used for performance tracking. There weren't many questions about the Wrike product itself or my behavioral fit. The CEO did request wireframes and specs to assess completeness.