Staff Software Engineer - DevX

We need to output HTML fragment with sections: About the role? Actually we have sections: About The Team, The Role, What You'll Do, What We're Looking For, Nice to Have, Who We Are (Company, Product), Some Of Our Benefit Programs Include, Other Fun Facts About Amplitude, etc. Also we have salary ranges for various locations; we need to include Pay section only if posting actually states them. Yes they have salary ranges for Colorado, NYC, California, Washington. So we should include a Pay section with those details. Benefits: they list benefit programs; we should include Benefits section. Schedule: not mentioned; no schedule info, so omit Schedule. Also we need headings:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to these headings appropriately. The posting includes: About The Team (maybe "About the role"? Actually "About The Team" could be under "About the role"? But we need to follow instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when we have content. If we have content that matches those categories, we use that heading. If not, we might need to adapt? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections; but we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to use those specific headings when applicable. So we need to map content to those categories. Let's identify content: - About the role: could be "About The Team" and "The Role" description. We'll combine into About the role section. - Responsibilities: "What You'll Do" list. - Requirements: "What We're Looking For" (staff-level experience etc.) plus maybe "Nice to Have" could be under Requirements or Skills? Could treat Nice to Have as part of Requirements or separate Skills? But we have Skills heading; we could put Nice to Have under Skills. However we need to avoid filler. We'll include Requirements (mandatory) and Skills (nice-to-have). Or we could put Nice to Have under Skills. - Qualifications: maybe not separate; we could combine with Requirements. - Benefits: "Some Of Our Benefit Programs Include" list. - Pay: salary ranges. - Schedule: not present, omit. We also have other sections like "Who We Are" (Company, Product) and "Other Fun Facts About Amplitude". Those may not map to headings; but we need to preserve ALL substantive information. If we omit those sections, we lose info. The instruction: "Prefer a few substantive sections over many thin ones." But also "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include that info somewhere. Could we incorporate into About the role or other sections? Possibly under About the role we could add a paragraph about company and product. Or we could create a section like "About the Company" but that's not in the allowed headings list. However 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 suggests we should use those for sections. It might be okay to add other headings if needed, but better to stick to those. We could incorporate company/product info into About the role or maybe under a heading "About the role" we can include a paragraph about the company and product. That would preserve info. Similarly "Other Fun Facts About Amplitude" could be added as a paragraph under About the role or maybe under Benefits? But better to add a short paragraph under About the role or maybe under a heading "About the role" we can include a subsection? But we cannot nest headings inside? We could just add a

after the list. Thus final HTML:

About the role

then paragraphs about team, role description, company, product, fun facts. Then

Responsibilities

with

• items from What You'll Do. Then

  Requirements

  with
  • items from What We're Looking For. Then

    Skills

    with
    • items from Nice to Have. Then

      Benefits

      with
      • items from Some Of Our Benefit Programs Include. Then

        Pay> section with salary ranges. We need to ensure we don't repeat job title as heading. Not needed. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out the EEO statement, the fraud warning, the Colorado/NYC etc salary details? Actually salary details are substantive; we keep them. The EEO statement and fraud warning we remove. Also remove "Based on Colorado law..." etc? Those are salary details for specific locations; we keep them as part of Pay. But the sentences like "Based on Colorado law, the following details are for individuals who will work for Amplitude in Colorado:" is part of the salary detail; we can keep the range but maybe drop the explanatory sentence? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The sentence "Based on Colorado law, the following details are for individuals who will work for Amplitude in Colorado:" is substantive? It's explanatory but maybe we can keep it as part of the Pay section. However it's somewhat boilerplate but it's location-specific. I'd keep it as part of the Pay paragraph. We also need to remove duplicated lines: there is duplicate "Based on legislation in Washington state..." appears twice; we should keep only one. Also remove "By applying for this job, you acknowledge that Amplitude processes your personal data..." etc (privacy notice) - that's legal boilerplate; remove. Also remove "Staying Safe - Protect Yourself From Recruitment Fraud" etc. Also remove "Amplitude provides equal employment opportunities (EEO)." etc. Also remove "This role is eligible for equity, benefits and other forms of compensation." maybe keep? It's somewhat generic but could be considered substantive? It's about compensation; but we already have Pay section. Might be okay to keep as part of Pay? But it's vague; maybe drop as it's not specific. Also remove "Other Fun Facts About Amplitude" maybe we keep as fun facts paragraph. Now craft content. About the role paragraph(s): - Amplitude is the leading AI analytics platform... (first paragraph). Could include that. - About The Team: DevX owns engineering velocity... (team description). - The Role: We're looking for a Staff Software Engineer – DevX (Hybrid – San Francisco) who bridges infrastructure and application thinking... (role description). We'll incorporate. - Company values etc: maybe include under About the role. - The Product: Amplitude is a digital analytics platform... (product description). - Other Fun Facts: list of fun facts. We'll combine into a few paragraphs. Now Responsibilities: from "What You'll Do" bullet points: - Cloud development platform: Unify and scale our existing local, remote, and ephemeral development environments across a polyglot codebase. Make it fast and reliable for engineers and AI agents to provision environments, build, test, debug, and validate changes, with reproducible test data and clear access controls. - Software factory: Find the biggest bottleneck in the engineering workflow, automate it, then move to the next one. This increasingly means building the sandboxes and tooling that let AI agents do the work directly, not just assist with it. - Developer experience & tooling: Own build systems, CI/CD, developer environments, and internal tooling. Drive down build/CI time, deploy risk, and feedback latency. - Technical leadership: Set direction and standards, turn ambiguous problems into roadmaps, and mentor senior/staff engineers through design review and pairing. We'll make each as

        . Requirements: from "What We're Looking For": - Staff-level engineering experience and impact. - Full-stack, infra-leaning skills, strong on the backend and systems side. - Experience moving a team's development workflow into the cloud (VMs, remote environments, preview branches, sandboxes). - A track record of shipping developer tooling or platform infrastructure that measurably improved velocity. - Hands-on experience building agentic or AI-powered engineering workflows, used responsibly with human oversight. - Strong judgment, clear writing, and the ability to drive alignment without formal authority. We'll list as

        . Skills (Nice to Have): - Monorepo tooling or large-scale platform migrations. - Agent harness infrastructure: eval frameworks, orchestration, or sandboxing for LLMs. Benefits: from "Some Of Our Benefit Programs Include": - Excellent Medical, Dental and Vision insurance coverages, with 100% employer-paid premiums for employee Medical, Dental, Vision on select plans - Flexible time off, paid holidays, and more - Generous stipends to spend on what matters most to you, whether that’s wellness (monthly), commuter transit/parking (monthly), learning and development (quarterly), home office equipment (annual), and much more - Excellent Parental benefits including: 12-20 weeks of Paid Parental Leave, Carrot Fertility Benefits/Adoption/Surrogacy support, Back-up Child Care support - Mental health and wellness benefits including no cost employee access to Modern Health coaching & therapy Sessions and high quality physician office experience via One Medical membership (select U.S. locations only) - Employee Stock Purchase Program (ESPP) We'll list each as

        . Pay: we need to include salary ranges for various locations. We'll combine into a paragraph maybe with bullet list? The instruction: use

        • for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits; it's compensation info. Could be a

          . We'll put a

          with the ranges. We need to include: - Colorado range: $198,000 - $299,000 base salary (inclusive of bonus or commission) - New York City salary range: $220,000 - $331,000 base salary (inclusive of bonus or commission) - California salary range: $220,000 - $331,000 base salary (inclusive of bonus or commission) - Washington salary range: $198,000 - $299,000 base salary (inclusive of bonus or commission) - Washington only: unlimited PTO, 10 to 13 holidays annually (will vary), medical dental and vision PPO and CDHP plans. Finally, a company sponsored 401(k) retirement plan. But note the Washington only benefits are actually benefits; but we already have benefits section; we could incorporate that into benefits but it's location-specific. However we already have benefits section generic; we could add a note under Pay about Washington-specific benefits. But maybe better to keep Pay section just salary ranges, and note Washington-specific benefits under Benefits? However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can keep Pay heading with salary ranges. The Washington-only benefits are not salary; they'd be benefits. But we already have benefits section; we could add a

        • under Benefits for Washington-specific benefits? But that would be location-specific; maybe we just keep generic benefits and ignore location-specific benefits as they are part of benefits but not generic. However we must preserve ALL substantive information