Product Designer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications? The posting includes sections: About Stable (company description), Role, What You Value, What You'll Do, Requirements, What We Offer. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. We need to decide which headings to use. The posting includes: - About Stable (company mission) – could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Stable" which is company overview. Could map to "About the role"? 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 can use other headings if appropriate? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. We should map content to those headings where appropriate. We have: - About the role: could include the description of role (the "Role" paragraph). Also maybe "What You'll Do" is responsibilities. - Responsibilities: could be "What You'll Do" list. - Requirements: the "Requirements" bullet list. - Qualifications: maybe "Preferred Experience" etc? But we have "Preferred Experience at B2B companies Bonus Experience designing for physical real-world processes Familiarity with frontend code and component systems". That could go under Qualifications or Skills. - Skills: maybe list of skills like design foundations, project management, communication, etc. - Benefits: "What We Offer" includes competitive salary, equity, unlimited vacation, medical/dental/vision, home office set-up, work from anywhere within US time zones, opportunities to shape future. - Pay: not specified explicitly; only "Competitive salary and generous equity". That is compensation but not a specific number. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive salary and generous equity, which is compensation info. So we could include a Pay section with that content. However they said "Prefer a few substantive sections over many thin ones." Might combine Pay and Benefits? But they gave separate headings. We could include Benefits section for medical etc, and Pay section for salary/equity. - Schedule: not specified (work from anywhere within US time zones maybe schedule flexibility). Not explicit schedule like full-time/part-time. Not given. So we should not create Schedule. - Qualifications: maybe we can put the "Requirements" as Qualifications? But they differentiate Requirements and Qualifications. Usually Requirements are must-haves, Qualifications are nice-to-haves. The posting has "Requirements" (6+ years experience etc) and then "Preferred Experience" etc. So we can map Requirements to Requirements heading, and Preferred Experience to Qualifications heading. - Skills: could be the design foundations etc listed under Requirements? Actually those are also under Requirements bullet list: "Excellent design foundations (hierarchy, layout, typography, interaction design)." That's a skill. Also "Strong project management skills", "Strong written and verbal communication skills." Could be under Skills. But we need to avoid duplication. Let's structure:

About the role

... role description paragraph (the Role section).

Responsibilities

• ... each bullet from "What You'll Do"

Requirements

• ... each bullet from "Requirements" (the list after ✅ Requirements)

Qualifications

• ... each bullet from "Preferred Experience" etc (the list after Requirements? Actually after Requirements there is "Preferred Experience at B2B companies Bonus Experience designing for physical real-world processes Familiarity with frontend code and component systems". We'll treat as qualifications.

Skills

maybe we could include the design foundations etc but they are already in Requirements. Might be redundant. Could omit Skills section if content already covered. But we need to follow instruction: Prefer a few substantive sections over many thin ones. If we already have Requirements covering those, we could skip Skills.

Benefits

• ... each bullet from "What We Offer" except salary/equity? Actually "Competitive salary and generous equity" is compensation; we could put that in Pay section. Benefits: unlimited paid vacation, medical/dental/vision insurance, home office set-up, work from anywhere within US time zones, opportunities to shape future.
  maybe as list.

  Pay

  Competitive salary and generous equity.

  We must not include sections with filler like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Not present. We must not include application instructions. Not present. We must not repeat job title as heading. Not. We must not include metadata like Job ID. Not present. Now we need to extract exact content. Let's copy the relevant sections. About Stable: The initial paragraph about mission etc. Should we include that? The instruction says we should include all substantive information. The "About Stable" is company description, not role-specific but still substantive. However the heading examples didn't include "About the company". But we could put it under "About the role"? Might be weird. Perhaps we can include a section "About the company" but not in allowed headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g...). Likely they expect us to use those headings only. So we should map company description to maybe "About the role"? But that seems odd. However the role description includes "As a product designer at Stable, you'll work..." That is role-specific. The company mission could be part of "About the role" as context. Could combine. Better: Use "About the role" heading to include both the role description and company mission? The instruction says "About the role" for section headings. So we can put role description there. The company mission could be placed in a preceding paragraph before any heading? The instruction says output ONLY the HTML fragment, no /. It didn't forbid having a preamble paragraph before headings. But they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It didn't say we cannot have other elements like

  outside headings. So we could have an introductory

  about Stable, then headings. Thus we can do:

  About Stable: ... mission etc.

  Then

  About the role

  Role description paragraph.

  Then responsibilities etc. Let's extract the About Stable text: "📫 About Stable Our mission is to make it simple to headquarter any business on the internet. Today, we provide companies with a business address and a dashboard to manage their physical mail online. Over 15,000+ companies like Brex, Doordash, and Gusto use Stable to automate their mailroom and act as their permanent business address with the IRS, state, and vendors. The rules that regulate US entities were written in the 1800s. Stable abstracts these antiquated requirements with tools that empower modern companies to move forward faster. These rules don't make sense for the way we work today — work takes place in the cloud and businesses are no longer tied to physical proximity or geography. We’re on a mission to fix the broken system of entity management. Starting with business addresses and mail, we’re abstracting the complex, archaic systems that make company-building painful and turning them into delightful experiences — so that modern businesses have the tools they need to move forward faster. We're backed by leading Silicon Valley investors like Y Combinator, Craft Ventures, Shakti, Hustle Fund, and founders from companies like Lattice, Apartment List, and FlexJobs. Our business is at an inflection point. We’re growing quickly with a product people love and we’ve proven we can service companies of all stages and industries — from early-stage startups to publicly traded companies in industries like technology, logistics, and property management. This is an opportunity to join an early-stage startup as one of the first employees and do work that directly impacts the future of how companies are built." We need to preserve all that. Remove emojis? The emojis are part of text but we can keep them? Probably we should keep the text but can drop emojis as they are not substantive? Might be okay to keep. Safer to keep them as they are part of original. But we can strip them for cleanliness. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Emojis are not substantive? They are decorative. I'd remove them. Now Role paragraph: "👩‍💻👨‍💻 Role As a product designer at Stable, you'll work in an AI-forward, builder-led environment. You'll write product briefs, query live business data, and work increasingly close to the code. You'll own your work from discovery through delivery, and you'll make impactful product decisions (prioritization, tradeoffs, and scope) in close collaboration with engineering and stakeholders. A defining aspect of this role is the nature of the problems you’ll work on. Stable sits at the intersection of digital software and physical operations. Designing great customer experiences means understanding real-world workflows inside processing centers handling 1M+ pieces of mail, and translating that complexity into simple, intuitive software. This cross-disciplinary work is challenging, nuanced, and a core differentiator for Stable. Our design team is small but established. You’ll build on strong foundations, collaborate with experienced designers, and play an active role in shaping how design shows up across the product as the company scales. Learn more about the team and culture at design.usestable.com." We need to keep that. What You Value: list of values (Be human, Stay curious, Act quickly with purpose, Insist on exceptional outcomes, Exceed customer expectations). Could be considered part of role description or maybe we can include under "About the role" or separate section? Not in headings list. Could be omitted? But it's substantive. Could be placed under "About the role" as a paragraph. Or we could create a section "Values" but not in allowed headings. Probably better to include under "About the role" as part of role description. What You'll Do: list of responsibilities. Let's extract the bullet points under ✅ What You'll Do: - Drive alignment: communicate clearly with stakeholders across the company, keeping teams aligned throughout the design process. - Hunt for data and customer opportunities: leverage our custom internal Stable MCP as your data analyst sidekick. Spin up your own reports and dashboards (with backup from our Data team when you need it). Speak and test directly with users to understand their pain points and needs. - Make product decisions: balance intuition, data, and research to determine what to build, what to cut, and when to ship. Own and challenge business goals while empathizing with and advocating for our customers. - Design product solutions: craft early concepts in tools like Figma Make, Claude, or Cursor. Make final polish and refinements in Figma or code, wherever it makes the most sense. - Partner with engineering: you’ll embed with a “pod” (three to four team members