Senior CloudOps & Site Reliability Engineer (Seattle)

MangoApps runs an enterprise SaaS platform that thousands of customers depend on every day. We're hiring a senior, hands-on engineer to own the reliability, availability, security, and performance of that platform in production, primarily on AWS.

This is a deep individual-contributor role, not a management track. You'll spend your time in the systems: tuning infrastructure, building observability, automating away toil, and leading the technical response when production is on the line. You'll influence how the rest of engineering builds and operates reliable services through your work and your judgment, not through a reporting line.

If you get satisfaction from understanding a production system end to end, finding the real root cause instead of the convenient one, and making the next incident less likely, this role is built for you.

Who you are:

• 5+ years of hands-on Cloud Operations and Site Reliability Engineering, operating production-scale SaaS (not pre-production or internal-only systems).
• You operate AWS at production scale today and can speak in specifics about AWS compute, networking, IAM, EKS/Kubernetes, and the operational realities of running real workloads there. This is a hard requirement.
• A second cloud (Google Cloud or Azure) is a plus, not a substitute. We value it, but AWS depth is what the role is focused on.
• You debug Linux at the level of why is this latency spike happening, not just restart the service.
• You reach for automation by reflex. Manual operational work bothers you, and you've built the tooling to remove it.

What will you own:

• Reliability & incident response - Keep the platform available and performant. Define and continuously sharpen monitoring, alerting, and observability. Lead production troubleshooting, drive root-cause analysis, and run post-incident reviews that actually change the system afterward. Participate in the on-call rotation for the services you own.
• AWS infrastructure & operations - Design, deploy, and optimize our AWS infrastructure - compute, storage, networking, DNS, load balancing, and security services. Drive architectural improvements to enhance reliability, scalability, performance, and cost. Own disaster recovery and business-continuity processes, and prove they work before you need them.
• Containers & orchestration - Build and operate containerized workloads on Docker with a focus on security, performance, and predictable scaling across environments.
• Automation & Infrastructure as Code Provision - Build the scripts and tooling that make operations boring and repeatable.
• CI/CD & release engineering - Maintain CI/CD pipelines and deployment automation. Partner with engineering to make releases safer, faster, and easier to roll back.
• Security & compliance - Apply cloud security practices across IAM, network security, secrets management, and vulnerability remediation. Keep infrastructure aligned to our internal security standards and compliance obligations.

Must have

• Production-scale experience operating cloud infrastructure on AWS.
• Deep Linux systems administration, troubleshooting, and performance tuning.
• Hands-on Docker in production
• Solid networking fundamentals: VPCs, routing, load balancing, DNS, VPNs, and security controls.
• Monitoring and observability with tools such as Prometheus, Grafana, ELK/OpenSearch, Datadog, or equivalents.
• Scripting and automation in Bash, Python, or similar.
• Git-based workflows and CI/CD pipelines; config management with Ansible or Puppet.
• Strong incident management and root-cause analysis instincts, with a bias toward fixing the system, not the symptom.

Nice to have

• Production experience on a second cloud (Google Cloud or Azure).
• IAM / SSO experience (SAML, OAuth, Okta, or similar).
• Multi-region or multi-cloud operations at scale.
• Background in cloud security, compliance, and governance practices.

What success looks like

• Sustained, high platform uptime against clear SLOs.
• Faster incident detection and resolution, with recurring failure classes systematically driven down.
• More automation and meaningfully less manual operational toil quarter over quarter.
• Observability is good because it lets the team see problems before customers do.
• Engineering teams ship reliably because the operational foundation is solid.

What We're Looking For in You

• Ownership: You take accountability for outcomes, not just tasks.
• Problem solver: You enjoy diagnosing and resolving complex infrastructure and production challenges.
• Continuous learner: You stay current with evolving cloud, automation, and reliability practices.
• Collaborative: You work effectively across teams and communicate clearly, both in routine operations and in the middle of a critical incident.
• Customer-focused: You understand that infrastructure reliability directly shapes customer experience and business success.