How do you manage a team?

"This was a problem-solving round of about 35 minutes with a product owner. At the start he explained the format: the case is specific to Revolut, no prior Revolut knowledge is needed, and the most important thing is to ask clarifying questions. The case: to grow Revolut for Business revenue over 12 months while at least keeping the current gross profit margin. He gave data when I asked (revenue by country, by segment and by revenue source) and said openly when he didn’t have something, asking me to make assumptions. At the end I had to give a short update. What went well: the atmosphere was relaxed and my questions got useful answers. What didn’t go well: I listed many levers without sizing gap or checking each idea against the margin constraint"

"Process was good. However it was slow, I needed more practice and time during the technical interview."

"The initial round with recruiter was good. Along with experience he asked some data platform related questions."

"What went well: The live coding and system architecture rounds went smoothly. I was able to articulate my design choices clearly, especially around API design, database strategy, and maintaining high availability for microservices. What didn’t go well: The initial behavioral portion felt slightly rushed because we spent extra time discussing specific cross-functional project dynamics from my previous roles. How does this interview compare to other interviews you've done? It was significantly more interactive. Rather than giving static answers, the interviewers actively challenged my assumptions and asked "what if" scenarios, making the evaluation feel comprehensive and realistic to day-to-day work."

"Overall went well. There were some technical questions which were asked but the interviewer assisted me to answer them."

"I had a long process with a recruiter screen, then a PM aptitude screen, then a full onsite loop for a PM leadership role managing PMs at roughly an L7-equivalent level. I put more than 100 hours into prep because this is absolutely not a night-before kind of interview, and I actually felt pretty strong across the first several rounds. The loop covered people management, cross-functional influence, execution and metrics, operating, project retro, and product sense, and the interviewer variance was real because some people would lightly guide while others gave me nothing. I got rejected, and I'm pretty sure the miss was the metrics depth in my last execution-style round, plus not going deep enough on secondary metrics in product sense."