Senior Software Engineer, Weave - Weights & Biases
Weights & Biases · Seattle, WA · 3 wk ago
On-siteEngineering$165k–$220k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real, specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Intro paragraph about CoreWeave, acquisition, etc. Probably not needed as a section? Could be part of "About the role"? Actually "About The Role" heading appears in posting. So we should have
About the role
with content: description of role: "We’re looking for Software Engineers to help build and scale Weave. In this foundational role on a small but growing team, you’ll design and ship core functionality, gather feedback directly from users and customers, and continuously improve the product experience. You’ll work closely with cutting-edge AI builders, developing the next generation of tools that help teams understand, evaluate, and iterate on their AI agents."
Then bullet list of responsibilities: "Implement robust and ergonomic APIs. Design and build integrations with popular agent harnesses and SDKs such as Claude Code, Codex, pi.dev, OpenAI Agents SDK, etc. Scale and improve backend performance to support low-latency, high-volume production use cases. Build polished and intuitive features such online LLM judges, playgrounds, evaluations, labeling, and tracing UX. Partner directly with users to understand workflows, gather feedback, and rapidly iterate on solutions."
That's a list of duties.
Then "Who You Are": qualifications: Bachelor’s degree in Computer Science or related field. 8+ years of experience in Software Engineering. Deep knowledge of Python and/or TypeScript. Experience (personal or professional) in building AI agents. Ability to operate effectively amid ambiguity and adapt rapidly to a changing environment. Previous startup experience is a plus.
Then "Preferred Experience managing large-scale online production services or OLAP databases."
Then "Wondering If You’re a Good Fit? We Believe In Investing In Our People And Value Candidates Who Bring Diverse Experiences — Even If You Aren’t a 100% Match. Here Are a Few Qualities That Tend To Resonate With Our Team ..." This is more like "Qualities" maybe could be part of "Qualifications" or "Skills". Could treat as "Qualifications" or "Preferred Qualifications". We'll combine.
Then "Why Us?" etc: description of culture, values, growth opportunities. Could be a section "About the company" or "Why join us". But we only need sections when there is real specific content. The posting includes "Why Us?" with description of culture, values, growth opportunities. That's substantive. Could be a section "About the team" or "Why join us". However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add other headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use others? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we stick to those headings. But we can also add other headings if needed? Safer to stick to those. So we need to map content to those headings.
We have:
- About the role: we already have.
- Responsibilities: list of duties.
- Requirements: maybe the mandatory qualifications (Bachelor's, 8+ years, Python/TS, AI agents experience, ability to operate amid ambiguity). Could be "Requirements".
- Qualifications: maybe the preferred qualifications (startup experience a plus, managing large-scale online production services or OLAP databases). Could be "Qualifications".
- Skills: maybe the "Qualities that tend to resonate" (intersection of software, hardware, ML infra; passionate about building tools developers love; curious about full AI lifecycle). Could be "Skills".
- Benefits: list of benefits (medical, dental, vision insurance 100% paid, company-paid life insurance, voluntary supplemental life insurance, short/long-term disability, FSA, HSA, tuition reimbursement, ability to participate in ESPP, mental wellness benefits via Spring Health, family-forming support via Carrot, paid parental leave, flexible full-service childcare support with Kinside, 401(k) with generous employer match, flexible PTO, catered lunch each day, casual work environment, work culture focused on innovative disruption). Also mention discretionary bonus, equity awards, comprehensive benefits program. So we can create Benefits section.
- Pay: The base salary range $165,000 to $220,000. Also mention starting salary determined based on job-related knowledge, skills, experience, market location. Also mention discretionary bonus, equity awards. So we can include Pay.
- Schedule: Not mentioned. No schedule info. So we should not create Schedule section.
We also need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes sections like "California Applicants California Consumer Privacy Act Equal Opportunity & Accommodations", "Export Control Compliance". Those are legal/EEO; we should remove them. Also "We strive for both market alignment and internal equity when determining compensation." That's part of compensation but maybe okay to keep? It's not boilerplate; it's about compensation. Could keep in Pay section.
Also "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." That's also compensation detail; keep.
Also "In addition to a competitive salary, we offer a variety of benefits to support your needs. The benefits below reflect our US-based offerings; for roles in other locations, benefits vary and are shared during the hiring process." That's part of Benefits.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections.
We must not include duplicated lines. Ensure we don't repeat same bullet.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
We’re looking for Software Engineers to help build and scale Weave. In this foundational role on a small but growing team, you’ll design and ship core functionality, gather feedback directly from users and customers, and continuously improve the product experience. You’ll work closely with cutting-edge AI builders, developing the next generation of tools that help teams understand, evaluate, and iterate on their AI agents.
Responsibilities
- Implement robust and ergonomic APIs.
- Design and build integrations with popular agent harnesses and SDKs such as Claude Code, Codex, pi.dev, OpenAI Agents SDK, etc.
- Scale and improve backend performance to support low-latency, high-volume production use cases.
- Build polished and intuitive features such as online LLM judges, playgrounds, evaluations, labeling, and tracing UX.
- Partner directly with users to understand workflows, gather feedback, and rapidly iterate on solutions.
Requirements
- Bachelor’s degree in Computer Science or related field.
- 8+ years of experience in Software Engineering.
- Deep knowledge of Python and/or TypeScript.
- Experience (personal or professional) in building AI agents.
- Ability to operate effectively amid ambiguity and adapt rapidly to a changing environment.
Qualifications
- Previous startup experience is a plus.
- Preferred experience managing large-scale online production services or OLAP databases.
Skills
- You thrive at the intersection of software, hardware, and ML infrastructure — from tuning distributed systems to scaling backend services.
- You’re passionate about building tools that developers love to use — intuitive APIs and UX that bring clarity and speed to AI workflows.
- You’re curious about the full AI lifecycle — from experiment tracking and model deployment to observability and evaluation — and want to shape an end-to-end platform that redefines how AI is built and scaled.
Benefits
- 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
In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility).
Pay
The base salary range for this role is $165,000 to $220,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.
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.
We should ensure no duplicate content. The bullet list for benefits includes "Medical, dental, and vision insurance - 100% paid for by CoreWeave". Also we have a separate paragraph about discretionary bonus etc. That's fine.
Check for any boilerplate left: we removed EEO, export control, California Applicants, etc. Also removed "We work hard, have fun, and move fast! ..."? That's part of "Why Us?" which we didn't include as a section. Should we include that content somewhere? It's substantive about culture. Could be placed under "About the role" or maybe under a separate section like "Why join us". But we only have allowed headings; we could incorporate that into "About the role" or "Benefits"? Might be better to add a short paragraph under "About the role" after the initial description? But the "Why Us?" section includes: "We work hard, have fun, and move fast! We’re in an exciting stage of hyper-growth that you will not want to miss out on. We’re not afraid of a little chaos, and we’re constantly learning. Our team cares deeply about how we build our product and how we work together, which is represented through our core values: Be Curious at Your CoreAct Like an
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real, specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Intro paragraph about CoreWeave, acquisition, etc. Probably not needed as a section? Could be part of "About the role"? Actually "About The Role" heading appears in posting. So we should have
About the role
with content: description of role: "We’re looking for Software Engineers to help build and scale Weave. In this foundational role on a small but growing team, you’ll design and ship core functionality, gather feedback directly from users and customers, and continuously improve the product experience. You’ll work closely with cutting-edge AI builders, developing the next generation of tools that help teams understand, evaluate, and iterate on their AI agents." Then bullet list of responsibilities: "Implement robust and ergonomic APIs. Design and build integrations with popular agent harnesses and SDKs such as Claude Code, Codex, pi.dev, OpenAI Agents SDK, etc. Scale and improve backend performance to support low-latency, high-volume production use cases. Build polished and intuitive features such online LLM judges, playgrounds, evaluations, labeling, and tracing UX. Partner directly with users to understand workflows, gather feedback, and rapidly iterate on solutions." That's a list of duties. Then "Who You Are": qualifications: Bachelor’s degree in Computer Science or related field. 8+ years of experience in Software Engineering. Deep knowledge of Python and/or TypeScript. Experience (personal or professional) in building AI agents. Ability to operate effectively amid ambiguity and adapt rapidly to a changing environment. Previous startup experience is a plus. Then "Preferred Experience managing large-scale online production services or OLAP databases." Then "Wondering If You’re a Good Fit? We Believe In Investing In Our People And Value Candidates Who Bring Diverse Experiences — Even If You Aren’t a 100% Match. Here Are a Few Qualities That Tend To Resonate With Our Team ..." This is more like "Qualities" maybe could be part of "Qualifications" or "Skills". Could treat as "Qualifications" or "Preferred Qualifications". We'll combine. Then "Why Us?" etc: description of culture, values, growth opportunities. Could be a section "About the company" or "Why join us". But we only need sections when there is real specific content. The posting includes "Why Us?" with description of culture, values, growth opportunities. That's substantive. Could be a section "About the team" or "Why join us". However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add other headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use others? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we stick to those headings. But we can also add other headings if needed? Safer to stick to those. So we need to map content to those headings.
We have:
- About the role: we already have.
- Responsibilities: list of duties.
- Requirements: maybe the mandatory qualifications (Bachelor's, 8+ years, Python/TS, AI agents experience, ability to operate amid ambiguity). Could be "Requirements".
- Qualifications: maybe the preferred qualifications (startup experience a plus, managing large-scale online production services or OLAP databases). Could be "Qualifications".
- Skills: maybe the "Qualities that tend to resonate" (intersection of software, hardware, ML infra; passionate about building tools developers love; curious about full AI lifecycle). Could be "Skills".
- Benefits: list of benefits (medical, dental, vision insurance 100% paid, company-paid life insurance, voluntary supplemental life insurance, short/long-term disability, FSA, HSA, tuition reimbursement, ability to participate in ESPP, mental wellness benefits via Spring Health, family-forming support via Carrot, paid parental leave, flexible full-service childcare support with Kinside, 401(k) with generous employer match, flexible PTO, catered lunch each day, casual work environment, work culture focused on innovative disruption). Also mention discretionary bonus, equity awards, comprehensive benefits program. So we can create Benefits section.
- Pay: The base salary range $165,000 to $220,000. Also mention starting salary determined based on job-related knowledge, skills, experience, market location. Also mention discretionary bonus, equity awards. So we can include Pay.
- Schedule: Not mentioned. No schedule info. So we should not create Schedule section.
We also need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes sections like "California Applicants California Consumer Privacy Act Equal Opportunity & Accommodations", "Export Control Compliance". Those are legal/EEO; we should remove them. Also "We strive for both market alignment and internal equity when determining compensation." That's part of compensation but maybe okay to keep? It's not boilerplate; it's about compensation. Could keep in Pay section.
Also "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." That's also compensation detail; keep.
Also "In addition to a competitive salary, we offer a variety of benefits to support your needs. The benefits below reflect our US-based offerings; for roles in other locations, benefits vary and are shared during the hiring process." That's part of Benefits.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections.
We must not include duplicated lines. Ensure we don't repeat same bullet.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
About the role
We’re looking for Software Engineers to help build and scale Weave. In this foundational role on a small but growing team, you’ll design and ship core functionality, gather feedback directly from users and customers, and continuously improve the product experience. You’ll work closely with cutting-edge AI builders, developing the next generation of tools that help teams understand, evaluate, and iterate on their AI agents.
Responsibilities
- Implement robust and ergonomic APIs.
- Design and build integrations with popular agent harnesses and SDKs such as Claude Code, Codex, pi.dev, OpenAI Agents SDK, etc.
- Scale and improve backend performance to support low-latency, high-volume production use cases.
- Build polished and intuitive features such as online LLM judges, playgrounds, evaluations, labeling, and tracing UX.
- Partner directly with users to understand workflows, gather feedback, and rapidly iterate on solutions.
Requirements
- Bachelor’s degree in Computer Science or related field.
- 8+ years of experience in Software Engineering.
- Deep knowledge of Python and/or TypeScript.
- Experience (personal or professional) in building AI agents.
- Ability to operate effectively amid ambiguity and adapt rapidly to a changing environment.
Qualifications
- Previous startup experience is a plus.
- Preferred experience managing large-scale online production services or OLAP databases.
Skills
- You thrive at the intersection of software, hardware, and ML infrastructure — from tuning distributed systems to scaling backend services.
- You’re passionate about building tools that developers love to use — intuitive APIs and UX that bring clarity and speed to AI workflows.
- You’re curious about the full AI lifecycle — from experiment tracking and model deployment to observability and evaluation — and want to shape an end-to-end platform that redefines how AI is built and scaled.
Benefits
- 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
In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility).
Pay
The base salary range for this role is $165,000 to $220,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.
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.
We should ensure no duplicate content. The bullet list for benefits includes "Medical, dental, and vision insurance - 100% paid for by CoreWeave". Also we have a separate paragraph about discretionary bonus etc. That's fine. Check for any boilerplate left: we removed EEO, export control, California Applicants, etc. Also removed "We work hard, have fun, and move fast! ..."? That's part of "Why Us?" which we didn't include as a section. Should we include that content somewhere? It's substantive about culture. Could be placed under "About the role" or maybe under a separate section like "Why join us". But we only have allowed headings; we could incorporate that into "About the role" or "Benefits"? Might be better to add a short paragraph under "About the role" after the initial description? But the "Why Us?" section includes: "We work hard, have fun, and move fast! We’re in an exciting stage of hyper-growth that you will not want to miss out on. We’re not afraid of a little chaos, and we’re constantly learning. Our team cares deeply about how we build our product and how we work together, which is represented through our core values: Be Curious at Your CoreAct Like an