Senior Software Engineer, Storage
CoreWeave · Livingston, NJ · 2 wk ago
Hybrid$143k–$210k/yrFull-time
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. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
Let's parse the posting.
First paragraph: description of CoreWeave (company intro). Might be considered "About the role"? Actually "What You’ll Do" then "About The Role". So we can treat "About the role" as the description after "About The Role". The earlier paragraph about CoreWeave is company overview; maybe we can include in "About the role"? But the instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- "What You’ll Do" bullet list (actually paragraph sentences). That could be Responsibilities.
- "About The Role" paragraph: Design and Implement distributed storage solutions ... etc. That's also responsibilities.
- "Who You Are": list of qualifications (degree, years experience, etc.) That's Requirements/Qualifications/Skills.
- "Wondering if you’re a good fit?" paragraph about qualities (maybe Skills? but could be omitted as filler? It's not specific? It says "If some of this describes you, we’d love to talk." Might be considered fluff; we could omit.
- "Why CoreWeave?" section about culture, values, etc. That's maybe Benefits? Actually it's about company culture; could be omitted as not specific benefits.
- "The base salary range for this role is $143,000 to $210,000." That's Pay.
- "In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility)." That's Benefits.
- "What We Offer" then list of benefits: medical, dental, vision insurance etc. That's Benefits details.
- "California Applicants California Consumer Privacy Act Equal Opportunity & Accommodations" etc. That's EEO boilerplate; remove.
- "Export Control Compliance" maybe keep? It's a requirement? It's a condition: applicant must be US person etc. That's a requirement (legal). Could be included in Requirements or Qualifications. It's substantive. We'll include maybe under Requirements.
We need to avoid duplication. Let's extract substantive content.
Responsibilities (What You’ll Do + 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's responsibilities.
Requirements/Qualifications/Skills: We have "Who You Are":
- 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.
Additionally, Export Control Compliance: applicant must be US person (citizen, national, lawful permanent resident, refugee, asylee) or eligible to access export controlled info without authorization or likely to obtain authorization. That's a requirement.
We could also include "Wondering if you’re a good fit?" qualities but they are vague; maybe skip.
Benefits: We have:
- base salary range $143,000 to $210,000 (Pay)
- total rewards includes discretionary bonus, equity awards, comprehensive benefits program.
- Benefits 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 maybe "We support and encourage an entrepreneurial outlook..." but that's culture.
We need to decide sections: About the role (maybe we can include company overview? But we have responsibilities separate). The instruction says use headings like About the role, Responsibilities, etc. We can include About the role as a short paragraph summarizing role (maybe from "About The Role" heading). But we already used that content for responsibilities. Could combine: About the role could be a brief summary: "The Object Storage 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 from earlier paragraph before "What You’ll Do". That seems appropriate for About the role.
Then Responsibilities as list.
Then Requirements (or Qualifications) as list. Could split into Requirements and Qualifications but we can combine into one section "Requirements". The instruction allows multiple sections but prefer few substantive sections. We'll include Requirements (covering degree, experience, etc.) and Skills (maybe separate). But we have many skill items; could be Skills section. Let's decide: We'll have:
- About the role (summary)
- Responsibilities
- Requirements (education, experience)
- Skills (technical proficiencies)
- Benefits
- Pay
- Schedule (if any schedule info? Not present. So we omit Schedule.)
We must not create Schedule unless posting states it. No schedule info, so omit.
Now ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML fragment: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- "What You’ll Do" bullet list (actually paragraph sentences). That could be Responsibilities.
- "About The Role" paragraph: Design and Implement distributed storage solutions ... etc. That's also responsibilities.
- "Who You Are": list of qualifications (degree, years experience, etc.) That's Requirements/Qualifications/Skills.
- "Wondering if you’re a good fit?" paragraph about qualities (maybe Skills? but could be omitted as filler? It's not specific? It says "If some of this describes you, we’d love to talk." Might be considered fluff; we could omit.
- "Why CoreWeave?" section about culture, values, etc. That's maybe Benefits? Actually it's about company culture; could be omitted as not specific benefits.
- "The base salary range for this role is $143,000 to $210,000." That's Pay.
- "In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility)." That's Benefits.
- "What We Offer" then list of benefits: medical, dental, vision insurance etc. That's Benefits details.
- "California Applicants California Consumer Privacy Act Equal Opportunity & Accommodations" etc. That's EEO boilerplate; remove.
- "Export Control Compliance" maybe keep? It's a requirement? It's a condition: applicant must be US person etc. That's a requirement (legal). Could be included in Requirements or Qualifications. It's substantive. We'll include maybe under Requirements.
We need to avoid duplication. Let's extract substantive content.
Responsibilities (What You’ll Do + 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's responsibilities.
Requirements/Qualifications/Skills: We have "Who You Are":
- 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.
Additionally, Export Control Compliance: applicant must be US person (citizen, national, lawful permanent resident, refugee, asylee) or eligible to access export controlled info without authorization or likely to obtain authorization. That's a requirement.
We could also include "Wondering if you’re a good fit?" qualities but they are vague; maybe skip.
Benefits: We have:
- base salary range $143,000 to $210,000 (Pay)
- total rewards includes discretionary bonus, equity awards, comprehensive benefits program.
- Benefits 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 maybe "We support and encourage an entrepreneurial outlook..." but that's culture.
We need to decide sections: About the role (maybe we can include company overview? But we have responsibilities separate). The instruction says use headings like About the role, Responsibilities, etc. We can include About the role as a short paragraph summarizing role (maybe from "About The Role" heading). But we already used that content for responsibilities. Could combine: About the role could be a brief summary: "The Object Storage 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 from earlier paragraph before "What You’ll Do". That seems appropriate for About the role.
Then Responsibilities as list.
Then Requirements (or Qualifications) as list. Could split into Requirements and Qualifications but we can combine into one section "Requirements". The instruction allows multiple sections but prefer few substantive sections. We'll include Requirements (covering degree, experience, etc.) and Skills (maybe separate). But we have many skill items; could be Skills section. Let's decide: We'll have:
- About the role (summary)
- Responsibilities
- Requirements (education, experience)
- Skills (technical proficiencies)
- Benefits
- Pay
- Schedule (if any schedule info? Not present. So we omit Schedule.)
We must not create Schedule unless posting states it. No schedule info, so omit.
Now ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML fragment: use for each section heading, then content:
for prose,
- for lists. We need to preserve all substantive info; not invent or summarize away detail. So we must keep each bullet point exactly as in posting (maybe slight rewording? Must preserve meaning; we can keep same phrasing). We'll copy the sentences. Let's extract About the role paragraph: "The Object Storage 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 three sentences. Now Responsibilities list: we need to capture each bullet from "What You’ll Do" and "About The Role". Actually "About The Role" already includes some responsibilities (Design and Implement...). We'll combine. 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 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. Check if any missing: The "About The Role" also had "Design and Implement distributed storage solutions to support scaling data intensive AI workloads." That's first. Good. Now Requirements (education/experience): - 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. Now Skills (technical proficiencies): - 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. - Must be a U.S. person (citizen, national, lawful permanent resident, refugee, asylee) or eligible to access export controlled information without a required export authorization, or eligible and reasonably likely to obtain the required export authorization from the applicable U.S. government agency. (We can phrase as per posting.) We need to keep the exact phrasing? The posting: "This position requires access to export controlled information. To conform to U.S. Government export regulations applicable to that information, applicant must either be (A) a U.S. person, defined as a (i) U.S. citizen or national, (ii) U.S. lawful permanent resident (green card holder), (iii) refugee under 8 U.S.C. 1157, or (iv) asylee under 8 U.S.C.1158, (B) eligible to access the export controlled information without a required export authorization, or (C) eligible and reasonably likely to obtain the required export authorization from the applicable U.S. government agency. CoreWeave may, for legitimate business reasons, decline to pursue any export licensing process." We can summarize but must preserve substantive info. We'll keep the key requirement: applicant must be a U.S. person (citizen/national, lawful permanent resident, refugee, asylee) or eligible to access export controlled info without authorization or likely to obtain authorization. We'll keep as a list item. Now Benefits: we need to list all benefits from "What We Offer". Also note base salary range is Pay. Benefits 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 - Pa