Went through the full Webflow engineering loop in early 2026, targeting a senior SWE role. Wanted to write this up because the prep advice I found online was pretty thin.
The system design round was a 60-minute live session with two interviewers: one senior engineer, one staff. They gave a prompt in the first five minutes and then it was basically open floor. The problem space was somewhere in the intersection of content delivery and collaborative editing, which tracks given Webflow is a visual CMS. They wanted to see how you'd design a system that lets multiple users edit a site structure concurrently without blowing up each other's changes.
A few things that came up that I wasn't expecting: They pushed hard on conflict resolution. Not at a high level, like actually: what's your merge strategy when two users modify the same element at the same time. CRDT vs OT came up. Know at least the intuition behind both. They asked about rendering pipeline considerations. If the site has a CDN layer, when does a draft change become visible? How do you handle cache invalidation without tanking editor UX. They cared a lot about data model clarity. Not the flashy stuff. Like: how do you represent a component tree in a database such that partial updates are cheap.
I had 3 YOE at FAANG before Webflow and came in with plenty of system design reps, but the product-domain specificity caught me a little off guard. Worth spending an hour actually using the Webflow editor before your system design round, seriously.
Leveling felt like their equivalent of a strong senior. Lots of ambiguity in the prompt, and they didn't give hints unless you were genuinely stuck.
Reply if you have specific questions about scope or format.