Skip to main content
All jobs

Employer listing

Technical Support Engineer

PostHog

remote · full time

Salary not specified

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 and have since shipped tools including:

  • A suite of analytics and observability tools (product analytics, replay vision, AI observability, and error tracking)
  • PostHog MCP for querying and acting on product and business data
  • Data warehouse for custom SQL insights

We are product-led, default alive, well-funded ($180m+ raised), and natively remote.

Who We’re Looking For

We're looking for a Technical Support Engineer who loves helping customers and won't leave a problem alone until it's solved. You're an engineer who happens to do support. You pick up new things fast, take feedback well, and are comfortable tackling problems nobody has seen before.

What You’ll Be Doing

  • Helping customers across all of PostHog's products, in the app and in shared Slack channels with larger customers
  • Owning tickets from beginning to end and keeping customers updated along the way
  • Shipping fixes to the PostHog codebase and docs when you find something broken or unclear
  • Becoming the support expert for a product area: owning its queue, working closely with the engineering team, and spotting patterns that turn into fixes
  • Improving support tooling and workflows built on PostHog itself
  • Passing customer pain points and feature requests to engineering teams with actionable context

What You Won't Be Doing

  • Routing tickets or forwarding difficult questions just because they are hard
  • Saying "that's not my job"
  • Pasting AI answers back to customers without testing and human verification

Requirements

  • Experience in at least two programming languages (via previous roles, side projects, etc.)
  • Experience debugging unfamiliar code or systems, verifying that fixes work
  • Clear, concise writing that explains complex fixes clearly
  • Thorough investigations conducted without slowing down response times
  • Ability to prioritize and context switch across a busy multi-product queue

Nice to Have

  • Experience supporting similar products (e.g., analytics, session replay, feature flags, experiments, or LLM observability)
  • A background in support, teaching, product, or explaining technical concepts to people