PostHog
Site Reliability Engineer (Pacific timezone)
Rol remoto de Cloud Foundations con fit claro de ubicación del candidato.
Publicado8 jul 2026
Países elegibles1 país aceptado
Señal de seniorityNivel abierto
Modelo de trabajoRemoto
Ubicaciones aceptadas para candidatos
Estados Unidos
Resumen del rol
Site Reliability Engineer (Pacific timezone)
Requisitos y responsabilidades
Contenido del rol extraído en secciones para revisar más rápido.
About PostHog
- PostHog Code, the only AI devtool that understands your product, not just your codebase.
- A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
- PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
Things we care about
- Transparency: Everyone can read about our roadmap, how we pay (or even let go of) people, our strategy, and how we work, in our public company handbook. Internally, we share revenue, notes and slides from board meetings, and fundraising plans, so everyone has the context they need to make good decisions.
- Autonomy: We don’t tell anyone what to do. Everyone chooses what to work on next based on what's going to have the biggest impact on our customers, and what they find interesting and motivating to work on. Engineers lead product teams and make product decisions. Teams are flexible and easy to change when needed.
- Shipping fast: Why not now? We want to build a lot of products; we can't do that shipping at a normal pace. We've built the company around small teams – autonomous, highly-efficient groups of cracked engineers who can outship much larger companies because they own their products end-to-end.
- Time for building: Nothing gets shipped in a meeting. We're a natively remote company. We default to async communication – PRs > Issues > Slack. Tuesdays and Thursdays are meeting-free days, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.
- Ambition: We want to solve big problems. We strongly believe that aiming for the best possible upside, and sometimes missing, is better than never trying. We're optimistic about what's possible and our ability to get there.
- Being weird: Weird means redesigning an already world-class website for the 5th time. It means shipping literally every product that relates to customer data. It means building an objectively unnecessary developer toy with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.
Who we're looking for
- Enthusiastic drivers. We need proactive people that can fully own projects and get them done, and know to get help when needed. "Are we there yet?" is the wrong question.
- Optimistic problem solvers. Things get hard here sometimes, whether it's scaling, shipping complex products, handling a stream of support requests, or trying to ship something that touches multiple teams. We need people who won't get disheartened, and will collaborate, iterate, and ship their way out of anything.
- Grown ups. We’re an international bunch of weirdos, but one thing unites us: everyone is kind, considerate, and professional towards each other. This isn't about age or experience, it's about being low-ego, flexible, and respectful.
- Genuine builders. PostHog is full of people who just love building stuff, people who would still be building software even if there wasn't a paycheck at the end. If this sounds like you, we should talk.
What you'll be doing
- Operating EKS clusters across several environments with Karpenter autoscaling, Cilium networking, and ArgoCD-driven GitOps deployments
- Managing and evolving a multi AWS account organization, provisioning, networking, access control, and cross-account connectivity
- Maintaining the Terraform/Terragrunt IaC platform - modules, automated plan-on-PR / apply-on-merge pipelines, and safe patterns for shared infrastructure
- Improving operational tooling around deploys, schema changes, backups, restores, and incident response
- Reducing operational load by identifying repeat pain points and eliminating them through code and self-healing automation
- Optimizing cloud spend as you go
- Participating in on-call and incident response, with a strong focus on making incidents rarer over time
Requirements
- Deep hands-on experience with Kubernetes in production (EKS preferred). You've debugged node pressure, networking issues, and deployment failures at scale (thousands of nodes)
- Strong experience operating production infrastructure on AWS. Not just one account, but understanding organizational boundaries, IAM, and networking between many
- Experience automating infrastructure using Terraform or Terragrunt at scale, including module design and state management
- Solid understanding of Linux systems (disk, memory, networking, failure modes)
- Experience supporting stateful systems (databases, queues, storage systems, etc.)
- Ability to debug and reason about performance and reliability issues in production
- You're comfortable owning systems end-to-end, including on-call responsibilities
Nice to haves
- Experience with GitOps workflows (ArgoCD) and CI/CD pipelines (GitHub Actions)
- Experience with building AI agent-enabled base-level infra services for teams that move fast
- Familiarity with multi-region infrastructure and the consistency/availability tradeoffs that come with it
Roles similares
Mantén una lista de respaldo.
Stack
Usa estas tags para comparar roles remotos similares.
Elegibilidad de ubicación
Candidatos deberían aplicar solo cuando el país del perfil aparece aquí.
Tu perfilPaís no definidoInicia sesión para comparar tu país con este rol.
Flujo de contratación
WithMira muestra el rol y luego envía candidatos a la aplicación de la empresa.
1Revisa fit del rol, stack y elegibilidad de ubicación en WithMira.
2Abre la página de aplicación de la empresa desde el link rastreado.
3Guarda el rol o suscríbete a oportunidades similares antes de salir.