Site Reliability Engineer, US - Central/Eastern Timezone

Job not on LinkedIn

🔥 0 minutes ago

Apply Now

Find Similar Remote Jobs

Set Up Email Alert For New Jobs

📊 Check your resume score for this job

Improve your chances of getting an interview by checking your resume score before you apply.

Upload Resume

PostHog

WebsiteLinkedInAll Job Openings

11 - 50 employees

Founded 2020

☁️ SaaS

⚡ Productivity

🏢 Enterprise

SaaS • Productivity • Enterprise

PostHog is a comprehensive platform that empowers developers to build successful products by providing tools for product analytics, web analytics, session replay, feature flags, experiments, and surveys. It integrates seamlessly into existing workflows, offering data pipelines and warehousing solutions that synchronize with popular platforms like Stripe, Hubspot, Zendesk, and more. With PostHog, teams can safely roll out new features, run experiments with statistical significance, and gather in-depth insights with AI and LLM products. The platform is built with full API access, enabling complete control over customer data. PostHog scales with businesses from startups to growth stages, making it a versatile tool for engineering teams seeking to streamline their data operations while focusing on product development.

📋 Description

• You won’t be in a typical “keep the lights on” SRE role. The work is about turning a fast-growing, stateful system into a predictable, well-automated platform. (provisioning, scaling, rebalancing, recovery) That means reducing operational stress, designing safe automation for traffic-heavy workloads, and building the tooling and patterns that let the system scale without scaling human effort. • You'll work on the kind of problems that only show up at large scale (petabytes of data, thousands of cores, constant ingestion) across a multi-region, multi-account AWS platform running many services on Kubernetes. • 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. • You'll have room to design and automate, not just respond to alerts. You should join this team if you like deep ownership of production systems and enjoy building the platform layer that everything else runs on.

🎯 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 have: 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

🏖️ Benefits

• 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.