We need to output only HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove application instructions, recruiting scams note, etc. Keep details about role, responsibilities, expertise, preferred experience, location, pay range, benefits? There's mention of benefits: "This role may also be eligible for bonus, equity, benefits, and Employee Travel Credits." Also "Our job titles may span more than one career level. The actual base pay is dependent upon many factors..." Also "Pay Range $164,000—$193,000 USD". Also location: "Your Location: This position is US - Remote Eligible. The role may include occasional work at an Airbnb office or attendance at offsites, as agreed to with your manager. While the position is Remote Eligible, you must live in a state where Airbnb, Inc. has a registered entity." Also "Our Commitment To Inclusion & Belonging" is EEO boilerplate; we should remove. Also "How We'll Take Care Of You" includes pay range etc. We'll keep pay range and benefits.
We need sections: About the role (maybe intro paragraph). Responsibilities (list of duties). Requirements (maybe expertise). Qualifications (maybe preferred experience). Skills (maybe technical skills). Benefits (bonus, equity, benefits, Employee Travel Credits). Pay (pay range). Schedule (maybe location/remote eligibility? Not exactly schedule but could be work schedule: remote eligible, occasional office/offsite). The instruction: include a section ONLY when posting has real, specific content for it. So we need to see if we have content for each.
Let's parse:
- About the role: The first paragraphs describing Airbnb, Community You Will Join, The Difference You Will Make. That's about the role. So we can put that in About the role section.
- Responsibilities: "A Typical Day" bullet list of duties: deliver major projects end to end, partner with content teams, own authoring platform, design for system "-ilities", raise technical bar, write thinking down, grow people around you, work in agent-assisted development loop. Those are responsibilities.
- Requirements: "Your Expertise" list: 5+ years designing and implementing complex systems end to end in integrated enterprise environments, proven experience building and maintaining custom author-facing tools, workflows, automations, and integrations in an enterprise headless CMS (Contentstack preferred), track record of owning delivery on projects that span multiple workstreams, depth in front-end and back-end development preferably with TypeScript, React, Node.js, strong working knowledge of large-scale content data analysis, bulk updates, reporting, demonstrated ability to build and operate high-performance, scalable, fault-tolerant internal tooling, design for failure modes and operational requirements, fluency with agentic development workflows, clear technical writing, experience mentoring engineers, comfortable navigating ambiguity, ability to drive alignment, manage projects, collaborate effectively with technical and non-technical stakeholders.
- Qualifications: "Preferred Experience" list: working with structured data in enterprise taxonomy or knowledge graph platforms, familiarity with architectural patterns of large, high-scale web applications, experience with modern reporting or analytics platforms such as Tableau or Grafana, BS, MS, or PhD in Computer Science or a related field.
- Skills: Could be overlapping with Requirements; but we could treat Skills as technical skills: TypeScript, React, Node.js, Contentstack, AI agents, etc. However we might not need separate Skills if we already covered in Requirements. But we need to decide: The instruction says prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they ask to use headings for those specific categories if content exists. We have content for Requirements (Your Expertise) and Qualifications (Preferred Experience). So we can include both.
- Benefits: "This role may also be eligible for bonus, equity, benefits, and Employee Travel Credits." Also maybe "Reasonable Accommodations" but that's boilerplate. So we have benefits content.
- Pay: Pay Range $164,000—$193,000 USD. Also mention base pay dependent on factors etc. That's specific.
- Schedule: Location and remote eligibility info: "Your Location: This position is US - Remote Eligible. The role may include occasional work at an Airbnb office or attendance at offsites, as agreed to with your manager. While the position is Remote Eligible, you must live in a state where Airbnb, Inc. has a registered entity." That's schedule/location info. Could be considered Schedule section.
We must not include boilerplate like EEO, inclusion, recruiting scams, reasonable accommodations note (though that is somewhat relevant but maybe considered boilerplate? It's about accommodations for disability; could be considered part of benefits? But it's more legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The reasonable accommodations note is likely part of EEO/legal; better to remove. Also the "A Note on Recruiting Scams" remove.
Also remove "Our Commitment To Inclusion & Belonging" and "Equal Employment Opportunity". Also remove "How We'll Take Care Of You" heading? Actually that section includes pay range and benefits; we need to keep pay and benefits but not the heading. We'll extract the relevant sentences.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the exact details, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should keep the original wording, not paraphrase? But we need to format into HTML with headings and lists. We can keep the sentences as is, maybe break into
or
. Must not lose any detail.
Thus we need to copy the relevant sentences exactly as they appear (or close). Let's extract.
About the role: The first few paragraphs:
"Airbnb was born in 2007 when two hosts welcomed three guests to their San Francisco home, and has since grown to over 5 million hosts who have welcomed over 2 billion guest arrivals in almost every country across the globe. Every day, hosts offer unique stays and experiences that make it possible for guests to connect with communities in a more authentic way. The Community You Will Join The Content Products team, within the BizTech organization, delivers the technology that empowers Airbnb’s knowledge culture, drives connection, and scales support for employees and the Airbnb community. Our platforms power Guest and Host support experiences in the Airbnb Help Center and Resource Center, the Knowledge Center for our support ambassadors, and One Airbnb for employees. The Difference You Will Make As a Senior Systems Engineer on the Content Products team, you will build the systems that power content management at Airbnb: advanced authoring capabilities, frictionless content workflows, analytics that improve content quality, auditing that meets compliance requirements, and AI-assisted experiences for writers. You will own major projects that span multiple workstreams and often arrive loosely defined, and you may lead a small pod of two to three engineers to deliver them. You will partner with product, engineering, and content teams across Airbnb to meet the evolving needs of everyone who creates, manages, and delivers content."
We need to keep that as prose in . Possibly split into multiple paragraphs but okay.
Responsibilities: The "A Typical Day" section includes multiple sentences each starting with a bold phrase? Actually the text:
"A Typical Day Deliver major projects end to end. Take end-to-end accountability across the software development lifecycle on projects that span multiple workstreams — breaking the work down, building the plan, and leading a small engineering pod where the project calls for it.Partner with content teams. Map and improve authoring workflows alongside content, product, and engineering partners; translate them into technical requirements; and deliver the capabilities that follow, including reporting, product integrations, and AI-assisted authoring and editing features.Own the authoring platform. Share the technical ownership of Contentstack, our enterprise headless CMS, with our engineering team — extending it with custom UI extensions and authoring apps in React that follow Airbnb’s Design Language System, building the integrations that bring structured taxonomy and knowledge graph capabilities to our support and knowledge surfaces, and improving content organization, security, and discoverability through taxonomies, controlled vocabularies, and metadata standards.Design for the system “-ilities.” Design systems that satisfy both functional requirements and the -ilities — reliability, security, maintainability, observability. Identify and design for potential failure modes, participate actively in incident response, and implement corrective actions that reach beyond the immediate fix.Raise the technical bar. Identify and deprecate or improve low-quality code, services, and frameworks, and plan quality improvements into the team’s roadmap rather than around it. Give constructive input in technical design and code review that helps shape the team’s direction.Write the thinking down. Document technical solutions clearly, surfacing the benefits, risks, and tradeoffs you considered — then seek out and incorporate peer review and feedback on your designs. Analyze data, form hypotheses, experiment, learn, and iterate to improve Airbnb’s content authoring and delivery experience.Grow the people around you. Coach and mentor engineers inside and outside the team, give timely and actionable feedback, help onboard and integrate new team members, and contribute to interviewing and to Airbnb’s broader technical community.Work in an agent-assisted development loop. Direct AI agents to explore unfamiliar systems, prototype solutions, generate and review code, and validate changes — while staying accountable for correctness and quality"
We need to turn each bullet into
. The sentences are separated by periods but no explicit bullet. We'll split at each capitalized verb phrase after a period? Let's list:
- Deliver major projects end to end.
- Take end-to-end accountability across the software development lifecycle on projects that span multiple workstreams — breaking the work down, building the plan, and leading a small engineering pod where the project calls for it.
- Partner with content teams. Map and improve authoring workflows alongside content, product, and engineering partners; translate them into technical requirements; and deliver the capabilities that follow, including reporting, product integrations, and AI-assisted authoring and editing features.
- Own the authoring platform. Share the technical ownership of Contentstack, our enterprise headless CMS, with our engineering team — extending it with custom UI extensions and authoring apps in React that follow Airbnb’s Design Language System, building the integrations that bring structured taxonomy and knowledge graph capabilities to our support and knowledge surfaces, and improving content organization, security, and discoverability through taxonomies, controlled vocabularies, and metadata standards.
- Design for the system “-ilities.” Design systems that satisfy both functional requirements and the -ilities — reliability, security, maintainability, observability. Identify and design for potential failure modes, participate actively in incident response, and implement corrective actions that reach beyond the immediate fix.
- Raise the technical bar. Identify and deprecate or improve low-quality code, services, and frameworks, and plan quality improvements into the team’s roadmap rather than around it. Give constructive input in technical design and code review that helps shape the team’s direction.
- Write the thinking down. Document technical solutions clearly, surfacing the benefits, risks, and tradeoffs you considered — then seek out and incorporate peer review and feedback on your designs. Analyze data, form hypotheses, experiment, learn, and iterate to improve Airbnb’s content authoring and delivery experience.
- Grow the people around you. Coach and mentor engineers inside and outside the team, give timely and actionable feedback, help onboard and integrate new team members, and contribute to interviewing and to Airbnb’s broader technical community.
- Work in an agent-assisted development loop. Direct AI agents to explore unfamiliar systems, prototype solutions, generate and review code, and validate changes — while staying accountable for correctness and quality.
We need to ensure we keep all details. Some sentences have two sentences combined