Senior Software Engineer, W&B Agent - W&B

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. Remove boilerplate. Preserve all substantive info. We need to parse the job posting. Key sections: - "What You’ll Do" -> responsibilities. - "About The Role" -> description of role (maybe about the role). Could be considered "About the role". - "Who You Are" -> requirements/qualifications/skills. - "Preferred Experience" -> maybe part of qualifications. - "Why Us?" maybe not needed. - "What We Offer" -> benefits. - "The base salary range for this role is $182,000 to $242,000." -> Pay. - Schedule? Not mentioned. So we should not include Schedule section. - Benefits: list of benefits. - Pay: salary range. - Requirements: maybe "4+ years of full stack engineering experience..." etc. - Qualifications: maybe overlapping with requirements. We can combine? But we need separate sections only if content exists. Could put "Requirements" for mandatory, "Preferred Experience" for preferred. But guidelines: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate if we have content. Could treat "Who You Are" as Requirements (mandatory) and "Preferred Experience" as Qualifications (or Skills). However "Skills" could be separate for technical skills. We need to decide mapping. Let's extract: Responsibilities (What You’ll Do): - ARIA is the AI Research and Iterations Agent that enables continuous experimentation at scale. - Engineering team builds this research agent from scratch leveraging distributed backend systems that execute multi-turn agent conversations, to the React UI that thousands of ML practitioners interact with every day. - Mission: ship a fast, reliable, and delightful agent experience that accelerates ML workflows; every engineer owns outcome end to end. - As Senior Full Stack Engineer on ARIA Agent team, you'll own features and systems across entire stack — from backend infrastructure and API design to React frontend that powers chat interface, billing UI, and agent configuration experience. - Build and maintain distributed worker systems that run agent conversations at scale. - Design streaming architecture delivering real-time token output to browser. - Contribute to frontend components that make ARIA feel fast and intuitive. - Collaborate closely with ML science, product, iOS, and SRE teams — blending reliability engineering with product sensibility. - Day to day: move fluidly between debugging a production memory leak in a Kubernetes worker, shipping a new billing UI component, hardening egress controls on code execution sandbox. About the role (About The Role): - As a Senior Full Stack Engineer on the ARIA Agent team, you'll own features and systems across the entire stack — from backend infrastructure and API design to the React frontend that powers the chat interface, billing UI, and agent configuration experience. - Build and maintain the distributed worker systems that run agent conversations at scale, design the streaming architecture that delivers real-time token output to the browser, and contribute to the frontend components that make ARIA feel fast and intuitive. - Collaborate closely with ML science, product, iOS, and SRE teams — blending reliability engineering with product sensibility. - Day to day, you'll move fluidly between debugging a production memory leak in a Kubernetes worker, shipping a new billing UI component, and hardening the egress controls on the code execution sandbox. Actually "About The Role" seems similar to responsibilities. Might be redundant. But we can keep both? The instruction: Prefer a few substantive sections over many thin ones. Could combine About the role and Responsibilities? But they are distinct headings. We could keep About the role as a brief overview, and Responsibilities as detailed list. However content overlaps heavily. Might be better to have only one section: Responsibilities (or About the role). But we need to follow instruction: include a section ONLY when posting has real, specific content for it. Both have content. Could keep both but avoid duplication? Might be okay. Requirements (Who You Are): - 4+ years of full stack engineering experience, with meaningful depth in both backend services and React/TypeScript frontend development. - Strong Python backend skills — async patterns, FastAPI, distributed state machines, Kubernetes pod lifecycle. - Proficient in TypeScript and React; comfortable building and maintaining production UI components including real-time streaming interfaces, complex state management, and responsive layouts across web and mobile web. - Experience building and operating services at scale — rolling deploys, autoscaling, worker concurrency, graceful termination. - Experience with observability tooling (Datadog, Weave tracing, structured logging) and a track record of building dashboards that surface actionable signals. - Security-conscious engineering mindset — input validation, sandboxed code execution, egress controls, and payload hardening. - Experience with MySQL or similar RDBMS for transactional state management. Qualifications (Preferred Experience): - Experience building streaming UIs (server-sent events, WebSockets) with graceful fallback handling. - Background in ML infrastructure, developer tooling, or observability platforms. - Hands-on experience building and shipping production-grade AI agents — including tool use, multi-turn conversation management, and agentic reliability patterns. - Comfortable thriving in a fast-paced startup environment — able to move quickly, make pragmatic tradeoffs, and iterate on real user feedback without sacrificing production quality. Skills: maybe we could list specific technical skills: Python, FastAPI, Kubernetes, TypeScript, React, MySQL, Datadog, etc. But we already have them in requirements. Could create Skills section summarizing. However guidelines: Prefer few substantive sections over many thin ones. Might be okay to not have separate Skills if covered. Benefits (What We Offer): - 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). Schedule: Not present, so omit. We must not include boilerplate like EEO, legal, etc. Remove those. We must not repeat job title as heading. We must output only HTML fragment. We'll produce sections:

About the role

... (maybe short paragraph)

Responsibilities

• ...
...

Requirements

• ...
...

Preferred Experience

maybe but heading must be from list: Qualifications. So we use Qualifications.

Qualifications

• ...
...

Skills

maybe not needed.

Benefits

• ...
...

Pay

... (maybe paragraph)

We need to ensure we don't include filler like "commensurate with experience". Not present. Let's craft content. About the role: Could be a short paragraph summarizing role: "As a Senior Full Stack Engineer on the ARIA Agent team, you'll own features and systems across the entire stack — from backend infrastructure and API design to the React frontend that powers the chat interface, billing UI, and agent configuration experience. You'll build and maintain distributed worker systems that run agent conversations at scale, design the streaming architecture that delivers real-time token output to the browser, and contribute to frontend components that make ARIA feel fast and intuitive. You'll collaborate closely with ML science, product, iOS, and SRE teams, blending reliability engineering with product sensibility. Day‑to‑day work includes debugging production memory leaks in Kubernetes workers, shipping new billing UI components, and hardening egress controls on the code execution sandbox." Responsibilities: Could be bullet list of duties: maybe same as above but more bullet. But we might duplicate. Could keep About the role as overview paragraph, Responsibilities as bullet list of specific duties. Let's extract bullet points from "What You’ll Do" and "About The Role" combined. Bullet list: - Build and maintain distributed worker systems that run agent conversations at scale. - Design streaming architecture delivering real‑time token output to the browser. - Contribute to frontend components (chat interface, billing UI, agent configuration) that make ARIA feel fast and intuitive. - Collaborate with ML science, product, iOS, and SRE teams to blend reliability engineering with product sensibility. - Debug production memory leaks in Kubernetes workers. - Ship new billing UI components. - Harden egress controls on the code execution sandbox. - Own features and systems across the full stack (backend infrastructure, API design, React frontend). - Ensure fast, reliable, delightful agent experience that accelerates ML workflows. We can include. Requirements bullet list from "Who Are": - 4+ years of full stack engineering experience with meaningful depth in both backend services and React/TypeScript frontend development. - Strong Python backend skills: async patterns, FastAPI, distributed state machines, Kubernetes pod lifecycle. - Proficient in TypeScript and React; comfortable building and maintaining production UI components including real‑time streaming interfaces, complex state management, and responsive layouts across web and mobile web. - Experience building and operating services at scale: rolling deploys, autoscaling, worker concurrency, graceful termination. - Experience with observability tooling (Datadog, Weave tracing, structured logging) and building dashboards that surface actionable signals. - Security‑conscious engineering mindset: input validation, sandboxed code execution, egress controls, payload hardening. - Experience with MySQL or similar RDBMS for transactional state management. Qualifications bullet list from "Preferred Experience": - Experience building streaming UIs (server‑sent events, WebSockets) with graceful fallback handling. - Background in ML infrastructure, developer tooling, or observability platforms. - Hands‑on experience building and shipping production‑grade AI agents — including tool use, multi‑turn conversation management, and agentic reliability patterns. - Comfortable thriving in a fast‑paced startup environment — able to move quickly, make pragmatic tradeoffs, and iterate on real user feedback without sacrificing production quality. Benefits bullet list from "What We Offer": - Medical, dental, and vision insurance – 100% paid 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 office and data center locations - Casual work environment - Work culture focused on innovative disruption Pay paragraph: - The base salary range for this role is $182,000 to $242,000. Starting salary determined