5m ago
Backend Engineer
Transak·Node.js · Fintech
🏢On-site
|Bangalore, Indiaalgorithmsapidata_science/data_engineeringdistributed_systems+9
Customer Success Manager
PostHog | Sales/Customer Success/Key Account Management | Software
Fully Remote
Full Time
$226k - $247k USD/yr
Source not independently verified
Confirm the company and recruiter through an official company domain before applying. Never pay money, share one-time codes, sign out of your Apple or Google account, install apps or configuration profiles, or run code from a repository sent by a recruiter.
Customer Success EU Team
Location
Remote (EMEA)
Timezone(s)
GMT +2 to GMT
About PostHog
Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
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.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
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.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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
A customer-obsessed person to take care of a large number of our larger customers. You’ll engage with them regularly to ensure their continued retention and growth.
You'll need to be incredibly helpful, technical enough to help our customers, and solve real problems without asking a sales engineer for help.
No going away and asking an expert by default. You will be the expert!
You’re great at building relationships with customers, understanding their priorities, and ensuring they are set up for success both today and in the long term.
What you’ll be doing
You’ll be the face of PostHog for anywhere from 25-40 paying customers in the $20k-$100k+ ARR range. Some of these customers will have come through our sales process and be well-known to us, while others will have self-served and never talked to us before!
It'll be your responsibility to ensure that both types of customers stay with us. That means taking care of the technical side (debugging, config advice), the commercial side (pricing questions, credit renewals), and the human side (multi-threading, managing escalations).
Day to day, it looks like:
Building relationships with your users. You should know who the key people are at each company, and they should know you.
Owning their feedback and making sure it gets to the wider PostHog team.
Investigating technical issues. You're the first person to dig into customer issues, often solving them yourself rather than immediately passing to support.
Being super responsive to their Slack messages, support tickets, and emails.
Being their favorite ever Customer Success person to work with!
More broadly, you'll watch product usage and revenue data so customer health doesn't move into the red, and act early when it does. Your aim is to never be surprised when a customer tells us they are leaving. If you want to build automations to help you do your job here, go for it!
Read this blog to find out more!
This role comprises a base salary component, plus a bonus for hitting/exceeding customer retention targets. The salary in our compensation calculator is the OTE (80/20).
What you won’t be doing
❌ Taking someone with you to every customer meeting. It’ll normally be you and the customer. Very occasionally, you might bring a product engineer with you, e.g. if they are one of our first customers paying for a new product.
❌ Aggressively pursuing expansion opportunities. This role is primarily focused on retention.
Requirements
Technically capable. You don't need to be an engineer, but you should be comfortable working with code. You troubleshoot issues customers run into (and sometimes even raise PRs yourself to fix bugs) and advise on configuration best practices across all PostHog products.
You get how product teams work. You know the roles, how they collaborate, and how they ship features - so you can help them use PostHog to solve real problems. For example, why running experiments matters, how to use product analytics and session replay together to find drop-off points and test fixes, or when error tracking helps teams ship better.
Strong customer focus. You need to help our users and remove any blockers to them using PostHog effectively – not route them elsewhere and move on.
Able to work at scale. You'll have around 40 customers. You can't treat them all the same, and you won't try to.
Nice to have
Experience working with similar technologies, i.e. developer tools more broadly, or specifically product analytics, session replay, feature flags, A/B testing, data warehouses, or data pipelines.
You’ve been in a Pre-sales or Technical Account Manager role before, bringing both technical expertise and commercial acumen.
If you have a disability, please let us know if there's any way we can make the interview process better for you - we're happy to accommodate!
Salary
We have a set system for compensation as part of being transparent. Salary varies based on location and level of experience.
Location
(based on market rates)Country
Region
Level
Step
Salary calculator
- Benchmark (United States - San Francisco, California) $237,375
- Level modifier 1
- Step modifier 0.95 - 1.04
Salary $225,506 - $246,870+ significant equity
We are open to paying well beyond these ranges for exceptional talent. If this is you, please apply.
Benefits
- Generous, transparent compensation & equity
- Unlimited vacation (with a minimum!)
- Two meeting-free days per week
- Home office
- Coworking credit
- Private health, dental, and vision insurance.
- Training budget
- Access to our Hedge House
- Carbon offsetting
- Pension & 401k contributions
- We hire and pay locally
- Company offsites
Get more details about all our benefits on the Careers page.
Your team's mission and objectives
Grow and retain the number of paying customers who fit our Ideal Customer Profile.
Q3 2026 Goals
- Hit CSM Net Revenue Retention (NRR) of 110% using quarterly comparison method (CSMs)
- Hit and track all team revenue goals (Dana)
Replace myself with Claude Ben SmithBen Smith
PostHog is investing heavily in AI tooling and an MCP first approach. To be a pioneer (and potentially expose gaps in our approach) this quarter I will exclusively use LLM tooling to prepare for some customer calls.
We'll know we're successful when: I will ship at least one skill, having used it to prepare for three customer check-in calls, and share my lessons learned internally.
Enable customers with custom skills Christophe Eynius TranbergChristophe Eynius Tranberg
More and more customers are using our MCP as part of their daily workflows. We have a unique understanding of what their challenges are and we have started shipping custom skills. I want to build a way to distribute custom skills to users and make them runnable using the wizard.
We'll know we're successful when: Concierge mode is shipped to production
Make customer feature requests queryable in real time Andre de VriesAndre de Vries
Today feature requests are collated by hand at quarter-end (Simon → engineering), and nobody can ask "what are customers asking for right now?" in between. I'll build a PostHog Signals scout that scans my customer conversations (shared Slack channels + call notes) for feature requests, groups them by theme, and emits them into the Signals inbox, so GTM and CS can pull live customer demand into renewal and roadmap conversations instead of waiting for a quarterly doc. Deliberately scoped to one source and kept low-maintenance to avoid over-building the earlier RFC, and I'll check with the customer analytics team first to avoid overlap.
We'll know we're successful when: The scout runs on a schedule and surfaces grouped feature-request themes into Signals, and at least one renewal or roadmap conversation this quarter pulls from it instead of the quarter-end collation.
Match what ships to the accounts who'd care Ella CullenElla Cullen
PostHog ships faster than any CSM can track. The hard part isn't reading the changelog. It's knowing which update matters for which account. I'll build a system that brings in all our product updates and matches what's shipping to the relevant customers, through the lens of "what does a busy CSM actually want to know?" It'll draw on each customer's PostHog activity + Granola + Slack to stay relevant. The goal is precision, not coverage. Not every account should qualify for an update every week.
We'll know we're successful when: I've used it on my own accounts to generate 5 useful, deployed product-update insights, each good enough it went into a real outreach.
Skill discoverability Dana ZouDana Zou
We're all building skills, but it feels like whether you know about a skill all depends on whether you saw it on Slack. The result is ~10 versions of the same workflow, and we're spending time rebuilding very similar skills. I'll work on this from three angles:
- 1-3 canonical skills for simple-but-manual tasks where a shared version works. e.g. billing page visit analysis, chasing unpaid invoices, renewal prep, and a first-pass account review.
- A
find-skillsskill: Claude checks the store for an existing team skill before building a workflow from scratch, or mid-task ("is there already a skill for what I'm doing?"). - The store as the default home: every skill shared in Slack lands in the store, and I'll regularly re-share and remind people of what's in there!
We'll know we're successful when: canonical skills are in the store and being used by the team, find-skills is shipped and in everyone's setup, and all skills shared in Slack are in our Skills store
Interview process
We do 2-3 short interviews, then pay you to do some real-life (or close to real-life) work.
- 1Application (You are here)Our talent team will review your application
We're looking to see how your skills and experience align with our needs.
- 2Culture interview30-min video call
Our goal is to explore your motivations to join our team, learn why you’d be a great fit, and answer questions about us.
- 3Technical interview45 minutes, varies by role
You'll meet the hiring team who will evaluate skills needed to be successful in your role. No live coding.
- 4Culture & Motivation interview20 minutes, varies by role
You have reached the final boss. It's time to chat with one of our Blitzscale team members.
- 5PostHog SuperDayPaid day of work
You’ll meet a few more members of the team and work on an independent project. It's challenging, but most people say it's fun, and we'll pay you $1,000 for your efforts!
- 6OfferPop the champagne (after you sign)
If everyone is happy, we’ll make you an offer to join us - YAY!
Apply
(Now for the fun part...)
Just fill out this painless form and we'll get back to you within a few days. Thanks in advance!
Required Skills
ab_tetingdebuggingproduct_analyticsslacksqltroubleshooting
Required Languages
🇬🇧 English
Key competency: Sales/Customer Success/Key Account Management