Staff Design Engineer - Americas

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to extract from the posting. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. Let's parse the content. The posting is a long narrative by Abhik. It includes: - Intro: personal story, role close to heart, design engineering formal role, first hire, doubling team. - Description: Design Engineer at Ashby isn't just frontend engineer nor designer vibe coding prototypes; combining excellence. - You’ll Work On Our Most Challenging Design Problems, Help Others Improve Their Designs By Expanding And Enhancing Our In-house Design System, And Consult On Bespoke Design Work Needed By Product Engineers. - Examples: Redesigned mobile web app... Built flexible composable components... Helped product engineer improve info hierarchy... - The Design Engineer Role Is More Common Today... Unique opportunity: product at scale, >100k weekly active users, millions of candidates per week, notable customers. - You’ll get to test ideas with recruiting team and hiring managers, hear customer feedback early. - This role has commitment of Benji and me... - You get to shape UI/UX of powerful complex product. Users need software that helps them move quickly while adapting to workflows. UI not simple chatbox nor sea of knobs; approachable first time while offering powerful customization. - Why You Shouldn’t Apply: list of reasons (design system only, extensive research before implementation, want everything perfect before release, need excellent taste and execution, need company-driven process, only want exciting work). Actually these are reasons you might not enjoy. - What Seniority/Level To Apply For: levels Junior, Design Engineer (mid/senior), Staff Design Engineer (this posting). Provide expectations. - What We’re Building: description of problem in TA software, building Ashby. - Engineering Culture: Minimal process, ownership, natural collaboration, deliberate communication, investing in tools, building diverse team, etc. Includes bullet points. - Increase Leverage, not Team Size: investment in developer tooling, CI/CD, debugger, building blocks, AI-powered tooling, unlimited token budget. We need to produce sections: maybe About the role (intro + description), Responsibilities (what you'll work on), Requirements/Qualifications (seniority levels expectations), Skills (maybe design and engineering proficiency), Benefits (maybe not explicit), Pay (none), Schedule (none). We should only include sections with real specific content. Check if there is any explicit Benefits, Pay, Schedule mentioned. I didn't see explicit benefits like health insurance, PTO, remote, etc. There's mention of "generous paid family leave" under engineering culture. That's a benefit. Also "small budget to meet up with folks in your city/region". Also "unlimited token budget". Also "focus time sacred, for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. So headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to decide which sections to include. We have substantive content for: - About the role: intro, description of role, why it's unique, etc. - Responsibilities: bullet list of what you'll work on (most challenging design problems, improve designs via design system, consult on bespoke design work, examples). Could also include shaping UI/UX, etc. - Requirements/Qualifications: seniority levels expectations (Junior, Design Engineer, Staff). Could combine as Requirements. - Skills: maybe design and engineering proficiency, taste, execution, ability to ship, etc. Could be part of Requirements. - Benefits: generous paid family leave, small budget for meetups, unlimited token budget, focus time ( for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying we can use those headings but not limited? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. So we need to fit all content under those headings. We can put the "Why You Shouldn’t Apply" under Responsibilities as a list of things that might not fit. Or under About the role as a note. We also have "What Seniority/Level To Apply For" which is about expectations; could go under Requirements or Qualifications. We have "What We’re Building" which is about product/mission; could go under About the role. We have "Engineering Culture" which could go under Benefits? Or maybe under About the role as well. But we have a Benefits section for tangible benefits; culture could be part of About the role. We have "Increase Leverage, not Team Size" about tooling; could be part of Benefits or About the role. We need to avoid duplication. Let's structure:

  About the role

  ... intro, description, unique opportunity, product scale, mission, engineering culture, etc.

  Responsibilities

  • Work on our most challenging design problems.
  • Help others improve their designs by expanding and enhancing our in-house design system.
  • Consult on bespoke design work needed by product engineers.
  • Redesign mobile web app: talk with customers, wireframe new flows, implement design system, turn wireframes into polished UI.
  • Build flexible, composable components in design system for setup wizards.
  • Help product engineers improve information hierarchy and scannability of designs (e.g., candidate assessments).
  • Shape the UI/UX of a powerful, complex product that balances approachability with powerful customization.
  • Test ideas with recruiting team and hiring managers, gather customer feedback quickly.
  maybe also include the "Why you shouldn't apply" as a list of things that might not be a fit: could be under Responsibilities as a note: "This role may not be a fit if you..." but we can include as a
  under Responsibilities with a heading? Might be confusing. Could add a

  preceding list: "Consider whether you enjoy..." but we can just include as part of Responsibilities. Better: Add a

  Considerations

  but not allowed. So we could incorporate into Responsibilities as a note: "Note: This role may not be ideal if you..." as a

  .

  Requirements

  We have posted levels from Junior to Staff. The higher the level, the more experience and alignment with the role we expect.

  • Junior Design Engineer: ≤2 years industry experience as designer or engineer; projects (personal or professional) with at least a couple users showcasing great visual taste and burgeoning talent in both UI/UX and engineering.
  • Design Engineer (Mid/Senior): 2+ years continuous experience as engineer or designer; good proficiency in both design and engineering, with exceptional proficiency in the discipline you practice full-time; experience designing products and shipping code to hundreds of users (even via side projects).
  • Staff Design Engineer (this posting): practiced our flavor of Design Engineering professionally; major contributions to a design system; designed and implemented features for hundreds of users; iterated on them through user feedback.

  Skills

  Combines excellence in both design and engineering; strong visual taste and execution; ability to ship fast and iterate based on user feedback; comfortable with minimal process and high ownership; collaborative and kind; lifelong learner.

  Benefits

  • Generous paid family leave.
  • Small budget to meet up with folks in your city/region.
  • Unlimited token budget for AI-powered tooling.
  • Focus time protected:
  • No leetcode interviews.
  • Opportunity to work on product at scale (100k+ weekly active users, millions of candidates per week) with notable customers (Notion, Linear, Shopify, Snowflake).
  • Engineering culture that values minimal process, ownership, natural collaboration, deliberate communication, investment in tools and abstractions, diverse team.
  We need to ensure we didn't miss any substantive info: mention that first hire was over