> Markdown version of [/jobs/ext/3606099-senior-manager-site-reliability-engineering](https://www.wearedevelopers.com/jobs/ext/3606099-senior-manager-site-reliability-engineering). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Manager, Site Reliability Engineering - **Company:** Invoca, Inc. - **Location:** New York, NY, United States - **Experience:** Expert - **Salary:** $190,000.0 - $250,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Audio Signal Processing, Audit Trail, Cloud Computing, Cyber Security, Continuous Delivery, Linux, DevOps, Integrated Development Environments, MySQL, Reliability Engineering, Prometheus, Policy as Code, Data Storage Technologies, Grafana, Kubernetes, Terraform - **Published:** October 7, 2026 - **Apply:** https://diversityjobs.com/career/18553056/Senior-Manager-Site-Reliability-Engineering-California-Los-Angeles ## About the Role We're looking for an operator who moved into leadership: someone who has grown infrastructure teams, holds a high bar, and is deeply invested in the people on them. You're the right shape for this role if you have: * 5+ years hands-on in an SRE, DevOps, systems, or infrastructure engineering role, and 3+ years directly managing teams in one of those disciplines. * Real depth across the platforms we run on: + Cloud infrastructure in AWS/GCP + Kubernetes + Infrastructure as code (Terraform) and policy-as-code for governing it + GitOps and continuous delivery (ArgoCD and Atlantis) + Observability (Prometheus, Grafana, ELK) + Linux (configured via Chef) + MySQL * Strong opinions about infrastructure design and automation, held with an open mind, and the judgment to use both what exists today and where the industry is heading to guide decisions. * Significant experience as a hiring manager - you know what strong looks like at this level because you've hired it - and a track record of inheriting a team and raising its performance through development, hiring, and clear expectations. * You can work alongside highly skilled external specialists, able to hold your own technically, and can hold them to a high bar. * A working point of view on AI in infrastructure work: where it genuinely accelerates the work and where it doesn't, what output you can trust and what needs a gate, and how to raise a whole team's fluency rather than leaving it to individuals. * Effective in a remote-first, asynchronous culture, and able to report complex technical progress in terms a non-engineering audience can act on. ## Description Invoca is an AI-powered revenue execution platform that brings together marketing, commerce, and contact center teams to turn every customer interaction into measurable, profitable growth. Join our dynamic, fast-growing team, where innovation and collaboration are at the core of our culture. About the team Reliability Engineering builds and runs the platform the rest of Invoca ships on. Real-time call routing, audio processing, transcription, and data storage all run on the infrastructure this team owns, across the US and EU, under PCI, SOC 2, and ISO obligations. Invoca believes in service ownership. Engineering teams are on call 24/7 for what they build, not just SRE. Leadership acts as an escalation point and joins the incident commander rotation roughly two days per month. About the role Invoca is building an agentic development environment, one where software is designed, written, tested, deployed, and operated with AI as a first-class collaborator. Infrastructure is where that gets real or doesn't: agents move fast, and the platform underneath them is what makes that safe. The fastest-growing consumer of infrastructure operations isn't a person clicking through a portal, it's software. That's what we're building for. You help shape where it goes next. Getting there starts with shedding weight: finding where we can leverage partners and managed services, building self-service paths engineers and agents can both use safely, and retiring what we shouldn't be running at all. This is not a caretaking role. You'd inherit a capable team with deep knowledge of our systems, being asked to work differently than it has. You bring outside perspective: you've built and run infrastructure teams elsewhere and you arrive with a specific point of view on what great looks like. This position reports to the Senior Director, Infrastructure & Security. What you'll do Lead the evolution of Invoca's infrastructure * Decide what we run and what we don't. We keep a system in-house only when it differentiates us. Apply that test system by system and find the right home. * Land the move from self-hosted to managed Kubernetes making sure the operational expertise stays with us. * Reduce what the team carries operationally so capacity goes toward building and not maintenance. * Own the technical direction for the platform your team runs, partnering with Developer Enablement, Infosec, and architecture where decisions reach beyond it. Lead the team and own the 3-month delivery plan * Lead a team of 8 SREs with deep systems knowledge. Set a clear bar, give people the feedback and context to hit it, and invest in the growth of the team. * Own and execute the rolling 3-month delivery plan: translate infrastructure strategy into clear priorities, navigate ambiguity, and hold full accountability for shipping high-impact work. * Represent SRE where infrastructure decisions get made, and be in architecture and planning conversations before your team is needed. * Work alongside a leadership team including a tech lead, architect, and your engineering management cohort to solve problems bigger than any one team. Build infrastructure with agents in mind * Drive a pipeline, not a bottleneck. Work the team does on another team's behalf becomes a callable API with a policy decision attached - invoked by an agent or a person with the same governance and the same audit trail. * Extend policy and scanning controls so agent-driven infrastructure change is safe by default rather than safe by review. * Define clean boundaries and contracts between infrastructure and the product teams that build on it. * Win on adoption, not mandate. The path with policy and audit attached has to also be the fastest one available for an agent or a person. Build for the agentic development era * Use AI and agentic workflows in how the team builds and operates infrastructure: agent-assisted development, automated incident detection and triage, self-healing deployments, drift and policy detection. * Establish safe, observable, and auditable ways to bring AI into how we build and run infrastructure, and help the teams around you adopt them with confidence. Standardize and multiply engineering leverage * Build shared practices and tooling for infrastructure that every team can adopt, replacing one-off, team-specific approaches. * Treat infrastructure as a product with internal users: define adoption goals and measure whether teams are actually better off because of your work. Connect the infrastructure to business outcomes * Translate technical decisions in the platform into terms leadership and product teams care about: velocity, cost, risk, customer trust, and revenue impact. * Partner with engineering and product leadership to prioritize your work based on measurable business and customer impact, not technical elegance alone., * Direct and kind. You say the hard thing in the room, not afterward, and you receive feedback the same way. * High agency. You act without waiting for permission on reversible decisions and own the outcome either way. No work is beneath you. * You raise the bar. You think from first principles rather than accepting how things have been done, and you don't reward work that's merely fine. * You make it safe to not know. A high bar and a safe team are not in tension - people have to be able to ask, dissent, and be wrong without paying for it, or you never hear the thing you needed to hear. Nobody is made small for the gap between where they are and where the bar is. * You bring intensity. Deadlines in days where the work allows, a rough first version to get real feedback, risk flagged early, and you finish what you start. * You dig for the real problem. When someone asks for something, you understand what they're trying to accomplish before responding. * You disagree productively and commit fully. Decisions you deliver to your team are yours, not something handed down. How success will be measured Within 12 months, success in this role will look like: * The team's performance is legible without you in the room. Reliability, delivery, and operational load metrics are reviewed regularly and someone outside SRE could tell whether the team and the platform had a good month. * When asked, internal customers are delighted when using our infrastructure and working with our team. * The team builds for those using the platform, not those running it. What gets prioritized traces back to what other teams actually need, dates are met reliably enough that people plan around them, and the volume of work routed to your team for execution has materially dropped. * Agents are a first-class consumer of the platform. Routine infrastructure change happens through interfaces a person or an agent uses identically, with the same identity, policy, and audit trail. * Capacity freed by the platform transition went somewhere visible - reinvested in work the team chose, not absorbed into maintenance that grew to fill it. * The team's work has a demonstrable, articulable connection to business or customer outcomes.