Staff Design Engineer

We need to output HTML fragment with sections: About the role, Responsibilities (maybe "What you'll do"), Requirements/Qualifications (maybe "What we're looking for"), Benefits, Pay (if present), Schedule (if present). The posting includes: About Scribe (company description) – but we only need sections when there is real content. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They gave examples; we can use those headings if content matches. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate like EEO etc. We must preserve all substantive info. We need to decide which sections to include. Content: - tl;dr: short description (maybe we can incorporate into About the role? Actually "About the role" is a heading present in the posting: "📌 About the role". So we can use that heading. - About Scribe: company description. Could be a section "About the company" but not in list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't include About the company. However we could still include a section if we think it's substantive but not in list? The instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could also use other headings if needed? It says "use

for section headings (e.g. ...)" implying we should use those for those types of content; but we could also use other headings if needed? Safer to stick to those headings. The company description could go under About the role? Not ideal. Maybe we can include a brief paragraph under About the role that includes company context. The posting already has "About Scribe" before About the role. We could incorporate that into About the role section as introductory prose. - Responsibilities: corresponds to "What you'll do" and "Your first 90 days". Could combine into Responsibilities. - Requirements/Qualifications/Skills: The posting has "What we're looking for" (requirements) and "Nice to have". Could treat "What we're looking for" as Requirements or Qualifications. "Nice to have" as Skills. - Benefits: present. - Pay: present: "Compensation Salary varies by location. All full-time employees receive equity in Scribe. Final offers depend on experience and scope." Also later "Compensation Range: $215K - $280K". So we have pay info. - Schedule: present: "Location Hybrid: Based in San Francisco. We work from the office 3 days per week." That's schedule/location. Thus we can create sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We must not include filler like "commensurate with experience". We have actual numbers. We must not repeat job title as heading. We must output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

... (including tl;dr and About Scribe maybe)

Responsibilities

• ... items from "What you'll do" and "Your first 90 days"

Requirements

• ... from "What we're looking for"

Skills

• ... from "Nice to have"

Benefits

• ... benefits list

Pay

... compensation details

Schedule

... location/hybrid schedule

We need to preserve all substantive info. Let's extract. From 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 that helps people and AI agents do their best work. We're growing fast. Since our founding in 2019, we've grown to 7 million users across 600,000 businesses. Based in San Francisco, we've been named a LinkedIn Top Startup, are valued at over $1 billion, and are backed by leading investors. Join us in our mission to transform how people do work. We're builders who hold a high bar, move fast, and care deeply about each other and our customers." We can combine tl;dr and About Scribe into About the role paragraph. Responsibilities: from "What you'll do" bullet points (though not bullet list but sentences). Also "Your first 90 days" details. Let's list responsibilities: - Own Stylus: roadmap, triage, call on what goes in, measured against numbers: component adoption, accessibility coverage, documentation health, design system survey every 6–12 months. Set direction while absorbing requests from engineers and designers. - Build the hard components: where aesthetics and performance fight each other. 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 explorations faster in code than Figma: animation, keyboard, touch. Then test them with real users. - Work with designers without a handoff: 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. First 90 days details (could be part of responsibilities but we can include as separate bullet points under Responsibilities as they are more specific timeline). Let's extract: Days 1–30: - Ship, then map. - Land your first Stylus change in the first week or two - small, real, in production. - 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. - 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. We can include these as responsibilities. Requirements (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. Skills (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 Benefits: - Health, dental, and vision insurance for you and your dependents - Flexible paid time off and company holidays - 401(k) - Paid parental leave - Daily catered lunch (SF office) - Commuter benefits - Home office stipend Pay: - Salary varies by location. - All full-time employees receive equity in Scribe. - Final offers depend on experience and scope. - Compensation Range: $215K - $280K Schedule/Location: - Hybrid: Based in San Francisco. - We work from the office 3 days per week. We must not include boilerplate like EEO etc. The final paragraph about Equal Opportunity Employer should be removed. Now produce HTML. We need to wrap each section in

heading and then content. For lists use

• . For prose use

  . We must ensure we don't duplicate content. Let's craft. About the role paragraph: combine tl;dr and About Scribe. Let's write:

  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. 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 that helps people and AI agents do their best work. We're growing fast. Since our founding in 2019, we've grown to 7 million users across 600,000 businesses. Based in San Francisco, we've been named a LinkedIn Top Startup, are valued at over $1 billion, and are backed by leading investors. Join us in our mission to transform how people do work. We're builders who hold a high bar, move fast, and care deeply about each other and our customers.

  That seems good. Responsibilities: we can make a
  with each bullet as
  • . Might be long but okay. We'll include all bullet points from "What you'll do" and the 90-day plan as separate items. Let's list them conc