Application window expected to close on 1/15/2025
Cisco Meraki, a division of Cisco Networking, is a cloud-managed IT company and leader in cloud-controlled Wi-Fi, routing, and security. Our intuitive platform enables organizations of all sizes to deliver customer and employee experiences at scale. To provide best-in-class technologies to our customers, we’ve created an unrivaled company culture for our employees. One where diverse backgrounds, perspectives, and experiences shape our work and fuel our evolution. One that is collaborative, flexible, and inclusive and provides employees with the autonomy to develop technology that’s accessible and secure for everyone.
The SRE Engineering Enablement Team, part of the SRE Engineering Enablement org at Meraki supports our CI Platforms, Developer Environments, tools, automation and processes that facilitate developers’ day to day work. We support the entire software development lifecycle (SDLC), including core developer tools and environments, build tools, code review, artifact management, CI, education, and documentation. Our customers are all engineers at Meraki.
As a Senior Site Reliability Engineer, you will architect, build, and evolve the developer experience for Meraki’s Cloud Engineering teams. You will work within a team distributed across the US and UK and collaborate with other teams across SRE and Cloud Engineering. Your decisions will shape the day to day operations of Meraki’s cloud, and enable our engineers to easily, safely, and confidently experiment on and build great products!
Responsibilities:
- 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.
- Work on cross-functional initiatives within Cloud Engineering and with non-technical stakeholders.
- Practice sustainable incident response (on call rotation) and blameless postmortems.
Source ⇲
