Did the Webflow PM loop for a senior PM role earlier this year. I've been through a lot of PM interviews at this point (Figma, Notion, a few others in the design-tool / visual-web space) and Webflow's process was one of the more thoughtful ones.
Here's the breakdown of what I encountered:
Recruiter screen (30 min) Basically: why Webflow, what are you looking for, comp range. They also asked what I thought about a specific product decision Webflow had made recently. Use the actual product before this call.
Hiring manager (45 min) Mix of background and situational questions. They wanted to hear how I make prioritization decisions when there's genuine disagreement between stakeholders. Asked me to walk through a product I'd launched that underperformed. They were specifically interested in how I handled the aftermath.
Product design / thinking round (60 min) A product sense question. Mine was roughly: how would you think about improving the Webflow Editor experience for users who are designers but not developers. Classic product design format: understand the user, frame the problem, generate solutions, prioritize. The difference at Webflow: they pushed hard on the technical feasibility angle. They want PMs who understand constraints, not just UX ideation.
Cross-functional / metrics round (45 min) They gave me a hypothetical launch and asked how I'd define success and what metrics I'd track. Also asked about a time I had to change strategy mid-execution based on data.
Bar-raise style behavioral (45 min) Deep dive into how I'd handle a roadmap conflict with an engineering lead. Not abstract, they had a specific scenario.
Overall the bar is high and skews toward PMs who can go deep technically without being engineers. If you've worked closely with frontend or CMS products, lean into that. If not, spend real time in the editor before your loop.