Recruiting Coordinator (Founding Talent Operations)

We need to output HTML fragment with sections: About the role (already present), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO etc. Must preserve all substantive info. We need to parse the posting. Content: - About Arena Intelligence (company description) – not needed as heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections: About the role (maybe we keep as heading? The posting includes "About The Role". We'll use

About the role

then prose. - Responsibilities: list of duties: Orchestrate High-Stakes Logistics, Deliver an Elite Candidate Experience, Interface with Executive Leadership, Build Founding Talent Operations, High-Agency Problem Solving, Maintain Operational Rigor, plus bullet points under "You’ll have Unapologetically High-Agency", "Executive Presence & Crisp Communication", "Systems & Operations Minded", "Obsessed with Detail & Precision". Those are more like qualities/skills but could be responsibilities. We'll treat them as responsibilities. - Requirements: "1–3+ years of experience in recruiting coordination, executive administration, or talent operations within a fast-paced technology company, high-growth startup, or top-tier search firm." Also "Tech-Savvy: Highly proficient in modern tool stacks (e.g., Ashby / Greenhouse, Google Workspace, Slack, Notion, Prelude)." Also maybe "Bonus Points If You:" items are not required but could be qualifications/skills. We'll treat them as Qualifications or Skills. - Qualifications: maybe the bonus points: prior experience at early-stage startup, keen interest in AI/ML, experience building interview rubrics, onboarding workflows, talent analytics dashboards. - Skills: maybe list of tools: Ashby/Greenhouse, Google Workspace, Slack, Notion, Prelude, plus communication, detail-oriented, etc. - 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". Also maybe "Come help build the space where anyone can explore and help shape the future of AI." That's more about mission. - Pay: The posting mentions base salary range depends on location, competitive compensation and equity. No specific numbers. Since we should not create Pay section unless posting actually states them. It does mention compensation and equity, but not specific numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation and equity, and benefits. So we can include Pay (maybe as "Compensation") but heading must be Pay per instruction. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use Pay heading if we have pay info. We have "competitive compensation and equity". That's pay info albeit not specific. It's still stating compensation. So we can include Pay section with that prose. - Benefits: we have comprehensive health and wellness benefits, etc. So include Benefits. - Schedule: The posting says "This role is based in San Francisco and is in-office." Also "Interviews and on-sites happen here, and you will be the person making them run." No explicit schedule like full-time, hours. It mentions in-office but not schedule details. Should we include Schedule? It does not state schedule like "Full-time", "40 hrs/week". Might be considered schedule info? The instruction: never create Schedule section unless posting actually states them. It does not explicitly state schedule (like hours). It says based in San Francisco and is in-office. That's location, not schedule. So we should NOT include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We must not repeat job title. Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details like "Own end-to-end interview coordination across complex, multi-stage pipelines (technical challenges, deep-dive research panels, founder/executive interviews, and debriefs) with absolute precision." etc. We need to avoid boilerplate like EEO etc. Remove that. Let's extract content. About Arena Intelligence: maybe we can include as part of About the role? But the instruction says About the role heading. Could include company description as part of About the role? Usually About the role includes role description. But we have separate "About Arena Intelligence" paragraph. Could we include it under About the role? Might be okay but risk of missing content. However we could create a separate section like "About the company" but not allowed headings list. The instruction only gives examples but not strict limited to those headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. So we should only use those headings. So we need to fit company description somewhere, maybe under About the role as introductory prose. That seems acceptable. Thus About the role section will contain both company description and role description. Now Responsibilities: list items. Let's list responsibilities from text: - Orchestrate High-Stakes Logistics: Own end-to-end interview coordination across complex, multi-stage pipelines (technical challenges, deep-dive research panels, founder/executive interviews, and debriefs) with absolute precision. - Deliver an Elite Candidate Experience: Serve as the primary, high-touch liaison for candidates. Ensure world-class researchers and engineers experience a seamless, transparent, and memorable interview process. - Interface with Executive Leadership: Partner directly with Arena’s founders and executive team to optimize their hiring bandwidth, protect their calendars, and hold hiring teams accountable to rapid feedback loops. - Build Founding Talent Operations: Help design, automate, and scale our talent tech stack (e.g., ATS workflows in Ashby/Greenhouse, scheduling automation, candidate communications, and pipeline analytics). - High-Agency Problem Solving: Intervene in real-time when schedules break or urgent priorities collide. Operate with sound judgment, finding immediate solutions without waiting for step-by-step instructions. - Maintain Operational Rigor: Champion data integrity across all recruiting systems, tracking key pipeline metrics (conversion rates, time-to-schedule, candidate velocity) to uncover bottlenecks. - You’ll have Unapologetically High-Agency: You don't wait for playbooks; you write them. You take extreme ownership of outcomes and proactively solve problems before they escalate. - Executive Presence & Crisp Communication: You write and communicate clearly, concisely, and with high polish. You are comfortable challenging and aligning senior leaders to keep hiring velocity high. - Systems & Operations Minded: You see scheduling not just as a set of calendar invites, but as a workflow optimization problem. You look for ways to eliminate friction and automate manual steps. - Obsessed with Detail & Precision: You have an allergic reaction to typos, mismatched time zones, broken links, and dropped handoffs. These could be responsibilities or qualities. We'll put them under Responsibilities as list items. Now Requirements: "1–3+ years of experience in recruiting coordination, executive administration, or talent operations within a fast-paced technology company, high-growth startup, or top-tier search firm." Also "Tech-Savvy: Highly proficient in modern tool stacks (e.g., Ashby / Greenhouse, Google Workspace, Slack, Notion, Prelude)." That's a requirement. We could also include "based in San Francisco and is in-office" as requirement? It's location, maybe schedule? Not needed. We'll put these as list items. Qualifications: Bonus points items: - Have prior experience at an early-stage / Series A–B venture-backed startup. - Have a keen interest in Artificial Intelligence, Machine Learning, and enterprise autonomy. - Have experience building or iterating on interview rubrics, onboarding workflows, or talent analytics dashboards. We'll list as qualifications. Skills: Could be derived from tech-savvy and other abilities: proficiency in Ashby/Greenhouse, Google Workspace, Slack, Notion, Prelude; strong communication; detail-oriented; systems thinking; etc. But we might avoid duplication. Perhaps we can put skills as list of tools and competencies: "Proficiency in Ashby/Greenhouse, Google Workspace, Slack, Notion, Prelude; strong written and verbal communication; detail-oriented; systems thinking; ability to prioritize and execute." However we must not invent details not in posting. The posting mentions "Tech-Savvy: Highly proficient in modern tool stacks (e.g., Ashby / Greenhouse, Google Workspace, Slack, Notion, Prelude)." Also mentions "Executive Presence & Crisp Communication", "Systems & Operations Minded", "Obsessed with Detail & Precision". Those are skills/competencies. So we can list them as skills. Thus Skills list: Proficiency in Ashby/Greenhouse, Google Workspace, Slack, Notion, Prelude; Executive presence and crisp communication; Systems and operations mindset; Obsessed with detail and precision. Now 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". Also maybe "Come help build the space where anyone can explore and help shape the future of AI." That's more mission. We'll put benefits as list items? Could be prose. We'll use

  • for list of benefits. Thus Benefits list: - Competitive compensation and equity aligned to market (base salary range depends on permanent work location) - Comprehensive health and wellness benefits (medical, dental, vision, additional support programs) - Opportunity to work on cutting-edge AI with a small, mission-driven team - Culture that values transparency, trust, and community impact - Chance to help build the space where anyone can explore and help shape the future of AI Now Pay: The posting mentions compensation and equity already; but we already put compensation in Benefits. However Pay section should be separate if we have pay info. The instruction says use Pay heading for compensation details. We could move compensation details to Pay section and keep Benefits for health etc. Let's do that. Pay section: "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." Benefits section: health benefits, opportunity to work on cutting-edge AI, culture values, chance to help build space. Now we must not repeat content. Ensure we don't duplicate. Now we need to output HTML fragment only. Let's craft.

    About the role

    ...

    We need to include company description: "Arena Intelligence Arena is the platform for evaluating how AI models perform in the real world. Founded by researchers from UC Berkeley's SkyLab, we're on a mission to measure and advance the frontier of AI for real-world use, and to build the foundation for everyone to understand, shape, and benefit from it. Tens of millions of people use Arena each month to evaluate how frontier systems handle the work they actually do. The preferences they share power the most transparent, rigorous, and human-centered evaluations in AI. Leading AI labs, enterprises, and independent researchers rely on our work and open datasets to understand how models