Senior Programs & Business Operations Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, there is a description: "Airbnb was born..." etc. That's about the company, maybe "About the role"? Actually "About the role" is typical heading for description of role. The posting includes: "The Community You Will Join ... The Experiences team ..." etc. That's description of role. We need to extract sections: "The Difference You Will Make" maybe responsibilities. "A Typical Day" maybe responsibilities. "Your Expertise" maybe qualifications/requirements. "Nice to have" maybe skills. "Your Location" maybe location but not a required section; we could put under "About the role"? But location is not one of the allowed headings; we can fold minor metadata into a short

or drop it. So location can be placed in a paragraph maybe under "About the role" or separate? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So location is minor metadata; we can put in a

maybe after heading? But we need to decide sections. We have Pay Range: $204,000—$249,000 USD. Also mention bonus, equity, benefits, Employee Travel Credits. So we have Pay and Benefits sections. Schedule: Not mentioned. So we should not create Schedule section. Benefits: mention "bonus, equity, benefits, and Employee Travel Credits." Also maybe "Our Commitment To Inclusion & Belonging" etc but that's boilerplate EEO; we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should exclude those sections. Thus we will have sections: About the role (company intro + role description), Responsibilities (The Difference You Will Make + A Typical Day), Requirements (Your Expertise), Skills (Nice to have), Benefits (bonus, equity, benefits, Employee Travel Credits), Pay (Pay Range). Possibly also "Qualifications" but we have Requirements and Skills; maybe we can combine Requirements and Qualifications? The instruction says use headings for those categories if content exists. We have "Your Expertise" which is requirements/qualifications. We'll put that under Requirements (or Qualifications). We'll also have Skills for nice-to-have. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the details. Let's extract content. About the role: Should include the introductory paragraphs about Airbnb, the Community You Will Join, etc. Also maybe "The Community You Will Join The Experiences team is responsible for scaling a curated, high-quality supply of unique activities hosted by local creators, iconic businesses, and operators worldwide and we're at an inflection point. How we surface Experiences is one of the biggest untapped demand levers we have. Recent signals (manual ranking outperforming the algorithm in places) point to a real gap: no one owns the demand-side merchandising strategy that sits on top of ranking. This role fills that gap. It is a biz ops and product ops hybrid focused on discoverability and merchandising: what we surface, to whom, and when." That's substantive. Responsibilities: From "The Difference You Will Make" bullet-like paragraphs: "As a Senior Business Operations Lead, you will own the merchandising strategy, partner deeply with Supply, Product, and Engineering on ranking and personalization, and build the reporting layer that tells us whether discoverability is improving. This role sits closer to Product and Eng than the other demand roles, so comfort driving a senior product partnership and influencing a technical roadmap is essential. You will report to the Director of Business Growth for Experiences and collaborate closely with others, including our SEM/SEO/Display lead, to ensure channel strategies are coherent and non-duplicative." Then "A Typical Day" list: bullet points: "Own merchandising & discoverability strategy Define the demand-side merchandising strategy on top of ranking: placement, sequencing, and the logic for what surfaces to which guestsPush for dynamic, context-aware ranking (day of week, availability, trends, market, traveler type) and represent the demand point of view in that roadmapPrioritize experiments that improve discoverability and translate results into decisions Partner with Product, Eng & Supply Serve as the senior demand counterpart to Product and Engineering on matching, personalization, and rankingClarify where merchandising is a demand mandate vs. a supply/product mandate, and drive alignment on ownershipKeep the product-to-ops conversation active, including through periods of reduced Product coverage Build the reporting layer Stand up dashboards and measurement for discoverability, spotlights, and placement performanceClose analytics and tooling gaps that limit how fast the team can learn and iterateBring a data-driven point of view on where merchandising investment pays off" We need to format as

• items. The text currently is a run-on; we need to split into logical items. We can infer items: - Own merchandising & discoverability strategy; define the demand-side merchandising strategy on top of ranking: placement, sequencing, and the logic for what surfaces to which guests. - Push for dynamic, context-aware ranking (day of week, availability, trends, market, traveler type) and represent the demand point of view in that roadmap. - Prioritize experiments that improve discoverability and translate results into decisions. - Partner with Product, Eng & Supply; serve as the senior demand counterpart to Product and Engineering on matching, personalization, and ranking. - Clarify where merchandising is a demand mandate vs. a supply/product mandate, and drive alignment on ownership. - Keep the product-to-ops conversation active, including through periods of reduced Product coverage. - Build the reporting layer; stand up dashboards and measurement for discoverability, spotlights, and placement performance. - Close analytics and tooling gaps that limit how fast the team can learn and iterate. - Bring a data-driven point of view on where merchandising investment pays off. We'll keep them as list items. Requirements: "Your Expertise" bullet list: - 12+ years in business operations, product operations, or strategy, ideally at a marketplace or consumer platform - Strong analytical foundation: comfortable in the data, building measurement, and turning insight into operating decisions - Proven experience partnering with Product and Engineering on ranking, search, personalization, or merchandising - Able to navigate ambiguity and drive alignment across senior stakeholders with competing mandates - Clear communicator who can influence a technical roadmap at a senior level without owning it directly We'll put under Requirements heading. Skills (Nice to have): - Background in search/ranking, recommendations, or merchandising systems - SQL or equivalent hands-on analytics capability We'll put under Skills heading. Benefits: "Our job titles may span more than one career level. The actual base pay is dependent upon many factors, such as: training, transferable skills, work experience, business needs and market demands. The base pay range is subject to change and may be modified in the future. This role may also be eligible for bonus, equity, benefits, and Employee Travel Credits." We need Benefits section: mention bonus, equity, benefits, Employee Travel Credits. Also maybe mention that base pay range is subject to change etc but that's more about Pay. We'll put benefits as bullet list: bonus, equity, benefits, Employee Travel Credits. Pay: Pay Range $204,000—$249,000 USD. Also mention base pay range subject to change etc. We'll put that in Pay section. Schedule: Not present, so omit. We also need to include location? It's minor metadata; we could fold into a short

  maybe under About the role or separate paragraph not as heading. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a

  for location after About the role maybe. But we must not create a heading for it. We'll just include a short paragraph: "Location: 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 minor metadata; we can include as a

  after About the role. We must remove boilerplate: EEO, Inclusion & Belonging, Reasonable Accommodations, Scam warning, etc. Also remove "Our Commitment To Inclusion & Belonging" etc. Also remove "How We'll Take Care Of You" maybe partially? That includes pay and benefits; we already captured pay and benefits. The rest of that paragraph about base pay range etc is part of Pay/Benefits; we already captured. The "Reasonable Accommodations" and "A Note on Recruiting Scams" are boilerplate; remove. Now produce HTML fragment: sections with

  headings, then content. Structure:

  About the role

  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 Experiences team is responsible for scaling a curated, high-quality supply of unique activities hosted by local creators, iconic businesses, and operators worldwide and we're at an inflection point. How we surface Experiences is one of the biggest untapped demand levers we have. Recent signals (manual ranking outperforming the algorithm in places) point to a real gap: no one owns the demand-side merchandising strategy that sits on top of ranking. This role fills that gap. It is a biz ops and product ops hybrid focused on discoverability and merchandising: what we surface, to whom, and when.

  Location: 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.

  Responsibilities

  • Own merchandising & discoverability strategy; define the demand-side merchandising strategy on top of ranking: placement, sequencing, and the logic for what surfaces to which guests.
  • Push for dynamic, context-aware ranking (day of week, availability, trends, market, traveler type) and represent the demand point of view in that roadmap.
  • Prioritize experiments that improve discoverability and translate results into decisions.
  • Partner with Product, Eng & Supply; serve as the senior demand counterpart to Product and Engineering on matching, personalization, and ranking.
  • Clarify where merchandising is a demand mandate vs. a supply/product mandate, and drive alignment on ownership.
  • Keep the product-to-ops conversation active, including through periods of reduced Product coverage.
  • Build the reporting layer; stand up dashboards and measurement for discoverability, spotlights, and placement performance.
  • Close analytics and tooling gaps that limit how fast the team can learn and iterate.
  • Bring a data-driven point of view on where merchandising investment pays off.

  Requirements

  • 12+ years in business operations, product operations, or strategy, ideally at a marketplace or consumer platform
  • Strong analytical foundation: comfortable in the data, building measurement, and turning insight into operating decisions
  • Proven experience partnering with Product and Engineering on ranking, search, personalization, or merchandising
  • Able to navigate ambiguity and drive alignment