Member of Product Staff

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. The posting includes: - About Arena Intelligence (company description) – not a heading we need? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." We can include a paragraph about company? Not required but we can include as prose

. The sections we need: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. Let's extract content: About The Role: paragraph describing role: "We're looking for a Member of Product Staff to be the GM and owner of a product pillar, identifying what to build, building conviction, shipping with engineering and research, and driving it to measurable outcomes. This is a highly cross functional role and You are close to users, close to the data, and close to the code. You write the PRDs, you query the tables yourself, and you stay with the product after launch until it works. Arena is small, and the product surface is unusually broad: a consumer product used by tens of millions of people each month, an API and enterprise offering that leading AI labs and enterprises rely on, and the evaluation methodology and leaderboard that sit underneath all of it. Depending on your background, you'll focus on one of the following areas: Enterprise & API. ... Evaluation. ... Growth." We can treat that as prose under About the role. Responsibilities: The bullet list after "YOU'LL Own product areas end to end..." etc. Let's extract: - Own product areas end to end, from identifying opportunities that aren't on anyone's roadmap, to building conviction, shipping, and driving to measurable outcomes - Ship and iterate, You measure, course-correct, and drive to sustained impact against the companies north star goals. - Work with ML researchers to turn research into product, creating new methods, models, and data consumable for the people who need them - Develop a deep understanding of our highest-expectation users, consumers, labs, enterprises, researchers and how they actually use Arena - Monitor user feedback, usage data, and analytics to identify trends, prioritize initiatives, and refine what we've shipped - Write the PRDs, specs, and narratives that align engineering, design, research, and leadership, and create clarity out of ambiguity when needed - Make high-stakes product decisions under uncertainty, and be accountable for the outcomes - Raise the product quality bar on the team and introduce practices others adopt, unblock teammates, and hold the line on craft We need to format as

• . Requirements: The "YOU'LL HAVE" section: list of requirements. - 5-10+ years of product management experience on consumer, developer, or enterprise products, ideally including 0-to-1 work at an early-stage company - A track record of repeated, attributable impact, multiple projects across different roles or companies where you can quantify outcomes (revenue, engagement, efficiency) and the impact sustained after you moved on - Product judgment, taste and autonomous ownership. You've identified opportunities, validated them with evidence, built buy-in, shipped, and the bet paid off. You’ve killed important projects in your career for the betterment of the product. - Clear, persuasive communication. You build buy-in across engineering, research, design, and leadership. You create clarity for others, not just yourself - Technical depth to work directly with engineers and researchers - Genuine conviction about AI evaluation and Arena's mission — you can articulate why this domain matters and where the product should go - Comfort with ambiguity. We're a startup. Scope is fluid, context shifts, and you'll wear many hats Qualifications: maybe same as requirements? The posting also has "BONUS POINTS" which could be considered Qualifications or Skills. We need to decide sections: Qualifications maybe for required qualifications; Skills maybe for bonus points? The instruction: Use sections only when posting has real, specific content. We have content for Requirements (the YOU'LL HAVE). We have content for Bonus Points (which could be Skills). We have Benefits: "We offer competitive compensation and equity aligned to the markets where our team members are based. The base salary range will depend on the candidate’s permanent work location. Comprehensive health and wellness benefits, including medical, dental, vision, and additional support programs. The opportunity to work on cutting-edge AI with a small, mission-driven team A culture that values transparency, trust, and community impact". That's benefits. Pay: Not explicitly given a number; they say base salary range will depend on location, competitive compensation and equity. That's vague but still mentions compensation. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state compensation and equity, but not specific numbers. Is that enough? It says "competitive compensation and equity". That is a statement about pay. I'd include a Pay section with that statement. However they also say "The base salary range will depend on the candidate’s permanent work location." That's still about pay. So we can include Pay. Schedule: Not mentioned. No schedule info. So omit Schedule. Skills: Could be the bonus points. But we also have technical depth etc already in requirements. Bonus points could be considered "Skills". Let's treat Bonus Points as Skills. Qualifications: Might be same as Requirements? Usually Qualifications are the required qualifications. But we already used Requirements for the YOU'LL HAVE list. Could rename that as Qualifications. However the instruction lists possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have content for About the role, Responsibilities, Requirements (maybe), Qualifications (maybe), Skills (bonus points), Benefits, Pay. We could map: - About the role: paragraph. - Responsibilities: the YOU'LL list. - Requirements: the YOU'LL HAVE list (core requirements). - Qualifications: maybe we could leave empty? But we must not emit heading with filler. So if we don't have distinct qualifications beyond requirements, we omit Qualifications. - Skills: Bonus points list. - Benefits: the benefits paragraph. - Pay: compensation statement. - Schedule: omit. Let's verify we have real content for each. Now produce HTML:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  ...

  Pay

  ...

  Make sure no extra whitespace? It's fine. Now extract exact text. About the role paragraph: Let's copy from "About The Role" section up to before "YOU'LL". The text: "We're looking for a Member of Product Staff to be the GM and owner of a product pillar, identifying what to build, building conviction, shipping with engineering and research, and driving it to measurable outcomes. This is a highly cross functional role and You are close to users, close to the data, and close to the code. You write the PRDs, you query the tables yourself, and you stay with the product after launch until it works. Arena is small, and the product surface is unusually broad: a consumer product used by tens of millions of people each month, an API and enterprise offering that leading AI labs and enterprises rely on, and the evaluation methodology and leaderboard that sit underneath all of it. Depending on your background, you'll focus on one of the following areas: Enterprise & API. The API and enterprise product surface that labs, enterprises, and independent researchers build on. You'll partner directly with customers to integrate models, run evals, and deliver high-quality results; translate their feedback into product and engineering initiatives; and own packaging and monetization so that every new product ships instrumented, billable, and correctly represented in our systems. Evaluation. The products that turn human preference into trustworthy evaluation. This is the leaderboard, the methodology, and the tools model developers use. You'll partner with research to develop new metrics, methodologies, and evaluation protocols that go beyond traditional benchmarks, disentangle performance factors like style, reasoning, and robustness, and protect the scientific integrity and transparency of the Arena leaderboard. Growth. How tens of millions of people discover, use, and come back to Arena. You’ll run experiments, and partner with design and marketing engineering to turn what we learn about our highest-expectation users into a product they can't stop using." We need to ensure we keep the content exactly as given, but we can trim extra spaces. Keep as is. Now Responsibilities list items: Let's copy each bullet. From "YOU'LL Own product areas end to end, from identifying opportunities that aren't on anyone's roadmap, to building conviction, shipping, and driving to measurable outcomes" "Ship and iterate, You measure, course-correct, and drive to sustained impact against the companies north star goals." "Work with ML researchers to turn research into product, creating new methods, models, and data consumable for the people who need them" "Develop a deep understanding of our highest-expectation users, consumers, labs, enterprises, researchers and how they actually use Arena" "Monitor user feedback, usage data, and analytics to identify trends, prioritize initiatives, and refine what we've shipped" "Write the PRDs, specs, and narratives that align engineering, design, research, and leadership, and create clarity out of ambiguity when needed" "Make high-stakes product decisions under uncertainty, and be accountable for the outcomes" "Raise the product quality bar on the team and introduce practices others adopt, unblock teammates, and hold the line on craft" Check punctuation: some have capitalization inconsistencies but keep. Now Requirements list (YOU'LL HAVE): "5-10+ years of product management experience on consumer, developer, or enterprise products, ideally including 0-to-1 work at an early-stage company" "A track record of repeated, attributable impact, multiple projects across different roles or companies where you can quantify outcomes (revenue, engagement, efficiency) and the impact sustained after you moved on" "Product judgment, taste and autonomous ownership. You've identified opportunities, validated them with evidence, built buy-in, shipped, and the bet paid off. You’ve killed important projects in your career for the betterment of the product." "Clear, persuasive communication. You build buy-in across engineering, research, design, and leadership. You create clarity for others, not just yourself" "Technical depth to work directly with engineers and researchers" "Genuine conviction about AI evaluation and Arena's mission — you can articulate why this domain matters and where the product should go" "Comfort with ambiguity. We're a startup. Scope is fluid, context shifts, and you'll wear many hats" Now Skills (Bonus Points): "Production experience with AI/LLM systems — inference pipelines, evaluation workflows, model integration, or AI-powered product features" "Experience with developer- or enterprise-facing products, and fluency in consumption or usage-based revenue models" "Comfort working with real-world usage data and designing metrics beyond standard benchmarks, including experiments run with statistical rigor" "Experience growing a consumer or developer product at scale, with hands-on ownership of experimentation and analytics" "You've raised the bar on a team with measurable before/after — introduced practices, tools, or standards that others adopted" Now Benefits paragraph: "We offer competitive compensation and equity aligned to the markets where our team members are based. The base salary range will depend on the candidate’s permanent work location. Comprehensive health and wellness benefits, including medical, dental, vision, and additional support programs. The opportunity to work on cutting-edge AI with a small, mission-driven teamA culture that values transparency, trust, and community impact" Note there is a missing space before "A