Job description

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 scribe.com 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 LinkedIn 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, DevEx, and the internal agents and skills). What you'll do - Own 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 TypeScript 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 decisions get better when the person making them has watched someone struggle. DAYS 31–60 · SET THE LINE. - Publish the Stylus roadmap and the quality bar that goes with it, and start using both to say no. This is the point where a backlog becomes a plan with an owner. - Pick the first hard component and build it - the one where aesthetics and performance fight each other, that nobody has had the time to do properly. - Start the legacy migration where it pays off most, and make the path off legacy obvious enough that other engineers take it without being asked. DAYS 61–90 · MAKE IT HOLD WITHOUT YOU. - Get adoption, accessibility, and documentation health reported automatically, so system health is a number we see rather than a question we ask. - Make contributing to Stylus something engineers and designers actually do: a clear way in for requests, contributions, and exceptions, with you making the call on each. - Ship the first AI workflows you'd want the rest of us using - the prompts, skills, and tooling that let designers and PMs build against the system safely. By six months: Stylus has a real roadmap instead of a backlog, the legacy-component migration is actively moving, and adoption is reported automatically rather than asked about. What we're looking for - 8+ years of experience in front-end development with a strong design sensibility and real depth in CSS, the DOM, and browser rendering. You have a view on when to use native platform elements versus a framework's version, and you can explain it. - Design ability of your own. You can make the call on an interaction, and you know which ones aren't worth what they cost to build. - You've worked on a design system at depth: components, primitives, tokens, versioning, adoption, and the governance to hold a line when a team wants an exception. - You shape the work rather than take tickets. You'll be accountable for a roadmap, which means knowing when to say no. - You already build with AI tools like Cursor and Claude Code, and you like getting other people using them well. - Accessibility, keyboard and touch input, and respecting user preferences are things you handle by default. If you're reading this thinking "that's me!", we want to meet you. Our loop is a code-and-craft exercise, not a portfolio review. Nice to have - Figma plugins, automations, or CI checks that report design system adoption and accessibility - Web components or multi-framework experience, including shipping a system into non-React surfaces - Desktop apps or browser extensions, especially always-on ones - Agent-facing or generative UI work Compensation & location SF-based candidates work hybrid, in the office 3 days per week. NYC candidates are fully remote. All full-time employees receive equity in Scribe. Final offers depend on experience and scope. All full-time employees receive equity in Scribe. Final offers depend on experience and scope. Benefits - Healthcare Coverage – Comprehensive health, dental, and vision plans, including two $0/month medical plan options for employees - Equity – Ownership in what we're building - 401(k) Plan – through Vestwell - Flex Benefit – $500/year for home office equipment, productivity tools, learning & development or fitness/wellness - Commuter Benefits – $100/month for SF based employees - PTO – Flexible paid time off and company holidays - Parental Leave – Paid leave to support growing families - Wellness & Family Support – Free Talkspace membership, One Medical access (location-dependent), and Kindbody discounts for family planning At Scribe, we celebrate our differences and are committed to creating a workplace where all employees feel supported and empowered to do their best work. Scribe is proud to be an Equal Opportunity Employer.

Requirements

Must-haves

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.
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 TypeScript 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 decisions get better when the person making them has watched someone struggle.
DAYS 31–60 · SET THE LINE.
Publish the Stylus roadmap and the quality bar that goes with it, and start using both to say no. This is the point where a backlog becomes a plan with an owner.
Pick the first hard component and build it - the one where aesthetics and performance fight each other, that nobody has had the time to do properly.
Start the legacy migration where it pays off most, and make the path off legacy obvious enough that other engineers take it without being asked.
DAYS 61–90 · MAKE IT HOLD WITHOUT YOU.

Nice-to-haves

Figma plugins, automations, or CI checks that report design system adoption and accessibility
Web components or multi-framework experience, including shipping a system into non-React surfaces
Desktop apps or browser extensions, especially always-on ones
Agent-facing or generative UI work
Compensation & location
SF-based candidates work hybrid, in the office 3 days per week. NYC candidates are fully remote.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

aidesign systemaccessibilityreacttypescriptfigmarest

Platform: ashby
Effort: quick

Benefits

Benefits detected in the listing.

Dental

Vision

401(K)

Pto

Paid Time Off

Parental Leave

Wellness