Site Reliability Engineer (US - Pacific time)

posthog· 10 open roles

San Francisco, CA On-siteFullTime2 months ago

Salary

Undisclosed

Experience

Mid

Job Type

FullTime

Posted

2 months ago

Apply Now

Boost your chances at posthog

Tailor your resume to this exact job and generate a matching cover letter in about 60 seconds with JobEase — our AI application assistant.

ATS-optimized resume
Personalized cover letter
Match score & keyword gaps

Tailor my application

Free to start · no card required

Get more other jobs in your inbox

Verified daily — no ghost listings.

About This RoleAI processing…

About PostHog PostHog is your product’s context layer. It ingests and stores your analytics, errors, replays, and business data so you and your agents can query and act on it. We launched out of Y Combinator's W20 cohort . We've since shipped more than a dozen products, including: A suite of analytics and observability tools, including product analytics , replay vision , AI observability , and error tracking PostHog MCP for users and their agents to query and act on their product and business data Data warehouse so users can query product and customer data together using custom SQL insights. W

Key Responsibilities

1
Default alive . Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
2
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.
3
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.
4
We raise money to push ambition and grow faster, not to keep the lights on.
5
This will be the most productive job you've ever had.
6
We need people who won't get disheartened, and will collaborate, iterate, and ship their way out of anything.
7
What you'll be doing You won’t be in a typical “keep the lights on” SRE role.

Requirements

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

Perks & 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.

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.