Staff Brand Designer

Responsibilities

• Design the web as our primary brand surface: Treat webflow.com as the place most people meet the brand, and design it as an experience rather than a stack of sections. Shape pacing, narrative, and flow across a visitor's path, not just the layout of individual pages. Express the brand through behavior—type, motion, interaction, and state—not only through how a frame looks at rest. Extend the brand system into web-native patterns and components that other designers and marketers can use without you in the room.

• Work in the space between brand and web: Design and build in the same motion, carrying work from brand idea to shipped page without handing it off at the seam. Act as the primary technical owner of Webflow's marketing surface area, from CMS architecture to component systems to publishing workflow. Build on Webflow as our most sophisticated customer, so the site stands as proof of what the platform can do rather than an exception to it. Hold the craft bar on brand expression and the technical bar on implementation at the same time, and know when the two are in tension. Make architectural calls that balance ambition against performance, scalability, and the cost of maintaining them a year from now. Ship launches, campaign pages, and fixes with speed and accuracy under real deadline pressure, including moments like Webflow Conf, and own performance, accessibility, and SEO health as ongoing commitments.

• Work across the brand's other surfaces: Bring the same standard to work that isn't a website: campaign systems, conference environments, editorial, film, and the brand's expression inside the product. Design for coherence across surfaces, so an idea that starts on the site still holds up in a keynote, a video, or a physical space. Understand how a brand system has to behave differently in each medium, and help evolve the system itself rather than only its web expression.

• Experiment, and put what works into production: Work in the open with AI-assisted design and development, generative code, and agentic build tooling, and bring back what actually holds up under a quality bar. Explore advanced and pre-release platform capabilities and ship them ahead of the market. Build the experiments that make an argument—a working prototype that settles a debate faster than a deck would. Use generative and agentic tooling where it closes the gap between designing a system and building it, which is increasingly the same act. Develop the team's practice as you go, so a tool you proved out this month is something everyone is using next month. Feed real practitioner insight back to Product and Engineering, because you're building on the thing we sell.

• Unblock the business: Partner with Brand Studio, Product Marketing, Growth, Legal, and Events to get campaigns and launches live without compromising the site. Reduce dependency bottlenecks by making your expertise available early, when decisions are still cheap to change. Mentor designers and marketers through pairing, feedback, and the systems and guardrails you build for them. Translate technical constraints into plain language so non-technical partners can make good tradeoffs themselves.

Requirements

• BS/BA college degree or relevant experience
• 8+ years of experience spanning brand design and web design or development, with work that clearly shows both
• Demonstrated experience designing marketing websites as a primary surface of a brand—narrative, flow, and interaction across a journey, not just individual page layouts
• Deep, demonstrable Webflow expertise, including complex CMS structures, components, interactions, performance work, and system-level thinking
• Experience contributing to brand work beyond websites—campaigns, environments, editorial, motion, or product surfaces—with a view on how a brand system has to change shape in each
• Active AI fluency: you are already using AI and agentic tooling in real production work, and can show what you have built with it, what you have thrown away, and how you tell those apart
• Familiarity with code: you read HTML and CSS comfortably, can follow and adapt JavaScript, and are not stuck when a build needs to go past the visual editor. Professional development experience is not required.
• A portfolio that shows both identity-level craft and shipped, high-traffic sites you can speak to at the architecture level

Nice-to-Haves

• Think about a website as an experience with pacing and narrative, rather than a set of pages to be laid out.
• Treat new tools as material to be tested rather than trends to have an opinion about, and can tell the difference between a capability and a demo.
• Move fluidly between a type-scale decision and a CMS schema decision, and consider neither beneath you nor outside your job.
• Are as interested in what the brand does in a room or a keynote as what it does in a viewport.