• architect, build, and evolve the developer experience for Meraki's Cloud Engineering teams • work within a team distributed across the US and UK and collaborate with other teams across SRE and Cloud Engineering • shape the day-to-day operations of Meraki's cloud • enable engineers to easily, safely, and confidently experiment on and build great products • lead the design and evolution of critical infrastructure for building, testing, and deploying our cloud applications • take the lead on complex problem resolution and debugging of internal and vendor-supplied tools • influence and drive operational excellence within the organization • learn and understand the priorities and practices of other engineering teams to design systems that work for them • partner with engineering leadership to define roadmaps, reporting on productivity gains and platform health to the SVP level • lead complex troubleshooting, perform blameless postmortems, and champion sustainable on-call practices across the organization

• Designing, implementing, and maintaining cloud infrastructure • Ensuring the reliability and performance of applications • Working closely with development teams to establish CI/CD pipelines • Automating deployment processes • Contributing to critical projects from anywhere in the USA

• Read, debug, and contribute to production C#/.NET code to diagnose and fix app-level reliability issues. • Identify and resolve memory leaks, thread pool exhaustion, and GC pressure before they manifest as incidents. • Partner with application engineers to embed reliability into new feature design and deployment practices. • Instrument .NET services with distributed tracing and structured logging to surface runtime anomalies early. • Operate and optimize EC2 Auto Scaling, ECS Fargate, and Lambda workloads — with clear judgment on when each is the right fit. • Build and maintain infrastructure-as-code using CloudFormation or CDK for consistent, reproducible environments. • Automate operational tasks, deployment pipelines, and disaster recovery procedures. • Continuously reduce toil through tooling and automation, freeing the team for higher-impact engineering work. • Manage RDS SQL Server deployments including Multi-AZ failover configuration and read replica setup. • Operate backup and point-in-time recovery (PITR) processes and validate restore procedures regularly. • Diagnose and resolve performance issues: slow queries, missing indexes, and blocking chains. • Capacity plan and scale database infrastructure to support transaction volume growth. • Build and maintain observability stacks using CloudWatch metrics, log insights, and alarms; AWS X-Ray for distributed tracing. • Own service health dashboards, SLOs/SLIs, and drive data-driven reliability improvements. • Design alerts that surface signal — not noise — and ensure on-call responders have the context to act quickly. • Conduct root cause analysis (RCA) on incidents and lead blameless post-mortems to capture lessons and prevent recurrence. • Design and maintain secure AWS network topologies: VPCs, subnets, security groups, and NACLs. • Configure and manage ALB/NLB routing, Route 53 DNS, and TLS certificate lifecycle via ACM. • Author and review least-privilege IAM policies; audit roles and resource-based policies for over-permissioning. • Support compliance and security controls relevant to a PCI-regulated payments environment. • Participate in on-call rotation to respond to production incidents and drive swift resolution. • Define and track error budgets; use them to balance velocity and reliability investment. • Communicate status updates clearly during incidents and coordinate cross-functional response. • Maintain and improve runbooks, escalation paths, and on-call health over time. • Collaborate with platform engineering teams on architecture decisions and scalability requirements. • Share observability and reliability best practices with application teams. • Mentor engineers on SRE principles and operational excellence.

• Own fleet reliability engineering: define availability targets, measure them honestly, and close the gap. • Run root cause analysis on the fleet's worst incidents and drive corrective actions to done across every site. • Build the failure data pipeline, facility and hardware both, that turns incident history into engineering priorities. • Set the maintenance strategy (reliability-centered, condition-based) so the fleet spends effort where the failure data says to.