People Operations Specialist

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. 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. Must not include sections with filler like "commensurate with experience". Pay: we have base salary range $108,000 to $143,000. So include Pay section. Benefits: we have list of benefits. Include Benefits section. Schedule: not mentioned; no schedule info, so omit. About The Role: we have description under "About The Role". That's a heading. Should we use

About The Role

then content. Responsibilities: we have "What You’ll Do" and bullet points under Employee lifecycle operations, Employee support and case management, Global mobility support, Compliance and documentation, Process, systems, and reporting. Those are responsibilities. So we can put under

Responsibilities

with

• each bullet. Requirements: we have "Who you are" bullet list of required qualifications. That's requirements. Qualifications: maybe we separate? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where. Likely "Who you are" is Requirements. Preferred exposure etc could be Qualifications or Skills. The "Preferred" list could be Qualifications. Skills maybe not explicit; we could combine. But we should not create empty sections. So we need to map content. We have: - About The Role: paragraph describing role. - Responsibilities: multiple sub-sections: Employee lifecycle operations, Employee support and case management, Global mobility support, Compliance and documentation, Process, systems, and reporting. Each has bullet points. - Who you are: required experience list (3+ years experience, etc). That's Requirements. - Preferred Exposure to immigration..., Experience supporting employees across more than one region..., Experience in a high-growth..., Familiarity with Workday..., Experience documenting processes... That could be Qualifications. - Skills: maybe not explicit; we could omit Skills section if no explicit skills list. However we have "Clear written and verbal communication skills", "Ability to follow established processes", "Sound judgment", "Comfort working across multiple systems". Those are skills but they are within Who you are. Could treat as Skills section. But we need to avoid duplication. Perhaps better: Requirements = mandatory experience; Qualifications = preferred; Skills = communication, judgment, etc. But we have to avoid filler. Let's extract. From "Who you are": - 3+ years of experience in People Operations, HR operations, HR coordination, shared services, or a closely related discipline. - Hands-on experience executing employee lifecycle transactions in an HRIS, ideally Workday. - Strong attention to detail and demonstrated accuracy when handling high-volume, deadline-driven work. - Experience supporting employees directly through a ticketing system, shared inbox, or comparable support model. - Ability to follow established processes consistently while recognizing when a situation needs to be escalated. - Sound judgment handling confidential and sensitive employee data. - Clear written and verbal communication skills, including the ability to explain process steps to employees plainly. - Comfort working across multiple systems, time zones, and cross-functional partners. These could be Requirements (mandatory) and also Skills. But we need separate sections. Perhaps we put all under Requirements, and skip Qualifications and Skills if they'd be redundant. However we have Preferred list that is distinct. So we can put Requirements = mandatory, Qualifications = preferred, Skills = maybe not needed. But we could still include Skills if we extract communication etc from Who you are, but that would duplicate. Better to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should attempt to fill each if we have content. Let's see: - About the role: we have content. - Responsibilities: we have content. - Requirements: we have mandatory experience list. - Qualifications: we have preferred exposure list. - Skills: we could list specific skills like "Attention to detail", "Communication", "Judgment", "Systems comfort". But those are already in Requirements. However we could still make a Skills section summarizing those. But risk of duplication. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay as long as we preserve info. But we should avoid creating sections with filler like "not specified". If we create Skills section, we need to put actual skill statements. We can extract from Who you are: Strong attention to detail, Clear written and verbal communication skills, Sound judgment handling confidential data, Comfort working across multiple systems, time zones, cross-functional partners. Also Ability to follow established processes consistently while recognizing when a situation needs to be escalated. That's more procedural. Could be considered skill. Thus we can create Skills section with those bullet points. - Benefits: we have list. - Pay: we have base salary range. - Schedule: no info, so omit. Now we need to format. We must not include boilerplate like EEO, legal, etc. Also remove "Wondering if you’re a good fit?" etc. Also remove "Why CoreWeave?" etc? Actually "Why CoreWeave?" includes culture description; that's substantive? Might be considered boilerplate but it's about company values. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why CoreWeave?" section is not explicitly listed as boilerplate, but it's more marketing. However it's still substantive about culture. Might be okay to keep? The instruction says "Prefer a few substantive sections over many thin ones." Could include as part of About the role? But we already have About The Role heading from the posting. The "Why CoreWeave?" could be considered part of About the role? However the posting already has "About The Role" heading earlier. The "Why CoreWeave?" is separate. It might be considered fluff but still substantive. Safer to include? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's clearly boilerplate like EEO. "Why CoreWeave?" is not boilerplate; it's about culture. So we could include it under About the role? But we already have About The Role heading with content from earlier. We could merge? But we must not invent headings. We could add another section like "About CoreWeave" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. So we should not add extra headings beyond those. Therefore we should incorporate the "Why CoreWeave?" content into About the role section (since it's about the role/company). That would preserve info. Thus About the role section will combine the initial paragraph about CoreWeave (the first paragraph) plus the "Why CoreWeave?" paragraph(s) about culture, values, etc. Now we need to format. Let's extract content. First paragraph: "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com." Then "What You’ll Do" heading but we will not repeat as heading; we will put under Responsibilities. Under Responsibilities we have bullet groups: Employee lifecycle operations: - Execute onboarding, offboarding, transfers, promotions, and other lifecycle transactions accurately and on schedule. - Process Workday changes including job data, compensation, org structure, and employment status, maintaining data integrity across systems. - Prepare and distribute employment documentation such as offer amendments, letters, verifications, and change notices. - Coordinate with IT, Facilities, Payroll, and Benefits to ensure start-date and departure readiness. Employee support and case management: - Serve as a first-line responder for employee and manager questions, resolving routine cases and escalating complex or sensitive matters to the appropriate partner. - Manage the People Operations ticket queue, tracking volume, aging, and resolution against agreed service levels. - Maintain and improve employee-facing documentation, FAQs, and knowledge base content. - Communicate clearly and empathetically with employees navigating process changes or time-sensitive requests. Global mobility support: - Support the Senior Global Mobility Partner with immigration and relocation case coordination, including intake, document collection, status tracking, and routine employee updates. - Maintain global mobility trackers and case records so status, deadlines, and next steps are always current and audit-ready. - Coordinate logistics with immigration counsel and relocation vendors, following established workflows and escalating exceptions rather than making independent determinations. - Assist with right-to-work verification, start-date readiness checks, and relocation payroll handoffs under defined guidance. - Escalate immigration, cross-border, and compliance judgment calls to the Senior Global Mobility Partner or Legal. Compliance and documentation: - Maintain accurate, complete employee records and mobility files in line with retention and privacy requirements. - Support audits, compliance reviews, and periodic data checks by preparing records and reconciling discrepancies. - Follow established controls for handling confidential and sensitive employee data. - Track upcoming compliance milestones and deadlines, surfacing risks to the appropriate owner in advance. Process, systems, and reporting: - Execute and document repeatable workflows across Workday, Greenhouse, Asana, and case-management and vendor platforms. - Produce recurring reports and dashboards on case volume, cycle time, ticket resolution, and open items. - Identify friction, manual steps, and recurring errors in existing processes, and propose practical improvements to the process owner. - Keep standard operating procedures current as tools, policies, and workflows change. Now Requirements (Who you are mandatory): - 3+ years of experience in People Operations, HR operations, HR coordination, shared services, or a closely related discipline. - Hands-on experience executing employee lifecycle transactions in an HRIS, ideally Workday. - Strong attention to detail and demonstrated accuracy when handling high-volume, deadline-driven work. - Experience supporting employees directly through a ticketing system, shared inbox, or comparable support model. - Ability to follow established processes consistently while recognizing when a situation needs to be escalated. - Sound judgment handling confidential and sensitive employee data. - Clear written and verbal communication skills, including the ability to explain process steps to employees plainly. - Comfort working across multiple systems, time zones, and cross-functional partners. Now Qualifications (Preferred): - Exposure to immigration, relocation, or global mobility processes in a coordination or administrative capacity. - Experience supporting employees across more than one region, such as the US, EMEA, or APAC. - Experience in a high-growth technology, infrastructure, or multinational organization. - Familiarity with Workday, Greenhouse, Asana, Fragomen Connect, or comparable HR and immigration systems. - Experience documenting processes or building knowledge base content. Now Skills: we could extract from Who you are but we already used those for Requirements. However we could still make a Skills section with items like: - Attention to detail - Accuracy in high-volume work - Ticketing system support - Process adherence and escalation judgment - Confidential data handling - Written and verbal communication - Multi-system, multi-timezone collaboration But that duplicates. However the instruction says preserve ALL substantive information; duplication is not prohibited. It says do NOT invent or summarize away detail. Duplication preserves detail. So we could include Skills section with those bullet points, but we must ensure we don't miss any. However we risk making the output longer but still okay. Alternatively we