Staff Engineer, Applied AI (Customer Agent)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the equal opportunity statement, the important notice about security, etc. Also remove the Massachusetts Applicants legal line? That's a legal requirement about lie detector test; that's likely boilerplate legal. Should we remove? It's a specific legal statement; but it's likely considered boilerplate legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove that line. Also remove the "Massachusetts Applicants" line? It's part of that legal. Probably remove.
Also remove the "By participating in Klaviyo’s interview process..." etc. Also remove the "AI fluency at Klaviyo includes responsible use..." etc. Also remove the "We provide accommodations as needed." etc. Also remove the "By clicking 'Submit Application' you consent..." etc. Also remove the "If you do not wish for Klaviyo to process your Personal Data..." etc. Also remove the "You can find our Job Applicant Privacy Notice here and here (FR)." etc.
Also remove the "Get to Know Klaviyo" paragraph? That's about company description; might be considered boilerplate? It's not exactly legal but could be considered generic marketing. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Get to Know Klaviyo" is not explicitly listed, but it's more about company overview; could be considered boilerplate but not prohibited. However we should preserve substantive information about the role. The company overview may be considered not essential to the job posting; but it's not prohibited. However to be safe, we might keep it? The instruction says "Prefer a few substantive sections over many thin ones." The company overview is not a section heading we have; we could incorporate into About the Team? But it's separate. Might be considered filler. I'd lean to remove it as it's not directly about the role. However the instruction only mandates removal of certain types; not explicitly forbidding company overview. But to keep output concise, we can omit.
We need to include sections: About The Team, About The Role, How You'll Make An Impact, What We're Looking For, Nice To Haves, Benefits, Pay, Schedule (travel). Let's extract content.
About The Team: paragraph(s) after "About The Team". Let's capture:
"Our Engineering team builds the AI systems that power how brands run their businesses on Klaviyo. We move fast, ship in production, and hold a high bar for what "AI-native" actually means: systems that make real judgment calls, not demos. The Customer Agent team is one of the newest and most ambitious groups in that org, based in Boston and working in-office: we're building a conversational AI system that lets brands serve their own customers at a scale no human support team could match. We're still small enough that one engineer’s work visibly shapes how the whole platform evolves. We're past the demo stage: the team ships changes against live customer traffic, measures quality with real evaluation frameworks, and treats reliability as a product feature, not an afterthought."
That's the content.
About The Role: after "About The Role". Content:
"As a Staff Engineer, you'll set the technical and product direction for a core area of Customer Agent end to end, building a 0-to-1 agentic product with the speed and ownership of a startup, backed by the scale and resources of one of the most innovative tech companies on the East Coast, while staying hands-on with the hardest problems yourself. This is a lead-level role, with a wide footprint across our agentic product - from orchestration to governance - that grows based on where the product is when you join. We're looking for an engineer who owns complex, ambiguous problems, who has built, scaled, and supported a production agentic system through everything that comes after the demo, and who up-levels the people, process, and technology around them."
That's prose.
How You'll Make An Impact: bullet points after that heading. Let's capture each line:
- Set the technical and product direction for a core area of Customer Agent, from architecture through production, and contribute to the direction of the platform overall.
- Take on the hardest technical problems in your area: orchestration, evaluation, guardrails, memory & context, failure handling for non-deterministic systems.
- Write and ship code, review designs, and make the hard calls in your area when there’s no obvious right answer.
- Define patterns that other engineers adopt, and mentor through design reviews rather than direct management.
- Partner with product, design, data science, and go-to-market leaders to shape what gets built, not just how it’s built.
- Evaluate emerging AI technologies and bring the ones worth betting on into production.
These are duties; we should put in
- .
What We're Looking For: bullet points after that heading. Let's capture:
- You've built, scaled, and supported production agentic systems, not just prototyped them: real orchestration, evals, guardrails, and non-deterministic failure handling.
- You've owned your part of one through launch, incidents, and the operational reality after the demo.
- You've learned the hard lessons that only come from running agents in production: securing them against misuse and abuse, and the operational scar tissue of keeping a non-deterministic system reliable as usage grows.
- You've owned technical and product direction for a significant area before, not just your own component, and you can point to something you designed and championed that shipped and that other engineers built on.
- You're hands-on: writing code, reviewing your own and others’ architecture decisions, and debugging production issues yourself, not delegating the hardest problems away.
- Your patterns and designs are reused by other engineers, and you've unblocked many others’ projects, not just your own.
- You communicate complex technical trade-offs clearly across engineering and product audiences, and you can turn an undefined problem into a plan others rally behind.
These are requirements; put in
- .
Nice To Haves: bullet points after that heading. Capture:
- Experience working on a multi-tenant agent platform at production scale, where external customers configure their own agent behavior on shared infrastructure.
- Experience building 0-to-1 products or working in startup environments.
- A track record with production evaluation systems, AI observability, or human-in-the-loop workflows for LLM-powered products.
These are nice-to-haves; put in
- .
Benefits: from paragraph: "In addition to base salary, our total compensation package may include participation in the company’s annual cash bonus plan, variable compensation (OTE) for sales and customer success roles, equity, sign-on payments, and a comprehensive range of health, welfare, and wellbeing benefits based on eligibility."
We can put that as
- items? It's a list of benefits: participation in annual cash bonus plan, variable compensation (OTE) for sales and customer success roles, equity, sign-on payments, comprehensive range of health, welfare, and wellbeing benefits based on eligibility. We'll make each as
- .
Pay: Base Pay Range For US Locations: $176,000—$264,000 USD. Also note: "Our salary range reflects the cost of labor across various U.S. geographic markets. The range displayed below reflects the minimum and maximum target salaries for the position across all our US locations. The base salary offered for this position is determined by several factors, including the applicant’s job-related skills, relevant experience, education or training, and work location." That's prose about pay determination. We can include that as
then maybe the range as
or
? The instruction: use - for any list of duties/requirements/benefits. Pay is not a list; we can use
. We'll include a
describing determination and then a
with the range.
Schedule: travel note: "This role may require up to 10% travel for purposes such as new hire onboarding, client or partner work if applicable, team meetings, and industry events. Travel is coordinated in advance." That's schedule/travel. We'll put as
.
We must not include any boilerplate like equal opportunity, Massachusetts Applicants legal line, etc. Also remove the "Get to Know Klaviyo" paragraph, the AI fluency line, accommodations, etc. Also remove the "By participating in Klaviyo’s interview process..." etc. Also remove the "IMPORTANT NOTICE: Our company takes the security and privacy..." etc. Also remove the "By clicking 'Submit Application'..." etc.
Now construct HTML.
We'll start with
About the Team
then ...
Then About the Role
...
Then How You'll Make An Impact
- ...
...
Then What We're Looking For
...
Then Nice To Haves
...
Then Benefits
...
Then Pay
... determination ...
Base Pay Range For US Locations: $176,000—$264,000 USD
Then Schedule
This role may require up to 10% travel for purposes such as new hire onboarding, client or partner work if applicable, team meetings, and industry events. Travel is coordinated in advance.
Check for any duplicated lines: ensure we didn't repeat.
Now ensure we didn't include any heading with empty content. All sections have content.
Now output only HTML fragment.
Let's craft the text precisely.
About The Team paragraph: combine sentences exactly as in posting.
"Our Engineering team builds the AI systems that power how brands run their businesses on Klaviyo. We move fast, ship in production, and hold a high bar for what "AI-native" actually means: systems that make real judgment calls, not demos. The Customer Agent team is one of the newest and most ambitious groups in that org, based in Boston and working in-office: we're building a conversational AI system that lets brands serve their own customers at a scale no human support team could match. We're still small enough that one engineer’s work visibly shapes how the whole platform evolves. We're past the demo stage: the team ships changes against live customer traffic, measures quality with real evaluation frameworks, and treats reliability as a product feature, not an afterthought."
Check for any stray quotes; we need to escape? In HTML we can keep straight quotes.
About The Role paragraph:
"As a Staff Engineer, you'll set the technical and product direction for a core area of Customer Agent end to end, building a 0-to-
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the equal opportunity statement, the important notice about security, etc. Also remove the Massachusetts Applicants legal line? That's a legal requirement about lie detector test; that's likely boilerplate legal. Should we remove? It's a specific legal statement; but it's likely considered boilerplate legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove that line. Also remove the "Massachusetts Applicants" line? It's part of that legal. Probably remove. Also remove the "By participating in Klaviyo’s interview process..." etc. Also remove the "AI fluency at Klaviyo includes responsible use..." etc. Also remove the "We provide accommodations as needed." etc. Also remove the "By clicking 'Submit Application' you consent..." etc. Also remove the "If you do not wish for Klaviyo to process your Personal Data..." etc. Also remove the "You can find our Job Applicant Privacy Notice here and here (FR)." etc. Also remove the "Get to Know Klaviyo" paragraph? That's about company description; might be considered boilerplate? It's not exactly legal but could be considered generic marketing. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Get to Know Klaviyo" is not explicitly listed, but it's more about company overview; could be considered boilerplate but not prohibited. However we should preserve substantive information about the role. The company overview may be considered not essential to the job posting; but it's not prohibited. However to be safe, we might keep it? The instruction says "Prefer a few substantive sections over many thin ones." The company overview is not a section heading we have; we could incorporate into About the Team? But it's separate. Might be considered filler. I'd lean to remove it as it's not directly about the role. However the instruction only mandates removal of certain types; not explicitly forbidding company overview. But to keep output concise, we can omit. We need to include sections: About The Team, About The Role, How You'll Make An Impact, What We're Looking For, Nice To Haves, Benefits, Pay, Schedule (travel). Let's extract content. About The Team: paragraph(s) after "About The Team". Let's capture: "Our Engineering team builds the AI systems that power how brands run their businesses on Klaviyo. We move fast, ship in production, and hold a high bar for what "AI-native" actually means: systems that make real judgment calls, not demos. The Customer Agent team is one of the newest and most ambitious groups in that org, based in Boston and working in-office: we're building a conversational AI system that lets brands serve their own customers at a scale no human support team could match. We're still small enough that one engineer’s work visibly shapes how the whole platform evolves. We're past the demo stage: the team ships changes against live customer traffic, measures quality with real evaluation frameworks, and treats reliability as a product feature, not an afterthought." That's the content. About The Role: after "About The Role". Content: "As a Staff Engineer, you'll set the technical and product direction for a core area of Customer Agent end to end, building a 0-to-1 agentic product with the speed and ownership of a startup, backed by the scale and resources of one of the most innovative tech companies on the East Coast, while staying hands-on with the hardest problems yourself. This is a lead-level role, with a wide footprint across our agentic product - from orchestration to governance - that grows based on where the product is when you join. We're looking for an engineer who owns complex, ambiguous problems, who has built, scaled, and supported a production agentic system through everything that comes after the demo, and who up-levels the people, process, and technology around them." That's prose. How You'll Make An Impact: bullet points after that heading. Let's capture each line: - Set the technical and product direction for a core area of Customer Agent, from architecture through production, and contribute to the direction of the platform overall. - Take on the hardest technical problems in your area: orchestration, evaluation, guardrails, memory & context, failure handling for non-deterministic systems. - Write and ship code, review designs, and make the hard calls in your area when there’s no obvious right answer. - Define patterns that other engineers adopt, and mentor through design reviews rather than direct management. - Partner with product, design, data science, and go-to-market leaders to shape what gets built, not just how it’s built. - Evaluate emerging AI technologies and bring the ones worth betting on into production. These are duties; we should put in
- .
What We're Looking For: bullet points after that heading. Let's capture:
- You've built, scaled, and supported production agentic systems, not just prototyped them: real orchestration, evals, guardrails, and non-deterministic failure handling.
- You've owned your part of one through launch, incidents, and the operational reality after the demo.
- You've learned the hard lessons that only come from running agents in production: securing them against misuse and abuse, and the operational scar tissue of keeping a non-deterministic system reliable as usage grows.
- You've owned technical and product direction for a significant area before, not just your own component, and you can point to something you designed and championed that shipped and that other engineers built on.
- You're hands-on: writing code, reviewing your own and others’ architecture decisions, and debugging production issues yourself, not delegating the hardest problems away.
- Your patterns and designs are reused by other engineers, and you've unblocked many others’ projects, not just your own.
- You communicate complex technical trade-offs clearly across engineering and product audiences, and you can turn an undefined problem into a plan others rally behind.
These are requirements; put in
- .
Nice To Haves: bullet points after that heading. Capture:
- Experience working on a multi-tenant agent platform at production scale, where external customers configure their own agent behavior on shared infrastructure.
- Experience building 0-to-1 products or working in startup environments.
- A track record with production evaluation systems, AI observability, or human-in-the-loop workflows for LLM-powered products.
These are nice-to-haves; put in
- .
Benefits: from paragraph: "In addition to base salary, our total compensation package may include participation in the company’s annual cash bonus plan, variable compensation (OTE) for sales and customer success roles, equity, sign-on payments, and a comprehensive range of health, welfare, and wellbeing benefits based on eligibility."
We can put that as
- items? It's a list of benefits: participation in annual cash bonus plan, variable compensation (OTE) for sales and customer success roles, equity, sign-on payments, comprehensive range of health, welfare, and wellbeing benefits based on eligibility. We'll make each as
- .
Pay: Base Pay Range For US Locations: $176,000—$264,000 USD. Also note: "Our salary range reflects the cost of labor across various U.S. geographic markets. The range displayed below reflects the minimum and maximum target salaries for the position across all our US locations. The base salary offered for this position is determined by several factors, including the applicant’s job-related skills, relevant experience, education or training, and work location." That's prose about pay determination. We can include that as
then maybe the range as
or
- ? The instruction: use
- for any list of duties/requirements/benefits. Pay is not a list; we can use
. We'll include a
describing determination and then a
with the range. Schedule: travel note: "This role may require up to 10% travel for purposes such as new hire onboarding, client or partner work if applicable, team meetings, and industry events. Travel is coordinated in advance." That's schedule/travel. We'll put as
. We must not include any boilerplate like equal opportunity, Massachusetts Applicants legal line, etc. Also remove the "Get to Know Klaviyo" paragraph, the AI fluency line, accommodations, etc. Also remove the "By participating in Klaviyo’s interview process..." etc. Also remove the "IMPORTANT NOTICE: Our company takes the security and privacy..." etc. Also remove the "By clicking 'Submit Application'..." etc. Now construct HTML. We'll start with
About the Team
then...
ThenAbout the Role
...
ThenHow You'll Make An Impact
- ... ...
What We're Looking For
- ...
Nice To Haves
- ...
Benefits
- ...
Pay
... determination ...
Base Pay Range For US Locations: $176,000—$264,000 USD
ThenSchedule
This role may require up to 10% travel for purposes such as new hire onboarding, client or partner work if applicable, team meetings, and industry events. Travel is coordinated in advance.
Check for any duplicated lines: ensure we didn't repeat. Now ensure we didn't include any heading with empty content. All sections have content. Now output only HTML fragment. Let's craft the text precisely. About The Team paragraph: combine sentences exactly as in posting. "Our Engineering team builds the AI systems that power how brands run their businesses on Klaviyo. We move fast, ship in production, and hold a high bar for what "AI-native" actually means: systems that make real judgment calls, not demos. The Customer Agent team is one of the newest and most ambitious groups in that org, based in Boston and working in-office: we're building a conversational AI system that lets brands serve their own customers at a scale no human support team could match. We're still small enough that one engineer’s work visibly shapes how the whole platform evolves. We're past the demo stage: the team ships changes against live customer traffic, measures quality with real evaluation frameworks, and treats reliability as a product feature, not an afterthought." Check for any stray quotes; we need to escape? In HTML we can keep straight quotes. About The Role paragraph: "As a Staff Engineer, you'll set the technical and product direction for a core area of Customer Agent end to end, building a 0-to-
- for any list of duties/requirements/benefits. Pay is not a list; we can use
- .
Benefits: from paragraph: "In addition to base salary, our total compensation package may include participation in the company’s annual cash bonus plan, variable compensation (OTE) for sales and customer success roles, equity, sign-on payments, and a comprehensive range of health, welfare, and wellbeing benefits based on eligibility."
We can put that as
- .
Nice To Haves: bullet points after that heading. Capture:
- Experience working on a multi-tenant agent platform at production scale, where external customers configure their own agent behavior on shared infrastructure.
- Experience building 0-to-1 products or working in startup environments.
- A track record with production evaluation systems, AI observability, or human-in-the-loop workflows for LLM-powered products.
These are nice-to-haves; put in