The opportunity
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.
What you'll do
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 any given time you'll be: tracking security operations improvements, FinOps initiatives, build system changes, software migrations, and other cross-cutting infrastructure programs simultaneously. Clear prioritization and status visibility are non-negotiable.
Hold teams accountable and escalate when needed. You know how to build the: relationships and create the visibility that keeps infrastructure work from getting deprioritized. When a team genuinely lacks capacity, you surface that quickly, bring the right people into the conversation, and get a trade-off decision made — not absorb the delay quietly.
Develop a way to provide program health continuously. Establish and maintain: clear, actionable reporting on the status of all infrastructure rollouts. Leadership should always know what's on track, what's at risk, and what decisions are needed from them.
Partner with Infrastructure leadership on planning and prioritization. Work: closely with engineering and SRE leadership to build and maintain a rolling roadmap, sequence work across teams, and ensure infrastructure investments align with engineering and business priorities.
Define clear ways of working across teams. Create frameworks, templates, and: coordination models that make it easier for infrastructure and product engineering teams to work together effectively. Build the playbook as you go.
What they're looking for
- Technically fluent. You've worked closely with infrastructure, SRE, or: platform engineering teams. You understand security operations, cloud infrastructure, CI/CD, and software migrations well enough to engage substantively, not just track status.
- A driver, not a facilitator. You move work forward. You follow up, push back,: escalate, and hold people accountable, constructively, but consistently. You don't wait for the next meeting to surface a problem.
- Influential and relationship-driven. You know that infrastructure work gets: done through trust, not authority. You build strong relationships across engineering teams, understand what motivates different stakeholders, and use that context to create alignment
- AI-first in how you work. You don't just talk about AI, you use it daily to: move faster, work smarter, and do more with less. You bring that mindset to the teams you work with and actively look for opportunities to automate, accelerate, and improve how programs are run.
- Comfortable with high volume and ambiguity. You can manage many parallel: workstreams without losing track of any of them, and you don't need a clean problem statement to get started.
- Clear and direct communicator. You tailor your message by audience,: engineering teams need different information than engineering VPs, and you make it easy for leadership to understand status and make decisions quickly.
- Outcome-oriented. You measure success by realizing the impact and what: improves, not by the quality of your tracking.
