Senior Lead Technical Program Manager - Infrastructure
for section headings, - for any list of duties/requirements/benefits, and
for prose.
We must not emit a heading followed by filler/placeholder text. So only include sections where we have real content.
Let's decide sections:
- About the role: Could include the description of the role's purpose and impact (the paragraph about infrastructure being foundation, connective tissue, etc.) plus maybe the "Get to Know Klaviyo" mission? But that is more about company. However we could treat "About the role" as the description of what the role entails at a high level. We'll include the paragraph(s) that describe the role's purpose.
- Responsibilities: The "How You'll Make a Difference" section with multiple bullet-like paragraphs. We'll convert each sentence or clause into
- items.
- Requirements / Qualifications / Skills: We have "Who You Are" (traits) and "Preferred Experience" and "Nice to haves". We need to decide how to split. The instruction says use headings for Requirements, Qualifications, Skills. We could combine them into one section "Requirements" with sub-lists? But we must follow headings list; we can include multiple of those headings if we have content. However we should prefer few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But we need to follow the allowed headings; we can choose to include only those we have content for. For example, we could have "Requirements" for mandatory experience, "Skills" for technical fluency and traits, "Preferred Experience" maybe as "Qualifications". But we need to avoid thin sections.
Let's examine content:
Who You Are: list of traits (technically fluent, driver, influential, AI-first, comfortable with high volume, clear communicator, outcome-oriented). These are more like skills/attributes.
Preferred Experience: 8+ years experience in technical program management within fast-paced product engineering environment, ideally SaaS or high-growth tech. Demonstrated experience driving large-scale infrastructure rollouts across multiple engineering teams. Familiarity with cloud infrastructure, FinOps, security operations, and software migration programs. Strong fluency in tools such as Jira, Linear, Asana, or Smartsheet. Track record of managing competing priorities and delivering results without direct authority over engineering teams.
Nice to haves: Experience in both infrastructure and product engineering contexts. Familiarity with FinOps frameworks and cloud cost optimization programs. Experience building or evolving TPM practices in a nascent or growing function. Hands-on with CI/CD tooling, build systems, or security compliance frameworks.
Thus we could have:
- Requirements: the "Preferred Experience" (maybe treat as requirements). Or we could split: Requirements = the mandatory experience (8+ years etc). Qualifications = the nice-to-haves? Skills = the Who You Are traits.
But the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use any of those as needed.
We need to preserve all substantive information; we must not invent or summarize away detail. So we need to include all the points from Who You Are, Preferred Experience, Nice to haves.
We could create three sections: Requirements, Qualifications, Skills. Each with - list.
But that might be many sections; but they are substantive. The instruction says "Prefer a few substantive sections over many thin ones." However these sections are not thin; each contains multiple items. So it's okay.
Alternatively we could combine Requirements and Qualifications into one section "Requirements" and have Skills separate. But we need to decide.
Let's think: The posting has "Preferred Experience (guidance, Not Gates)" which is like qualifications. The "Who You Are" is like skills/attributes. The "Nice to haves" is additional qualifications.
Thus we could have:
- Requirements: the Preferred Experience list (the 8+ years etc). (These are the main qualifications.)
- Qualifications: the Nice to haves list.
- Skills: the Who You Are list.
That seems reasonable.
Now Benefits: we have mention of 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. Also maybe mention of accommodations? But that's more about AI fluency and accommodations; but that's not a benefit per se. We'll include the benefits described.
Pay: Base Pay Range For US Locations: $192,000—$288,000 USD.
Schedule: Travel up to 10% etc.
Now About the role: we need to capture the role description. Let's extract:
"Klaviyo's infrastructure is the foundation that every product, every customer, and every engineer depends on. In this role you will be the connective tissue between our Infrastructure organization and the rest of engineering, driving the rollout of critical, cross-cutting programs that affect how we build, operate, and secure our platform at scale. You will juggle a high volume of parallel efforts across cloud infrastructure, FinOps, build systems, software migrations, security operations, and more, keeping each moving, supporting teams to be successful, and escalating quickly when capacity or priority decisions need to be made. This is not a role for someone who waits to be told what to do. It's a role for someone who drives."
Also maybe include the earlier paragraph about valuing backgrounds etc? That's more about company culture; but could be part of About the role? However the instruction says do not repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. The intro about valuing backgrounds is not metadata; it's about company values. Could be part of About the role or maybe we could omit as it's more generic. But we need to preserve ALL substantive information; does that include the company culture statements? Probably yes, as it's substantive about the workplace. However the instruction also says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company culture statement is not boilerplate; it's part of the posting. So we should include it.
Thus About the role could include:
- At Klaviyo, we value the unique backgrounds, experiences and perspectives each Klaviyo (we call ourselves Klaviyos) brings to our workplace each and every day. We believe everyone deserves a fair shot at success and appreciate the experiences each person brings beyond the traditional job requirements. If you’re a close but not exact match with the description, we hope you’ll still consider applying. Want to learn more about life at Klaviyo? Visit klaviyo.com/careers to see how we empower creators to own their own destiny.
- Klaviyo's infrastructure is the foundation that every product, every customer, and every engineer depends on. In this role you will be the connective tissue between our Infrastructure organization and the rest of engineering, driving the rollout of critical, cross-cutting programs that affect how we build, operate, and secure our platform at scale. You will juggle a high volume of parallel efforts across cloud infrastructure, FinOps, build systems, software migrations, security operations, and more, keeping each moving, supporting teams to be successful, and escalating quickly when capacity or priority decisions need to be made. This is not a role for someone who waits to be told what to do. It's a role for someone who drives.
We could combine into a few paragraphs.
Now Responsibilities: The "How You'll Make a Difference" section includes multiple paragraphs each starting with a bold phrase? Actually the text:
"How You'll Make a Difference Own the rollout of infrastructure initiatives across engineering. Drive programs from planning through completion, coordinating across teams that don't report to you and don't always have capacity to prioritize infrastructure work. Keep things moving.Manage a high volume of concurrent efforts. At
for prose. We must not emit a heading followed by filler/placeholder text. So only include sections where we have real content. Let's decide sections: - About the role: Could include the description of the role's purpose and impact (the paragraph about infrastructure being foundation, connective tissue, etc.) plus maybe the "Get to Know Klaviyo" mission? But that is more about company. However we could treat "About the role" as the description of what the role entails at a high level. We'll include the paragraph(s) that describe the role's purpose. - Responsibilities: The "How You'll Make a Difference" section with multiple bullet-like paragraphs. We'll convert each sentence or clause into
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use any of those as needed.
We need to preserve all substantive information; we must not invent or summarize away detail. So we need to include all the points from Who You Are, Preferred Experience, Nice to haves.
We could create three sections: Requirements, Qualifications, Skills. Each with - list.
But that might be many sections; but they are substantive. The instruction says "Prefer a few substantive sections over many thin ones." However these sections are not thin; each contains multiple items. So it's okay.
Alternatively we could combine Requirements and Qualifications into one section "Requirements" and have Skills separate. But we need to decide.
Let's think: The posting has "Preferred Experience (guidance, Not Gates)" which is like qualifications. The "Who You Are" is like skills/attributes. The "Nice to haves" is additional qualifications.
Thus we could have:
- Requirements: the Preferred Experience list (the 8+ years etc). (These are the main qualifications.)
- Qualifications: the Nice to haves list.
- Skills: the Who You Are list.
That seems reasonable.
Now Benefits: we have mention of 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. Also maybe mention of accommodations? But that's more about AI fluency and accommodations; but that's not a benefit per se. We'll include the benefits described.
Pay: Base Pay Range For US Locations: $192,000—$288,000 USD.
Schedule: Travel up to 10% etc.
Now About the role: we need to capture the role description. Let's extract:
"Klaviyo's infrastructure is the foundation that every product, every customer, and every engineer depends on. In this role you will be the connective tissue between our Infrastructure organization and the rest of engineering, driving the rollout of critical, cross-cutting programs that affect how we build, operate, and secure our platform at scale. You will juggle a high volume of parallel efforts across cloud infrastructure, FinOps, build systems, software migrations, security operations, and more, keeping each moving, supporting teams to be successful, and escalating quickly when capacity or priority decisions need to be made. This is not a role for someone who waits to be told what to do. It's a role for someone who drives."
Also maybe include the earlier paragraph about valuing backgrounds etc? That's more about company culture; but could be part of About the role? However the instruction says do not repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. The intro about valuing backgrounds is not metadata; it's about company values. Could be part of About the role or maybe we could omit as it's more generic. But we need to preserve ALL substantive information; does that include the company culture statements? Probably yes, as it's substantive about the workplace. However the instruction also says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company culture statement is not boilerplate; it's part of the posting. So we should include it.
Thus About the role could include:
- At Klaviyo, we value the unique backgrounds, experiences and perspectives each Klaviyo (we call ourselves Klaviyos) brings to our workplace each and every day. We believe everyone deserves a fair shot at success and appreciate the experiences each person brings beyond the traditional job requirements. If you’re a close but not exact match with the description, we hope you’ll still consider applying. Want to learn more about life at Klaviyo? Visit klaviyo.com/careers to see how we empower creators to own their own destiny.
- Klaviyo's infrastructure is the foundation that every product, every customer, and every engineer depends on. In this role you will be the connective tissue between our Infrastructure organization and the rest of engineering, driving the rollout of critical, cross-cutting programs that affect how we build, operate, and secure our platform at scale. You will juggle a high volume of parallel efforts across cloud infrastructure, FinOps, build systems, software migrations, security operations, and more, keeping each moving, supporting teams to be successful, and escalating quickly when capacity or priority decisions need to be made. This is not a role for someone who waits to be told what to do. It's a role for someone who drives.
We could combine into a few paragraphs.
Now Responsibilities: The "How You'll Make a Difference" section includes multiple paragraphs each starting with a bold phrase? Actually the text:
"How You'll Make a Difference Own the rollout of infrastructure initiatives across engineering. Drive programs from planning through completion, coordinating across teams that don't report to you and don't always have capacity to prioritize infrastructure work. Keep things moving.Manage a high volume of concurrent efforts. At
or drop it. The intro about valuing backgrounds is not metadata; it's about company values. Could be part of About the role or maybe we could omit as it's more generic. But we need to preserve ALL substantive information; does that include the company culture statements? Probably yes, as it's substantive about the workplace. However the instruction also says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company culture statement is not boilerplate; it's part of the posting. So we should include it. Thus About the role could include: - At Klaviyo, we value the unique backgrounds, experiences and perspectives each Klaviyo (we call ourselves Klaviyos) brings to our workplace each and every day. We believe everyone deserves a fair shot at success and appreciate the experiences each person brings beyond the traditional job requirements. If you’re a close but not exact match with the description, we hope you’ll still consider applying. Want to learn more about life at Klaviyo? Visit klaviyo.com/careers to see how we empower creators to own their own destiny. - Klaviyo's infrastructure is the foundation that every product, every customer, and every engineer depends on. In this role you will be the connective tissue between our Infrastructure organization and the rest of engineering, driving the rollout of critical, cross-cutting programs that affect how we build, operate, and secure our platform at scale. You will juggle a high volume of parallel efforts across cloud infrastructure, FinOps, build systems, software migrations, security operations, and more, keeping each moving, supporting teams to be successful, and escalating quickly when capacity or priority decisions need to be made. This is not a role for someone who waits to be told what to do. It's a role for someone who drives. We could combine into a few paragraphs. Now Responsibilities: The "How You'll Make a Difference" section includes multiple paragraphs each starting with a bold phrase? Actually the text: "How You'll Make a Difference Own the rollout of infrastructure initiatives across engineering. Drive programs from planning through completion, coordinating across teams that don't report to you and don't always have capacity to prioritize infrastructure work. Keep things moving.Manage a high volume of concurrent efforts. At