Staff Engineer, Storage
for each section.
We need to not repeat job title. No Job ID.
We need to preserve all substantive info.
We need to use - for any list of duties/requirements/benefits.
We need
for prose.
We need to omit boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove the sections about California Applicants, EEO, Export Control Compliance, etc.
Also remove "Learn more at www.coreweave.com." maybe not needed but it's not boilerplate? It's a link; but it's not substantive about role. Could be considered navigation? Probably safe to drop.
Also remove "Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025." That's company info but maybe not needed for role? It's not about role; but it's substantive about company. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview may be considered not required but it's substantive about the company. However they said prefer a few substantive sections over many thin ones. Could include an "About CoreWeave" section? Not in allowed headings list. The allowed headings are only those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those. Company overview could go under About the role? Possibly. But "About the role" heading is for role description. The company overview could be placed in a
under About the role or maybe omitted? The instruction: "Prefer a few substantive sections over many thin ones." So we could include About the role with a paragraph describing CoreWeave and the role.
We need to not repeat job title as heading. The job title is likely "Storage Engineer" or similar but not given explicitly. We'll not add.
Now extract responsibilities from "What You’ll Do" and "About The Role". The "What You’ll Do" bullet list? Actually it's a paragraph with sentences. We'll turn each sentence into list items? The instruction: use
- for any list of duties/requirements/benefits. So we need to make a list for responsibilities. We'll extract each duty as a list item.
From "What You’ll Do": Actually the section heading "What You’ll Do" then a paragraph: "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."
Then "About The Role" then a list of bullet-like sentences separated by periods? Actually it's a run-on: "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."
We need to split into list items by each sentence (separated by periods). We'll produce
- for each.
Now requirements/qualifications/skills: "Who You Are" section includes bullet-like sentences: "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? We believe in investing in our people, and value candidates who can bring their own diversified experiences to our teams – even if you aren't a 100% skill or experience match." That's more encouragement; could be included as a paragraph.
We need to decide which headings: Requirements, Qualifications, Skills. Could combine into one section "Requirements" with list. Or separate: Requirements (experience), Qualifications (education), Skills (technical). But we have limited content; better to have one "Requirements" section with list covering education, experience, skills. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe one section "Requirements" containing all.
But we also have "Skills" heading allowed; we could split: Requirements (experience), Qualifications (education), Skills (technical). That would be three sections, each with list. That's okay if each has substantive content.
Let's do:
- About the role: prose paragraph describing CoreWeave and role.
- Responsibilities: list of duties.
- Requirements: list of experience (8-10+ years, storage systems engineering/infrastructure).
- Qualifications: list of education (Bachelor’s, Master’s, or PhD degree in CS, Engineering, or related).
- Skills: list of technical skills (object storage, protocols, languages, AI tools, observability, cloud-native, Kubernetes).
- Benefits: list of benefits.
- Pay: paragraph with salary range and note about discretionary bonus, equity awards.
We should not include Schedule.
Now ensure we don't include boilerplate like "We believe in investing in our people..." maybe include as a paragraph under Requirements or Qualifications? It's not a requirement but a note. Could be included as a
under Requirements.
Now produce HTML fragment.
We must not include or . Just the fragment.
Let's craft.
About the role: combine company overview and role description.
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."
Then maybe another paragraph: "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's fine.
Now Responsibilities list items:
- 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 list:
- 8–10+ years of experience working in storage systems engineering or infrastructure.
Maybe also include "Strong hands-on experience with object storage or distributed filesystems in production environments." That's more skill; but could be under Skills. We'll keep Requirements as experience.
Qualifications list:
- Bachelor’s, Master’s, or PhD degree in Computer Science, Engineering, or a related field.
Skills list:
- 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.
Now Benefits list (as per 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
Now Pay paragraph:
- "The base salary range for this role is $188,000
for prose. We need to omit boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove the sections about California Applicants, EEO, Export Control Compliance, etc. Also remove "Learn more at www.coreweave.com." maybe not needed but it's not boilerplate? It's a link; but it's not substantive about role. Could be considered navigation? Probably safe to drop. Also remove "Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025." That's company info but maybe not needed for role? It's not about role; but it's substantive about company. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview may be considered not required but it's substantive about the company. However they said prefer a few substantive sections over many thin ones. Could include an "About CoreWeave" section? Not in allowed headings list. The allowed headings are only those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those. Company overview could go under About the role? Possibly. But "About the role" heading is for role description. The company overview could be placed in a
under About the role or maybe omitted? The instruction: "Prefer a few substantive sections over many thin ones." So we could include About the role with a paragraph describing CoreWeave and the role. We need to not repeat job title as heading. The job title is likely "Storage Engineer" or similar but not given explicitly. We'll not add. Now extract responsibilities from "What You’ll Do" and "About The Role". The "What You’ll Do" bullet list? Actually it's a paragraph with sentences. We'll turn each sentence into list items? The instruction: use
- for any list of duties/requirements/benefits. So we need to make a list for responsibilities. We'll extract each duty as a list item.
From "What You’ll Do": Actually the section heading "What You’ll Do" then a paragraph: "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."
Then "About The Role" then a list of bullet-like sentences separated by periods? Actually it's a run-on: "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."
We need to split into list items by each sentence (separated by periods). We'll produce
- for each.
Now requirements/qualifications/skills: "Who You Are" section includes bullet-like sentences: "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? We believe in investing in our people, and value candidates who can bring their own diversified experiences to our teams – even if you aren't a 100% skill or experience match." That's more encouragement; could be included as a paragraph.
We need to decide which headings: Requirements, Qualifications, Skills. Could combine into one section "Requirements" with list. Or separate: Requirements (experience), Qualifications (education), Skills (technical). But we have limited content; better to have one "Requirements" section with list covering education, experience, skills. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe one section "Requirements" containing all.
But we also have "Skills" heading allowed; we could split: Requirements (experience), Qualifications (education), Skills (technical). That would be three sections, each with list. That's okay if each has substantive content.
Let's do:
- About the role: prose paragraph describing CoreWeave and role.
- Responsibilities: list of duties.
- Requirements: list of experience (8-10+ years, storage systems engineering/infrastructure).
- Qualifications: list of education (Bachelor’s, Master’s, or PhD degree in CS, Engineering, or related).
- Skills: list of technical skills (object storage, protocols, languages, AI tools, observability, cloud-native, Kubernetes).
- Benefits: list of benefits.
- Pay: paragraph with salary range and note about discretionary bonus, equity awards.
We should not include Schedule.
Now ensure we don't include boilerplate like "We believe in investing in our people..." maybe include as a paragraph under Requirements or Qualifications? It's not a requirement but a note. Could be included as a
under Requirements. Now produce HTML fragment. We must not include or . Just the fragment. Let's craft. About the role: combine company overview and role description. 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." Then maybe another paragraph: "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's fine. Now Responsibilities list items: - 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 list: - 8–10+ years of experience working in storage systems engineering or infrastructure. Maybe also include "Strong hands-on experience with object storage or distributed filesystems in production environments." That's more skill; but could be under Skills. We'll keep Requirements as experience. Qualifications list: - Bachelor’s, Master’s, or PhD degree in Computer Science, Engineering, or a related field. Skills list: - 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. Now Benefits list (as per 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 Now Pay paragraph: - "The base salary range for this role is $188,000
- for each.
Now requirements/qualifications/skills: "Who You Are" section includes bullet-like sentences: "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? We believe in investing in our people, and value candidates who can bring their own diversified experiences to our teams – even if you aren't a 100% skill or experience match." That's more encouragement; could be included as a paragraph.
We need to decide which headings: Requirements, Qualifications, Skills. Could combine into one section "Requirements" with list. Or separate: Requirements (experience), Qualifications (education), Skills (technical). But we have limited content; better to have one "Requirements" section with list covering education, experience, skills. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe one section "Requirements" containing all.
But we also have "Skills" heading allowed; we could split: Requirements (experience), Qualifications (education), Skills (technical). That would be three sections, each with list. That's okay if each has substantive content.
Let's do:
- About the role: prose paragraph describing CoreWeave and role.
- Responsibilities: list of duties.
- Requirements: list of experience (8-10+ years, storage systems engineering/infrastructure).
- Qualifications: list of education (Bachelor’s, Master’s, or PhD degree in CS, Engineering, or related).
- Skills: list of technical skills (object storage, protocols, languages, AI tools, observability, cloud-native, Kubernetes).
- Benefits: list of benefits.
- Pay: paragraph with salary range and note about discretionary bonus, equity awards.
We should not include Schedule.
Now ensure we don't include boilerplate like "We believe in investing in our people..." maybe include as a paragraph under Requirements or Qualifications? It's not a requirement but a note. Could be included as a