Manager, Field Engineering

We need to output HTML fragment with sections: About the role? Actually the posting includes "What You’ll Do" (responsibilities) and "Who You Are" (requirements/qualifications). Also "What We Offer" (benefits). Also base salary range. Also maybe "Pay" section. Also schedule? Not present. So we include sections: Responsibilities (What You’ll Do), Requirements (Who You Are), Benefits (What We Offer), Pay (base salary range). Possibly also "About the role" not present; we can skip. Must not repeat job title. Must not include boilerplate like EEO, export control, etc. Also remove duplicated lines. We need to preserve all substantive info. So we need to capture responsibilities bullet list from "What You’ll Do". Let's extract bullet points: - Evolve the operating model for Physical AI Field Engineering within your region, from opportunity qualification and problem framing through data exploration, model development, deployment, adoption, and expansion. - Lead, coach, and develop a high-performing team of Specialist Field Engineers, Forward Deployed Data Scientists, and Forward Deployed Engineers, including hiring, workforce planning, career development, performance management, and succession planning. - Set the technical and delivery bar for customer engagements, ensuring that teams build solutions that are grounded in engineering criteria, validated against physical constraints, and deployed into workflows where they create measurable value. - Partner directly with strategic customers and senior stakeholders across automotive, robotics, aerospace, and industrial engineering to understand their priorities, shape technical strategy, and maintain executive confidence throughout delivery. - Work closely with Account Executives, Account Managers, Account Solutions Architects, Technical Solutions Managers, Product, Engineering, and Platform teams to qualify opportunities, allocate specialist capacity, and create a consistent customer experience. - Build mechanisms that make the team more effective at scale, including reusable engagement patterns, delivery standards, onboarding, enablement, technical reviews, and knowledge-sharing practices. - Establish a disciplined field-to-product feedback loop: identify recurring customer needs, distinguish reusable product opportunities from one-off delivery work, and translate field evidence into actionable recommendations for Product and Engineering. - Own the operating metrics that show whether the model is working, including customer value, time to deployment, software adoption, delivery quality, team capacity, expansion, and infrastructure or SaaS opportunities created through engagements. - Represent Physical AI Field Engineering internally and externally, helping CoreWeave explain how domain expertise, applied AI, and the CoreWeave platform combine to solve difficult engineering problems. Now "Who You Are": list of qualifications: - Bachelor’s or Master’s degree in Computer Science, Engineering, Physics, Mathematics, or a related technical discipline, or equivalent practical experience. - 10+ years of experience in technical consulting, field engineering, product engineering, applied AI, or a related customer-facing engineering discipline. - 5+ years of experience leading and developing technical teams in a fast-moving environment, with a track record of hiring strong people, setting a clear bar, and creating an environment where specialists can do their best work. - Sufficient technical depth in AI/ML applied to physical systems or engineering workflows to engage credibly with ML engineers, data scientists, controls engineers, simulation specialists, and engineering leaders, and to make sound judgments about data, modeling, validation, and deployment trade-offs. - Experience partnering across Product, Engineering, Sales, Marketing, and Field Engineering to align priorities and move work from customer signal to delivered capability. - Excellent written and verbal communication skills with the ability to clearly articulate complex technical topics to technical, executive, and customer audiences. - Preferred Experience in automotive, robotics, aerospace and defense, industrial, manufacturing, or another engineering-intensive industry. - Experience delivering or supporting AI solutions in embedded, on-site, production, or safety-critical environments. - Familiarity with modern ML platforms and workflows spanning experimentation, model management, data exploration, application development, and cloud deployment. - Capable of owning capacity models, hiring plans, creating technical career frameworks, delivery KPIs, or portfolio-level planning across multiple customer engagements. - Track record of converting repeated customer problems into reusable software, product capabilities, or standardized delivery patterns. Also there is a paragraph about "Wondering if you’re a good fit?" but that's more fluff; we can include as part of Requirements? Might be considered "Preferred Experience" but it's more about qualities. We could include as part of Requirements or maybe a separate "Qualifications" section. The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings. We have responsibilities, requirements/qualifications, benefits, pay. Could combine requirements and qualifications into one section "Requirements". Or separate "Requirements" and "Qualifications". Since we have both required and preferred, we could put required under Requirements and preferred under Qualifications. But we need to avoid filler. The "Wondering if you’re a good fit?" paragraph is more fluff but still substantive? It describes qualities; we could include under Qualifications as bullet list. However the instruction: Prefer a few substantive sections over many thin ones. Might combine into Requirements. We also have "What We Offer" benefits list. Need to capture bullet list: - Medical, dental, and vision insurance - 100% paid for by CoreWeave - Company-paid Life Insurance - Voluntary supplemental life insurance - Short and long-term disability insurance - Flexible Spending Account - Health Savings Account - Tuition Reimbursement - Ability to Participate in Employee Stock Purchase Program (ESPP) - Mental Wellness Benefits through Spring Health - Family-Forming support provided by Carrot - Paid Parental Leave - Flexible, full-service childcare support with Kinside - 401(k) with a generous employer match - Flexible PTO - Catered lunch each day in our office and data center locations - A casual work environment - A work culture focused on innovative disruption Also note: "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." That's substantive; we can include as a paragraph before list. Pay: base salary range $157,000 to $231,000. Also note: "The starting salary will be determined based on job-related knowledge, skills, experience, and market location. We strive for both market alignment and internal equity when determining compensation. In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility)." Also later: "The range we’ve posted represents the typical compensation range for this role. To determine actual compensation, we review the market rate for each candidate which can include a variety of factors. These include qualifications, experience, interview performance, and location. In addition to a competitive salary, we offer a variety of benefits to support your needs." This is somewhat repetitive; we can summarize but must preserve all substantive info, not invent or summarize away detail. We need to keep the details but can combine into a paragraph. However we must not create filler like "commensurate with experience". The text includes specifics: base salary range, starting salary determined based on job-related knowledge, skills, experience, market location; market alignment and internal equity; total rewards includes discretionary bonus, equity awards, comprehensive benefits program. Also later: range posted typical compensation range; actual compensation determined reviewing market rate for each candidate includes qualifications, experience, interview performance, location. In addition to competitive salary, we offer variety of benefits. This is somewhat repetitive but we need to preserve all substantive info; we can combine but must not lose any detail. Could produce a paragraph that includes all points: base salary range $157,000-$231,000; starting salary based on job-related knowledge, skills, experience, market location; we strive for market alignment and internal equity; total rewards includes discretionary bonus, equity awards, comprehensive benefits program; actual compensation determined by reviewing market rate for each candidate, considering qualifications, experience, interview performance, location; in addition to competitive salary, we offer variety of benefits (as listed). That seems to preserve. Now schedule: not present, so omit. Now produce HTML: Use

for each section heading. Use

• for lists. Use

  for prose. We need sections: Responsibilities, Requirements, Benefits, Pay. Possibly also "About the role" not present. We'll not include empty sections. Let's craft. First, maybe a short intro paragraph about the role? The posting starts with description of CoreWeave; but that's boilerplate? It's about company; could be considered "About the role"? Actually it's about company overview; could be considered "About the role" but it's not specific to role. 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. The company overview might be considered minor metadata? It's not about the role; but it's descriptive. Might be okay to include as a paragraph before sections? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview is not boilerplate; it's substantive about CoreWeave. Could include as a short

  before sections. However the instruction about headings: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have an "About the role" heading with that company overview paragraph. But the company overview is not exactly about the role; but it's about the company. Might still fit under "About the role". However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we can include a brief paragraph under "About the role". Let's do that. Thus sections: About the role (company overview), Responsibilities, Requirements, Benefits, Pay. Now ensure we don't include boilerplate like EEO, export control, California Applicants, etc. Remove those. Now produce HTML. Let's draft:

  About the role

  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.

  Responsibilities

  • Evolve the operating model for Physical AI Field Engineering within your region, from opportunity qualification and problem framing through data exploration, model development, deployment, adoption, and expansion.
  • Lead, coach, and develop a high-performing team of Specialist Field Engineers, Forward Deployed Data Scientists, and Forward Deployed Engineers, including hiring, workforce planning, career development, performance management, and succession planning.
  • Set the technical and delivery bar for customer engagements, ensuring that teams build solutions that are grounded in engineering criteria, validated against physical constraints, and deployed into workflows where they create measurable value.
  • Partner directly with strategic customers and senior stakeholders across automotive, robotics, aerospace, and industrial engineering to understand their priorities, shape technical strategy, and maintain executive confidence throughout delivery.
  • Work closely with Account Executives, Account Managers, Account Solutions Architects, Technical Solutions Managers, Product, Engineering, and Platform teams to qualify opportunities, allocate specialist capacity, and create a consistent customer experience.
  • Build mechanisms that make the team more effective at scale, including reusable engagement patterns, delivery standards, onboarding, enablement, technical reviews, and knowledge-sharing practices.
  • Establish a disciplined field-to-product feedback loop: