Senior Software Engineer I
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. The page already shows it, so we don't add.
We need to preserve all substantive information. Let's extract:
- Intro about CoreWeave (company description) maybe not needed? It's part of posting but could be considered background. Might be okay to include as a paragraph before sections? The instruction: output only HTML fragment; we can include a
with company overview if it's substantive. Not a heading. Probably okay.
- "What You’ll Do" section: description of building full-stack apps, UNION, etc. That's responsibilities.
- "About The Role": more details about building full-stack, owning production, stack, AI-facing, etc. Could be responsibilities as well. Might combine.
- "Who You Are": list of qualifications/experience. That's requirements/qualifications/skills.
- "Preferred Experience": additional preferred qualifications.
- "Wondering if you’re a good fit?" bullet list of qualities: could be skills or cultural fit.
- "Why CoreWeave?" about culture, values: maybe not needed but could be included as a section? Not specified headings; we could omit as not required.
- Pay: base salary range.
- Benefits: list.
We must not include boilerplate like EEO, legal, export control, etc. So remove those.
We must not include duplicated lines.
We need to decide sections: About the role (maybe combine What You’ll Do and About The Role). Responsibilities (maybe same). Requirements (must-have). Qualifications (maybe same as requirements). Skills (maybe technical skills). Benefits. Pay.
We need to avoid thin sections; prefer few substantive sections. Could combine Requirements and Qualifications into one? But headings are prescribed; we can include both if they have content. Might be okay.
Let's extract content:
Company overview 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. Learn more at www.coreweave.com."
What You’ll Do / About The Role combined:
- Build full-stack applications, and features in UNION itself, and own all of it in production, from the interface down to the data model.
- Stack: TypeScript with React and Next.js, Python services running on Kubernetes, and Postgres alongside the lakehouse.
- Care more that you have built and run this kind of software than which frameworks you built it in.
- A good share of the work is AI-facing, meaning natural language interfaces and agents that operate on governed data, plus the evaluation work that tells you whether they are any good.
- Owning a product area means you sit with the people who run the process and work out with them what the software should do.
- You are also the one who answers for it when it breaks.
- Most of these processes have never been written down anywhere, so a fair amount of the job is working out what to build before you build it.
Who You Are (requirements):
- 5+ years building and operating production software, including both backend services and modern web frontends
- Strong Python and TypeScript, with real experience in React, Next.js, or a comparable modern framework
- Experience designing and running HTTP APIs that other services depend on, including timeouts, retries, and keeping writes correct when a call fails partway through
- Strong SQL and relational data modeling, including schemas you had to change after they were already live
- Experience shipping LLM-backed features to production, including how you measured whether their output was correct
- Hands-on experience with containers and deployment tooling such as Docker, Helm, and Kubernetes, and with operating your own services
- Experience wiring applications up to data platforms and analytical databases such as Spark, Kafka, StarRocks, or Snowflake
- CI/CD, automated testing, observability, and on-call for the software you own
- Experience working directly with non-engineers on problems nobody had specified yet, and shipping software they adopted
Preferred Experience:
- Experience building AI-native applications such as text-to-SQL interfaces, copilots, agents, or automated insight generation
- Experience with agent frameworks such as LangGraph, and with the tracing and evaluation tooling around them
- Experience designing and running distributed systems in cloud-native environments such as Kubernetes
- Familiarity with open table formats such as Iceberg, Delta, or Hudi, and with query engines such as StarRocks, Snowflake, or BigQuery
- Experience building internal platforms or tools that other teams used to answer their own questions
- Background in an operationally heavy domain such as capacity planning, supply chain, or finance
Qualities (Wondering if you’re a good fit?):
- You want the people using your software to be people you know by name, and you take it personally when it gets in their way
- You want a product area that is yours to own end to end, from the first conversation with a user to the thing running in production
- You work well at speed. Priorities here move with the business, and the problems worth solving tend to arrive on short notice
- You want to know whether the AI in your product is any good, and you will build the evals to find out
- You stand behind what you ship, whether you wrote it or a model helped you write it
Why CoreWeave? (culture) maybe optional.
Pay: base salary range $153,000 to $204,000. Starting salary determined based on job-related knowledge, skills, experience, market location. Also 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
We should not include "California Applicants" etc.
Now produce HTML.
We need to decide sections:
-
About the Role
(maybe combine What You’ll Do and About The Role)
- Responsibilities
(maybe same as above; but we could avoid duplication by using About the Role for description and Responsibilities for bullet list of duties? But we have limited content; maybe we just have About the Role and Responsibilities combined? The instruction: use heading only when posting has real specific content for it. We have content for both About the Role and Responsibilities (they overlap). Could we treat About the Role as a section with prose, and Responsibilities as a list? Might be okay.
But we must not repeat same content in two sections? Not prohibited but better to avoid thin sections. Could combine into one section "About the Role" with prose and bullet list.
Similarly, Requirements and Qualifications could be combined.
Skills maybe we can list technical skills.
But we have many bullet points; we could put them under Requirements (must-have) and Preferred Experience under Qualifications or Skills.
Let's decide:
Section About the Role: prose description of role (what you'll do). Use .
Section Responsibilities: maybe not needed if we covered in About the Role. Could omit.
Section Requirements: list of mandatory qualifications (Who You Are). Use
- .
Section Qualifications: list of preferred experience (Preferred Experience). Use
- .
Section Skills: maybe list of technical skills extracted from both? Could be redundant. Could omit Skills.
Section Benefits: list of benefits.
Section Pay: salary range.
We must not include Schedule.
Now produce HTML.
We need to ensure we don't include any boilerplate like "Learn more at www.coreweave.com." That's okay as part of company overview.
We must not include "Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025." That's okay.
We must not include "What You’ll Do" heading; we will embed content.
Let's craft.
HTML fragment:
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. Learn more at www.coreweave.com.
About the Role
You will build full-stack applications, and features in UNION itself, and own all of it in production, from the interface down to the data model. Our stack is TypeScript with React and Next.js, Python services running on Kubernetes, and Postgres alongside the lakehouse. We care more that you have built and run this kind of software than which frameworks you built it in. A good share of the work is AI-facing, meaning natural language interfaces and agents that operate on governed data, plus the evaluation work that tells you whether they are any good. Owning a product area here means you sit with the people who run the process and work out with them what the software should do. You are also the one who answers for it when it breaks. Most of these processes have never been written down anywhere, so a fair amount of the job is working out what to build before you build it.
Requirements
- 5+ years building and operating production software, including both backend services and modern web frontends
- Strong Python and TypeScript, with real experience in React, Next.js, or a comparable modern framework
- Experience designing and running HTTP APIs that other services depend on, including timeouts, retries, and keeping writes correct when a call fails partway through
- Strong SQL and relational data modeling, including schemas you had to change after they were already live
- Experience shipping LLM-backed features to production, including how you measured whether their output was correct
- Hands-on experience with containers and deployment tooling such as Docker, Helm, and Kubernetes, and with operating
for prose. We must not repeat job title as heading. The page already shows it, so we don't add. We need to preserve all substantive information. Let's extract: - Intro about CoreWeave (company description) maybe not needed? It's part of posting but could be considered background. Might be okay to include as a paragraph before sections? The instruction: output only HTML fragment; we can include a
with company overview if it's substantive. Not a heading. Probably okay. - "What You’ll Do" section: description of building full-stack apps, UNION, etc. That's responsibilities. - "About The Role": more details about building full-stack, owning production, stack, AI-facing, etc. Could be responsibilities as well. Might combine. - "Who You Are": list of qualifications/experience. That's requirements/qualifications/skills. - "Preferred Experience": additional preferred qualifications. - "Wondering if you’re a good fit?" bullet list of qualities: could be skills or cultural fit. - "Why CoreWeave?" about culture, values: maybe not needed but could be included as a section? Not specified headings; we could omit as not required. - Pay: base salary range. - Benefits: list. We must not include boilerplate like EEO, legal, export control, etc. So remove those. We must not include duplicated lines. We need to decide sections: About the role (maybe combine What You’ll Do and About The Role). Responsibilities (maybe same). Requirements (must-have). Qualifications (maybe same as requirements). Skills (maybe technical skills). Benefits. Pay. We need to avoid thin sections; prefer few substantive sections. Could combine Requirements and Qualifications into one? But headings are prescribed; we can include both if they have content. Might be okay. Let's extract content: Company overview 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. Learn more at www.coreweave.com." What You’ll Do / About The Role combined: - Build full-stack applications, and features in UNION itself, and own all of it in production, from the interface down to the data model. - Stack: TypeScript with React and Next.js, Python services running on Kubernetes, and Postgres alongside the lakehouse. - Care more that you have built and run this kind of software than which frameworks you built it in. - A good share of the work is AI-facing, meaning natural language interfaces and agents that operate on governed data, plus the evaluation work that tells you whether they are any good. - Owning a product area means you sit with the people who run the process and work out with them what the software should do. - You are also the one who answers for it when it breaks. - Most of these processes have never been written down anywhere, so a fair amount of the job is working out what to build before you build it. Who You Are (requirements): - 5+ years building and operating production software, including both backend services and modern web frontends - Strong Python and TypeScript, with real experience in React, Next.js, or a comparable modern framework - Experience designing and running HTTP APIs that other services depend on, including timeouts, retries, and keeping writes correct when a call fails partway through - Strong SQL and relational data modeling, including schemas you had to change after they were already live - Experience shipping LLM-backed features to production, including how you measured whether their output was correct - Hands-on experience with containers and deployment tooling such as Docker, Helm, and Kubernetes, and with operating your own services - Experience wiring applications up to data platforms and analytical databases such as Spark, Kafka, StarRocks, or Snowflake - CI/CD, automated testing, observability, and on-call for the software you own - Experience working directly with non-engineers on problems nobody had specified yet, and shipping software they adopted Preferred Experience: - Experience building AI-native applications such as text-to-SQL interfaces, copilots, agents, or automated insight generation - Experience with agent frameworks such as LangGraph, and with the tracing and evaluation tooling around them - Experience designing and running distributed systems in cloud-native environments such as Kubernetes - Familiarity with open table formats such as Iceberg, Delta, or Hudi, and with query engines such as StarRocks, Snowflake, or BigQuery - Experience building internal platforms or tools that other teams used to answer their own questions - Background in an operationally heavy domain such as capacity planning, supply chain, or finance Qualities (Wondering if you’re a good fit?): - You want the people using your software to be people you know by name, and you take it personally when it gets in their way - You want a product area that is yours to own end to end, from the first conversation with a user to the thing running in production - You work well at speed. Priorities here move with the business, and the problems worth solving tend to arrive on short notice - You want to know whether the AI in your product is any good, and you will build the evals to find out - You stand behind what you ship, whether you wrote it or a model helped you write it Why CoreWeave? (culture) maybe optional. Pay: base salary range $153,000 to $204,000. Starting salary determined based on job-related knowledge, skills, experience, market location. Also 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 We should not include "California Applicants" etc. Now produce HTML. We need to decide sections: -
About the Role
(maybe combine What You’ll Do and About The Role) -Responsibilities
(maybe same as above; but we could avoid duplication by using About the Role for description and Responsibilities for bullet list of duties? But we have limited content; maybe we just have About the Role and Responsibilities combined? The instruction: use heading only when posting has real specific content for it. We have content for both About the Role and Responsibilities (they overlap). Could we treat About the Role as a section with prose, and Responsibilities as a list? Might be okay. But we must not repeat same content in two sections? Not prohibited but better to avoid thin sections. Could combine into one section "About the Role" with prose and bullet list. Similarly, Requirements and Qualifications could be combined. Skills maybe we can list technical skills. But we have many bullet points; we could put them under Requirements (must-have) and Preferred Experience under Qualifications or Skills. Let's decide: Section About the Role: prose description of role (what you'll do). Use. Section Responsibilities: maybe not needed if we covered in About the Role. Could omit. Section Requirements: list of mandatory qualifications (Who You Are). Use
- .
Section Qualifications: list of preferred experience (Preferred Experience). Use
- .
Section Skills: maybe list of technical skills extracted from both? Could be redundant. Could omit Skills.
Section Benefits: list of benefits.
Section Pay: salary range.
We must not include Schedule.
Now produce HTML.
We need to ensure we don't include any boilerplate like "Learn more at www.coreweave.com." That's okay as part of company overview.
We must not include "Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025." That's okay.
We must not include "What You’ll Do" heading; we will embed content.
Let's craft.
HTML fragment:
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. Learn more at www.coreweave.com.
About the Role
You will build full-stack applications, and features in UNION itself, and own all of it in production, from the interface down to the data model. Our stack is TypeScript with React and Next.js, Python services running on Kubernetes, and Postgres alongside the lakehouse. We care more that you have built and run this kind of software than which frameworks you built it in. A good share of the work is AI-facing, meaning natural language interfaces and agents that operate on governed data, plus the evaluation work that tells you whether they are any good. Owning a product area here means you sit with the people who run the process and work out with them what the software should do. You are also the one who answers for it when it breaks. Most of these processes have never been written down anywhere, so a fair amount of the job is working out what to build before you build it.
Requirements
- 5+ years building and operating production software, including both backend services and modern web frontends
- Strong Python and TypeScript, with real experience in React, Next.js, or a comparable modern framework
- Experience designing and running HTTP APIs that other services depend on, including timeouts, retries, and keeping writes correct when a call fails partway through
- Strong SQL and relational data modeling, including schemas you had to change after they were already live
- Experience shipping LLM-backed features to production, including how you measured whether their output was correct
- Hands-on experience with containers and deployment tooling such as Docker, Helm, and Kubernetes, and with operating
- .
Section Skills: maybe list of technical skills extracted from both? Could be redundant. Could omit Skills.
Section Benefits: list of benefits.
Section Pay: salary range.
We must not include Schedule.
Now produce HTML.
We need to ensure we don't include any boilerplate like "Learn more at www.coreweave.com." That's okay as part of company overview.
We must not include "Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025." That's okay.
We must not include "What You’ll Do" heading; we will embed content.
Let's craft.
HTML fragment: