Webflow is the leader in visual web development — designers and marketers build sites without writing code. The engineering org is heavy on browser internals, DOM manipulation, real-time collaboration, and the unique problems of building a “designer’s IDE in the browser.”
Process
Recruiter screen → 60-minute coding phone (often frontend-flavored, DOM/JS focus) → onsite virtual: 2 coding (one DSA, one frontend), 1 system design, 1 behavioral, 1 hiring manager. Frontend roles include a “build a small UI” round. Cycle: 2–3 weeks.
What they actually ask
- Design a real-time collaborative canvas (think Figma but for web design)
- Build an undo/redo stack for a visual editor with branching history
- Implement drag-and-drop with snapping, alignment guides, and z-ordering
- DOM manipulation, event delegation, virtual DOM diffing
- Behavioral: customer obsession, ownership, the Webflow design ethos
Levels and comp (2026)
- SE II: $170K–$210K total
- Senior SE: $240K–$310K
- Staff: $340K–$450K
- Principal: $500K–$650K
Prep priorities
- Brush up on browser internals: DOM, CSSOM, layout, paint, composite
- Practice frontend system design (real-time, offline support, conflict resolution)
- Be ready to discuss design tools, what makes them feel responsive, and why state management is hard
Frequently Asked Questions
Does Webflow hire backend engineers?
Yes, but the public face is frontend. Backend roles focus on hosting infrastructure, CMS APIs, and form processing.
What stack does Webflow use?
JavaScript/TypeScript everywhere — Node.js backend, React for the editor, MongoDB for storage.
Is Webflow fully remote?
Distributed-first with hubs in San Francisco, New York, and Mexico City. Most roles are remote-eligible.