Sr. Engineer, Storage

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. From posting: - "What You’ll Do" section: description of responsibilities. Should be under

Responsibilities

(or maybe "What You’ll Do" maps to Responsibilities). Use

• for list of duties. - "About The Role" paragraph: maybe also responsibilities? Actually "About The Role" includes bullet-like sentences. Could be part of responsibilities. We'll combine. - "Who You Are": qualifications/requirements. Could be Requirements or Qualifications. We'll put under

  Requirements

  (or Qualifications). The posting lists degree, years experience, hands-on experience, protocols, proficiency, etc. Also "Wondering if you’re a good fit?" etc. We'll include as list. - "Why CoreWeave?" includes culture description; maybe not needed as a section; but could be under Benefits? Not exactly. The instruction: include sections only when posting has real specific content. Benefits: they list benefits later: "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 "What We Offer" enumerates benefits. So we should have Benefits section with list. - Pay: they give base salary range $143,000 to $210,000. Also mention discretionary bonus, equity awards. So we can include Pay section with that info. - Schedule: not mentioned. So omit Schedule. - Skills: maybe we can extract skills from requirements: proficiency in Go, C, Rust; experience with storage protocols; familiarity with observability tools; cloud-native infra, Kubernetes. Could be a Skills section. But we already have Requirements covering many. To avoid duplication, we could put skills under Requirements or Qualifications. The instruction: prefer few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But they ask to use headings for those categories if content exists. We have content for Requirements (degree, experience). Also content for Skills (programming languages, tools). Could split but risk thin sections. However both are substantive. Let's include both Requirements and Skills. - About the role: we have "About The Role" paragraph and "What You’ll Do". Could be under About the role heading. But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading with prose describing role. Then Responsibilities heading with list of duties. However the posting already has "What You’ll Do" which is responsibilities. And "About The Role" is more description. We'll follow headings: About the role (prose), Responsibilities (list), Requirements (list), Skills (list), Benefits (list), Pay (prose). Omit Qualifications if we used Requirements; but we could also have Qualifications separate. To avoid thin, maybe combine Requirements and Qualifications into one heading? But they listed both as possible headings. We'll choose Requirements (includes degree, experience) and Skills (includes tech). That seems fine. Now need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we must not include sections like "California Applicants", "Export Control Compliance", "Equal Opportunity & Accommodations". Also remove "Learn more at www.coreweave.com." etc. We need to preserve all substantive information. So include the description about CoreWeave at start? That's introductory fluff but maybe not needed as a section. 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 intro paragraph about CoreWeave is not a heading; we could include as a short

  before sections? The instruction says output ONLY the HTML fragment. It didn't forbid introductory paragraph. But we should include substantive info: maybe we keep a brief

  about CoreWeave as context. However they said "Prefer a few substantive sections over many thin ones." The intro is not a section; could be a

  before first heading. Let's include a short paragraph summarizing CoreWeave. Now craft HTML:

  CoreWeave is The Essential Cloud for AI™, delivering a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence.

  Then sections:

  About the role

  Design and implement distributed storage solutions to support scaling data‑intensive AI workloads. Contribute to the development of exabyte‑scale, S3‑compatible object storage and integrate dedicated storage clusters into diverse customer environments. Work with technologies such as RDMA, GPU Direct Storage, and distributed filesystem protocols such as NFS or FUSE to optimize storage performance and efficiency. Lead efforts to improve the reliability, durability, security, and observability of our storage stack. Collaborate with operations teams to monitor, troubleshoot, and improve storage systems in production environments. Set the bar for developing metrics and dashboards to provide visibility into storage performance and health. Analyze telemetry and system data to drive improvements in throughput, latency, and resilience. Work cross‑functionally with platform, product, and infrastructure teams to deliver seamless storage capabilities across the stack. Share your knowledge and mentor other engineers on best practices in building distributed, high‑performance systems.

  That's basically the "About The Role" content turned into prose.

  Responsibilities

  • Design and implement distributed storage solutions to support scaling data‑intensive AI workloads.
  • Contribute to the development of exabyte‑scale, S3‑compatible object storage and integrate dedicated storage clusters into diverse customer environments.
  • Work with technologies such as RDMA, GPU Direct Storage, and distributed filesystem protocols such as NFS or FUSE to optimize storage performance and efficiency.
  • Lead efforts to improve the reliability, durability, security, and observability of our storage stack.
  • Collaborate with operations teams to monitor, troubleshoot, and improve storage systems in production environments.
  • Set the bar for developing metrics and dashboards to provide visibility into storage performance and health.
  • Analyze telemetry and system data to drive improvements in throughput, latency, and resilience.
  • Work cross‑functionally with platform, product, and infrastructure teams to deliver seamless storage capabilities across the stack.
  • Share your knowledge and mentor other engineers on best practices in building distributed, high‑performance systems.
  But note that this duplicates the About the role content. Might be redundant. However the instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we put both About the role and Responsibilities with same content, we are duplicating. Better to split: About the role could be a brief summary, Responsibilities list the duties. The About the role paragraph we wrote is essentially the same as responsibilities. Could we make About the role a short description: "The Storage Engine Team builds reliable, scalable storage solutions for AI workloads." Then Responsibilities list the detailed duties. Let's check original: "About The Role Design and Implement distributed storage solutions to support scaling data intensive AI workloads.Contribute to the development of exabyte-scale, S3-compatible object storage and integrate dedicated storage clusters into diverse customer environments.Work with technologies such as RDMA, GPU Direct Storage, and distributed filesystems protocols such as NFS or FUSE to optimize storage performance and efficiency.Lead efforts to improve the reliability, durability, security, and observability of our storage stack.Collaborate with operations teams to monitor, troubleshoot, and improve storage systems in production environments.Set the bar for developing metrics and dashboards to provide visibility into storage performance and health.Analyze telemetry and system data to drive improvements in throughput, latency, and resilience.Work cross-functionally with platform, product, and infrastructure teams to deliver seamless storage capabilities across the stack.Share your knowledge and mentor other engineers on best practices in building distributed, high-performance systems." That is essentially a list of responsibilities. So we could treat that as Responsibilities section, and About the role could be a brief overview: maybe the first sentence "The Storage Engine Team at CoreWeave is responsible for the product capabilities and data plane function of CoreWeave’s managed storage products. We build reliable, scalable storage solutions with segment leading performance." That's from earlier "What You’ll Do" paragraph? Actually earlier: "What You’ll Do The Storage Engine Team at CoreWeave is responsible for the product capabilities and data plane function of CoreWeave’s managed storage products. We build reliable, scalable storage solutions with segment leading performance. Storage engine works with engineering teams across infrastructure, compute, and platform to ensure our storage services meet the needs of the world’s most demanding AI workloads." That could be About the role. Then Responsibilities list the detailed items from "About The Role". Let's do that. Thus:

  About the role

  The Storage Engine Team at CoreWeave is responsible for the product capabilities and data plane function of CoreWeave’s managed storage products. We build reliable, scalable storage solutions with segment‑leading performance and work with engineering teams across infrastructure, compute, and platform to ensure our storage services meet the needs of the world’s most demanding AI workloads.

  Responsibilities

  • Design and implement distributed storage solutions to support scaling data‑intensive AI workloads.
  • Contribute to the development of exabyte‑scale, S3‑compatible object storage and integrate dedicated storage clusters into diverse customer environments.
  • Work with technologies such as RDMA, GPU Direct Storage, and distributed filesystem protocols such as NFS or FUSE to optimize storage performance and efficiency.
  • Lead efforts to improve the reliability, durability, security, and observability of our storage stack.
  • Collaborate with operations teams to monitor, troubleshoot, and improve storage systems in production environments.
  • Set the bar for developing metrics and dashboards to provide visibility into storage performance and health.
  • Analyze telemetry and system data to drive improvements in throughput, latency, and resilience.
  • Work cross‑functionally with platform, product, and infrastructure teams to deliver seamless storage capabilities across the stack.
  • Share your knowledge and mentor other engineers on best practices in building distributed, high‑performance systems.
  Now Requirements: from "Who You Are" bullet list. We'll create

  Requirements

  with list. Items: - Bachelor’s, Master’s, or PhD degree in Computer Science, Engineering, or a related field. - 8–10+ years of experience working in storage systems engineering or infrastructure. - Strong hands‑on experience with object storage or distributed filesystems in production environments. - Experience with one or more storage protocols (e.g. S3, NFS) and file systems such as Ceph, DAOS, or similar. - Proficiency in a systems programming language such as Go, C, or Rust. - Proficiency leveraging AI tools to augment software development. - Familiarity with storage observability tools and telemetry pipelines (e.g., ClickHouse, Prometheus, Grafana). - Experience working with cloud‑native infrastructure, Kubernetes, and scalable system architectures. Also "Wondering if you’re a good fit?" paragraph includes qualities; could be part of Requirements or separate. Might be considered "Qualifications". But we can incorporate as list items under Requirements as well (they are qualities). However to avoid too many items, we could add a separate

  Qualifications

  for those qualities. But the instruction: prefer few substantive sections over many thin ones. The qualities are somewhat similar to requirements; we could merge them into Requirements as additional bullet points. Let's add: - Love to grow and push the boundaries of your expertise.