Design Engineer

Position: Staff Design Engineer
tl;dr –We are looking for a Staff Design Engineer who thinks like a designer, codes like a front-end engineer, and treats AI as a collaborator.

About Scribe Scribe is where exceptional people come to do the best work of their careers. More than 94% of the Fortune 500 use Scribe to own their specialized intelligence: the unique way their teams work, decide, and get things done. Our Specialized Intelligence platform automatically captures how work happens and turns it into a living asset for people and AI agents.

We're growing fast. Since our founding in 2019, we've reached 7 million users across 600,000 businesses. Based in San Francisco, we're a Linked In Top Startup, valued at over $1B, and backed by leading investors. Join us in our mission to transform how people work.

About the role

We're hiring a Staff Design Engineer to own Stylus, our design system, and the quality of what we ship across the web app, desktop app, browser extension, and marketing site. As a Staff Design Engineer at Scribe, you sit at the intersection of design and frontend engineering.

AI has made designs, code, and prototypes cheap to produce. What separates good product from great product now is judgment: knowing which interactions are worth building, and then building them well. We want someone who can look at a problem, decide what it should feel like, and ship it themselves.

At its core, this role is anchored in Stylus ownership. From there you'll drive both design craft (product polish, prototyping, and interaction quality) and platform power (frontend tooling, Dev Ex, and the internal agents and skills).What you'll doOwn Stylus. The roadmap, triage, and the call on what goes in, measured against numbers we actually track: component adoption, accessibility coverage, and documentation health, plus the design system survey we run every 6–12 months.

You'll set direction while absorbing requests from engineers and designers.

Build the hard components. The ones where aesthetics and performance fight each other. You'll decide what becomes a shared primitive and what stays a one-off, and build both.

Prototype in code and validate with customers. Build interactive prototypes in React and Type Script for the explorations that are faster in code than in Figma: animation, keyboard, touch. Then test them with real users.

Work with designers without a handoff. A designer starts a direction, you iterate together in Figma or directly in code, and you're the person who can say what a given interaction will cost to build.

Keep design and code from drifting apart. Tokens aligned with design, legacy components actively migrated onto the system instead of left alone, and Figma-to-code tooling that stays useful.

Make the system work for agents as well as people. Explore emerging UX patterns and AI-ready design languages, and build the primitives we'll need as more of our UI gets assembled by models.

Share how you work. Document the prompts, patterns, and workflows you use in Cursor and Claude Code and share them with designers and engineers. Mentor engineers on design principles.

Your first 90 days

We hire people who set their own agenda, so treat this as the shape of the first quarter rather than a checklist handed to you.

Days 1–30
· Ship, then map.

Land your first Stylus change in the first week or two - small, real, in production. You'll learn more about our stack from one merged component fix than from a month of onboarding docs.

Build the honest picture: where components have drifted, which surfaces are furthest from the system, and what our accessibility coverage actually is versus what we assume it is.

Meet the people who file the requests - designers, product engineers, marketing - and watch customers use the product. Craft…