Senior Systems Engineer, Enterprise AI Platforms

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: About The Role (description), What You'll Do (responsibilities), Who You Are (requirements/qualifications/skills), Preferred (maybe skills), Why CoreWeave? (maybe benefits?), The base salary range (Pay), benefits list (Benefits). Also maybe "What success looks like in the first year" could be part of responsibilities. We need to avoid boilerplate like EEO, legal, etc. Also remove duplicated lines. Must preserve all substantive info. We need to decide sections: - About the role: we have "About The Role" paragraph(s). Could combine with "What success looks like..." maybe part of responsibilities. - Responsibilities: "What You'll Do" bullet list (though it's prose). Also "AI platform lifecycle and governance", "Guardrails as enforceable controls", "Infrastructure you'll own", "Operations, reliability, and telemetry". Those are responsibilities. - Requirements/Qualifications/Skills: "Who You Are" (6+ years etc), plus "Preferred" (real-world experience etc). Could combine into Qualifications and Skills. - Pay: base salary range $182,000 to $242,000. - Benefits: list of benefits (medical, dental, vision, etc). Also maybe "Why CoreWeave?" includes culture but not benefits; we can treat as maybe not needed. We must not include sections with placeholder like "commensurate with experience". We have actual numbers. We must not repeat job title as heading. No Job ID. We must output only HTML fragment, no /, no markdown fences. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive information; not invent or summarize away detail. So we need to include details like specifics of responsibilities, etc. We must be careful to not include boilerplate like "CoreWeave is The Essential Cloud for AI™..." maybe that's introductory fluff but could be considered part of About the role? It's generic company description; maybe we can include as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." Could combine company overview into About the role? But they said "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can have an About the role section that includes the company description and role description. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the long legal EEO paragraph at end, also the "Wondering if you're a good fit?" maybe that's not boilerplate but could be considered part of Who You Are? It's more like a call to action; maybe we can keep as part of Who You Are? It's not boilerplate but it's somewhat promotional. Might be okay to keep as part of Who You Are? But it's not a requirement; it's more like "you may be a great fit if..." Could be considered part of Qualifications? Might be okay to keep as part of Who You Are (maybe as a paragraph). However it's somewhat fluff; but we need to preserve ALL substantive information; does that include promotional "you may be a great fit if..."? It's substantive? It's more like encouragement; but we could keep it as part of Who You Are. We also need to remove duplicated lines: there may be repeated sentences like "The base salary range for this role is $182,000 to $242,000." and later "The range we’ve posted represents the typical compensation range for this role." We need to keep both? They are somewhat duplicated but not identical; we need to preserve ALL substantive information; but we should avoid duplication? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to detect duplicates and keep only one instance. The two salary statements are similar but not exact duplicates; but they convey same info. Might be considered duplicated? Safer to keep only one concise statement: maybe keep the first one and drop the later repetitive. Also the benefits list appears twice? There's "In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility)." Then later "What We Offer The range we’ve posted represents the typical compensation range for this role.... In addition to a competitive salary, we offer a variety of benefits to support your needs. The benefits below reflect our US-based offerings for full-time employees; for roles in other locations, benefits vary and are shared during the hiring process. These include: ..." So we need to keep the benefits list but maybe combine. We need to output only HTML fragment. Let's extract substantive content: Company description: "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." That's generic but maybe part of About the role. About The Role: paragraphs after "About The Role". Let's capture: "CoreWeave is hiring a Senior AI Platform Engineer to own the design, implementation, and governance of AI across CoreWeave's employee environment. You'll be the technical owner for the AI tools our employees use every day, on every surface they ship on: chat assistants, desktop apps, coding agents, AI terminals, AI browsers, workplace knowledge tools, and whatever comes next. You'll make them safe to adopt by building CoreWeave's guardrails directly into the platform through identity, device, and tenant-level controls rather than policy documents alone. This role is for someone who is genuinely passionate about AI and lives on its bleeding edge: someone who is already tuning agent behavior every week, has run swarms of agents and agent loops rather than just chatted with a model, and wants to keep learning at the velocity this field now moves. The tools, models, and best practices in this job will change monthly. That should excite you, not exhaust you. This is not a traditional AI/ML engineering role, and it is not a traditional IT administration role. It is deliberately a composite role that combines three things: production software and SRE engineering, hands-on LLM and agent work, and enterprise IT controls across identity, devices, and SaaS. We expect strong candidates to arrive deep in two of the three and grow into the third. Tell us which two." Then "What success looks like in the first year: ..." We'll treat as part of responsibilities. Responsibilities sections: - "What You'll Do": paragraph: "IT Engineering at CoreWeave designs, builds, and operates the systems that enable our employees and acquired organizations to work securely and efficiently at scale. The team partners closely with Security, Business Development, PeopleOps, and Corporate functions to deliver resilient, standardized, and automation-first IT solutions that support CoreWeave's rapid growth." Then after About The Role, there is "What success looks like in the first year:" with bullet-like sentences: "CoreWeave employees get frontier AI capabilities before almost any enterprise on earth. When a vendor ships a new model, agent surface, or feature, you already know it's coming; you're plugged into vendor roadmaps, betas, and the community and you have an evaluated, governed rollout ready in days, not quarters. That speed is possible because of the foundation you build in year one: sanctioned tools governed through identity, a connector and MCP allowlist in production, an intake process so "is this allowed" has an answer, internal agents shipping through an IT-owned gateway, and leadership visibility into usage, cost, and risk. The foundation is the floor; the pace is the job." Then there are headings: "AI platform lifecycle and governance", "Guardrails as enforceable controls", "Infrastructure you'll own", "Operations, reliability, and telemetry". Each with bullet-like paragraphs. We need to turn these into

  • lists. The content under each heading is prose; we can split into list items per sentence or keep as

    ? The instruction: Use

    • for any list of duties/requirements/benefits. So we need to make lists for duties (responsibilities). So we can create a
      with
      • items each representing a duty. Could group under headings? But we need headings

        for sections. So we can have

        Responsibilities

        then a
        with
        • items covering all duties. Or we could have multiple

          subsections? The instruction says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those specific headings. So we should not create additional headings like "AI platform lifecycle and governance". Instead we should incorporate those details into the Responsibilities section as list items. Thus we need to extract all duty statements and put them as

          under Responsibilities. Similarly, Requirements/Qualifications/Skills: we need to decide which heading(s) to use. We have "Who You Are" (requirements) and "Preferred" (preferred qualifications). Could combine into Requirements and maybe Skills. But we have headings: Requirements, Qualifications, Skills. We could put mandatory requirements under Requirements, preferred under Qualifications, and skills under Skills. Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine into one section "Requirements" that includes both mandatory and preferred? But we have separate headings available; we could use Requirements for mandatory, Qualifications for preferred, Skills for technical skills. That's three sections but maybe okay if each has substantive content. However we need to avoid thin sections. Let's see if each has enough content. Mandatory requirements (Who You Are): includes 6+ years experience, 2+ years hands-on LLM, strong software engineering skills in Python/Go/Rust/TS, experience operating services in production, working understanding of enterprise IT control systems, ability to produce clear technical documentation and lead initiatives. That's substantive. Preferred: includes real-world experience administering identity, endpoint management, SaaS platforms; experience deploying and governing enterprise AI tools across 1k+ org; hands-on experience building custom MCP servers, authoring reusable agent skills; working knowledge of data governance for AI; experience self-hosting and serving models; familiarity with compliance frameworks; etc. That's also substantive. Skills: maybe we could list specific technical skills: Python, Go, Rust, TypeScript, containers, IaC, CI/CD, secrets management, observability, Terraform, Okta, Google Workspace, etc. But those are already in the sections. Could create a Skills section summarizing. But to avoid many thin sections, maybe we combine Requirements and Qualifications into one "Requirements" section, and Skills into another? Or combine all into one "Requirements". The instruction says prefer a few substantive sections over many thin ones. So maybe we have three sections: About the role, Responsibilities, Requirements (including qualifications and skills), Pay, Benefits. That's five sections. We need to include Pay and Benefits sections only if posting actually states them. It does. We need to not include Schedule section because not mentioned. Thus final sections: About the role, Responsibilities, Requirements, Pay, Benefits. Now we need to craft HTML. We'll start with