Senior Engineer, Storage (File & Block)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings exactly those strings? Probably yes: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We include only those with content.
We need to extract content for each.
Let's parse:
- "What You'll Do" seems like Responsibilities. So we can put that under Responsibilities
with list items.
- "About The Role" seems like About the role (maybe overview). So we put that under About the role
with paragraphs.
- "Who You Are" includes qualifications, requirements, skills. We need to split into Requirements, Qualifications, Skills maybe. The posting lists: Bachelor's or Master's degree... 6–10 years building storage systems... Strong hands-on experience... Depth in the storage data path... Experience with multi-tenant services... Proficiency in a systems/back-end language... Experience building on Kubernetes... Familiarity with distributed databases... Ideally, experience with distributed or parallel storage stacks... Familiarity with storage observability tools... Bonus: exposure to high-performance data-path technologies... Strong debugging and problem-solving skills... Clear communicator...
We can categorize: Requirements: maybe the mandatory items (degree, years experience, hands-on experience, depth, multi-tenant, proficiency, Kubernetes experience). Qualifications: maybe the "Ideally" and "Bonus"? But we can just put all under Requirements and Skills? However we need to follow headings: Requirements, Qualifications, Skills. We need to decide what goes where.
Typically: Requirements = mandatory experience/education. Qualifications = education/degrees? Skills = technical skills. But we can approximate.
Let's extract:
Education: Bachelor's or Master's degree in Computer Science, Engineering, or a related field. -> could be Qualifications.
Experience: 6–10 years building storage systems, distributed systems, or infrastructure services. -> Requirements.
Strong hands-on experience with distributed or networked file systems and/or block storage in production — e.g., NFS/POSIX file semantics at scale, and/or block volume services (durability, snapshots, replication). -> Requirements or Skills.
Depth in the storage data path: IO performance, caching, small-file and metadata-heavy workloads, crash consistency, and resilience under load. -> Skills.
Experience with multi-tenant services or storage control planes — provisioning, tenancy/quota, and data-protection features (snapshots, encryption, key management). -> Requirements.
Proficiency in a systems/back-end language — Go strongly preferred (C or Rust a plus). -> Skills.
Experience building on Kubernetes — controllers/operators, CRDs, and CSI (dynamic provisioning, resize, snapshots, RWO volumes). -> Skills.
Familiarity with distributed databases (e.g., CockroachDB), workflow orchestration (e.g., Temporal), and gRPC/Protobuf service design. -> Skills.
Ideally, experience with distributed or parallel storage stacks such as Ceph/RBD, Lustre, GPFS/Spectrum Scale, BeeGFS, WEKA, VAST, or DAOS. -> maybe Qualifications (preferred).
Familiarity with storage observability tools and telemetry pipelines (e.g., ClickHouse, Prometheus, Grafana). -> Skills.
Bonus: exposure to high-performance data-path technologies (RDMA, GPUDirect Storage, RoCE, InfiniBand, SPDK). -> maybe Skills (bonus).
Strong debugging and problem-solving skills in distributed, high-performance environments. -> Skills.
Clear communicator, able to work collaboratively across teams and share technical insights effectively. -> Skills (soft skill).
Now "What We Offer" includes benefits and 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; 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.
Pay: The base salary range for this role is $182,000 to $242,000. 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."
Thus we have Pay section with salary range and bonus/equity mention.
Schedule: Not mentioned. No schedule info (like full-time, remote). So we should NOT include Schedule heading.
Now "About the role" section: The paragraph after "About The Role" includes design, build, operate etc. That's basically responsibilities but they already have "What You'll Do". However we can treat "About The Role" as overview. We'll include that paragraph(s) under About the role.
Let's extract the About The Role paragraph: It starts: "Design, build, and operate highly scalable, multi-tenant file and block storage — from the data path (NFS for file; durable, high-performance block volumes) to the control plane that governs tenancy, provisioning, and data protection — running natively on CoreWeave's storage fleet and delivered through Kubernetes." Then multiple sentences each starting with a bold phrase? Actually the text includes many sentences separated by periods. We'll keep as prose maybe split into
but could also be list? The instruction: Use
for prose. So we can put the whole block as one or multiple paragraphs. Probably better to keep as multiple paragraphs for readability but not required. We'll just wrap each sentence in
. However we must preserve all substantive information; not invent or summarize away detail. So we need to keep all details. Let's copy the About The Role text exactly as given: "Design, build, and operate highly scalable, multi-tenant file and block storage — from the data path (NFS for file; durable, high-performance block volumes) to the control plane that governs tenancy, provisioning, and data protection — running natively on CoreWeave's storage fleet and delivered through Kubernetes. Own the file system data path: NFS hot-path reliability, IO resilience, and performance — including the small-file / IOPS-heavy workloads that AI pipelines depend on, and the throughput that keeps GPUs fed. Build a native block storage service: durable, high-performance block volumes for customer workloads and internal stateful services — the third leg of the file/object/block triad, running on our own data path and shared storage hardware. Deliver both file and block as first-class Kubernetes citizens: design and ship a backend-neutral CSI driver with dynamic provisioning, resize, snapshots, and RWO block volumes, backed by a public provisioning SLO — reusing shared control-plane and CSI patterns across file and block rather than rebuilding per service. Build the control plane: multi-tenant isolation, quota, QoS, snapshots, key management (BYOK), audit, and lifecycle policy — the capabilities that unblock regulated and enterprise customers (e.g., encryption in transit, HIPAA controls). Improve the reliability, durability, and observability of the storage stack; partner with operations to monitor, analyze, and optimize using telemetry, metrics, and dashboards to improve performance, latency, and resilience. Work cross-functionally with platform, product, and infrastructure teams to deliver seamless storage across the stack, including tiering cold data to lower-cost object storage while preserving access. Share your knowledge and mentor other engineers on best practices in building distributed, high-performance systems." That is the responsibilities list actually. Wait that is under "About The Role". Actually the "What You'll Do" earlier maybe is similar but not present? Let's check earlier: after "What You'll Do" we have a paragraph: "We're looking for a Senior Storage Engineer, File & Block to help build and operate the file and block storage services at the heart of CoreWeave's Storage team — the high-performance, multi-tenant storage that our largest AI training and inference workloads and internal stateful services run on. You'll help turn CoreWeave's storage from a follower of GPU growth into a multiplier of it: owning the data path and control plane for both file and block, running them on our own hardware fleet, and shipping the customer-facing capabilities that unblock petabyte-scale deals. You'll work closely with compute, platform, and infrastructure teams to make storage fast, reliable, and effortless to consume at scale." That is more of a high-level overview. Then "About The Role" includes the detailed bullet-like sentences. So we can treat "What You'll Do" as About the role overview, and "About The Role" as Responsibilities (or vice versa). But the instruction says use headings like About the role, Responsibilities, etc. We need to decide mapping. Better to follow the headings as they appear: "About The Role" heading corresponds to About the role section. "What You'll Do" could be Responsibilities. However the content under "What You'll Do" is more generic overview; the detailed list is under "About The Role". But both are responsibilities. To avoid duplication, we could combine them under Responsibilities. But we need to follow instruction: include a section ONLY when the posting has real, specific content for it. So we can have both About the role and Responsibilities sections with content. Thus: - About the role: use the paragraph(s) from "What You'll Do". That's a few sentences. - Responsibilities: use the detailed list from "About The Role". Could be formatted as
- each line. Now Requirements: maybe the mandatory items from "Who You Are": degree, 6-10 years, hands-on experience, depth, multi-tenant, proficiency, Kubernetes experience. We'll put those as list. Qualifications: maybe the "Ideally" and "Bonus"? Actually "Ideally, experience with distributed or parallel storage stacks..." and "Bonus: exposure to high-performance data-path technologies". Could be qualifications (preferred). We'll put those as list. Skills: the rest: proficiency in Go, experience with Kubernetes, familiarity with distributed databases, workflow orchestration, gRPC/Protobuf, storage observability tools, debugging, communication. We'll list. But we need to avoid duplication: some items appear in both Requirements and Skills. We'll try to separate. Let's list items from "Who Are": 1. Bachelor's or Master's degree in Computer Science, Engineering, or a related field. (Qualification/Education) 2. 6–10 years building storage