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.
We are:
Product-led. More than 500K 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.
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.
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.
We do not care what your old job title was. We care that you want to talk to customers, own the relationship and help them get more from PostHog.
Some of our best TCSMs used to ship code. Now they ship happy customers. Ex-dev, ex-TAM, ex-something-else? All good, if you want to own customers and not only be near them!
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).
❌ 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.
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.
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!
#LI-DNI
","descriptionPlain":"ABOUT POSTHOG\n\nPostHog 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.\n\nWe launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:\n\n - A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking\n\n - PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data\n\n - Data warehouse https://posthog.com/context-warehouse/managed-warehouse so users can query product and customer data together using custom SQL insights.\n\nWe are:\n\n 1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.\n\n 2. Default alive https://paulgraham.com/aord.html. 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.\n\n 3. 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.\n\nWe're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog. \n\n \n\n\nTHINGS WE CARE ABOUT\n\n - 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 https://posthog.com/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.\n\n - 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 https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.\n\n - Shipping fast: Why not now? https://posthog.com/handbook/values#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 https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.\n\n - 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 https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.\n\n - 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 https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.\n\n\nWHO WE’RE LOOKING FOR\n\n - 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.\n\n - You'll need to be incredibly helpful, technical enough to help our customers, and solve real problems without asking a sales engineer for help. \n\n - No going away and asking an expert by default. You will be the expert!\n\n - 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.\n\n - We do not care what your old job title was. We care that you want to talk to customers, own the relationship and help them get more from PostHog.\n \n - Some of our best TCSMs used to ship code. Now they ship happy customers. Ex-dev, ex-TAM, ex-something-else? All good, if you want to own customers and not only be near them!\n\n\n\n\nWHAT YOU’LL BE DOING\n\nYou’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! \n\nIt'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).\n\nDay to day, it looks like:\n\n - Building relationships with your users. You should know who the key people are at each company, and they should know you. \n\n - Owning their feedback and making sure it gets to the wider PostHog team.\n\n - Investigating technical issues. You're the first person to dig into customer issues, often solving them yourself rather than immediately passing to support.\n\n - Being super responsive to their Slack messages, support tickets, and emails.\n\n - Being their favorite ever Customer Success person to work with!\n\nMore 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!\n\n\n\nRead this blog to find out more! https://posthog.com/blog/customer-success-at-posthog\n\n\n\nThis role comprises a base salary component, plus a bonus https://posthog.com/handbook/cs-and-onboarding/how-we-work#how-contractual-bonus-works---technical-csms for hitting/exceeding customer retention targets. The salary in our compensation calculator is the OTE (80/20). \n\n\n\n\nWHAT YOU WON’T BE DOING\n\n❌ 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. \n\n❌ Aggressively pursuing expansion opportunities. This role is primarily focused on retention. \n\n\n\n\nREQUIREMENTS\n\n - 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. \n\n - 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.\n\n - 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.\n\n - 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.\n\n\nNICE TO HAVE\n\n - 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.\n\n - You’ve been in a Pre-sales or Technical Account Manager role before, bringing both technical expertise and commercial acumen.\n\nIf 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! \n\n#LI-DNI","compensation":{"compensationTierSummary":null,"scrapeableCompensationSalarySummary":null,"compensationTiers":[],"summaryComponents":[]}},{"id":"43dbf072-0fc1-48c9-8c1e-7416db7d4a14","title":"ClickHouse Operations Engineer ","department":"Engineering","team":"ClickHouse","employmentType":"FullTime","location":"Remote","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-08-25T07:00:51.155+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"USA"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/43dbf072-0fc1-48c9-8c1e-7416db7d4a14","applyUrl":"https://jobs.ashbyhq.com/posthog/43dbf072-0fc1-48c9-8c1e-7416db7d4a14/application","descriptionHtml":"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.
We are:
Product-led. More than 500K 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.
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.
ClickHouse is the core piece of infrastructure at PostHog. Every product and customer relies on it to ingest, store, and query data.
We need someone to automate, manage, and maintain ClickHouse as we grow towards capturing trillions of events per year and having one of the world’s largest clusters.
This includes ClickHouse operations and scaling infrastructure, as well as node and instance-level performance optimization. We want to ensure that we have the right hardware deployed at the right time for each workload on ClickHouse.
You'll build systems and automations for the provisioning and scaling of our large ClickHouse clusters, handling over 100 PB's of data. You'll have the ability to investigate and experiment using the latest hardware that cloud providers have to offer in order to find the optimal setup for our solution. And yes, You'll have a budget to do this.
You'll be using Terraform, Ansible, and Kubernetes to automate the dynamic provisioning of instances and work on a bleeding edge ClickHouse implementation, like open format backed tables, and not just maintenance.
We're also building a query optimizer for ClickHouse, which means you will work on query performance tooling.
You bring OLAP Database Experience. This role is focussed on ClickHouse, but if you bring strong experience with other OLAP Databases, that's great. We're looking for people that went into the internals of ClickHouse and other OLAP Databases, not high level users.
You bring experience in automating Dynamic provisioning instances. Strong experience with utilizing Terraform, Ansible and K8s is important.
You bring experience with Scale and Complexity! We're building and operating high-scale complex data storage solutions, we need you to have experience with the challenges this brings.
You bring the Stack we need. We build using Python, Terraform, Ansible, Kubernetes, AWS, and Zookeeper (An alternative to Zookeeper is fine)
You’re ready to do the best work of your career. We have incredible distribution, a big financial cushion and an amazing team. There’s probably no better place to see how far you can go.
If this sounds like you, we should talk.
We are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know.
","descriptionPlain":"ABOUT POSTHOG\n\nPostHog 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.\n\nWe launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:\n\n - A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking\n\n - PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data\n\n - Data warehouse https://posthog.com/context-warehouse/managed-warehouse so users can query product and customer data together using custom SQL insights.\n\nWe are:\n\n 1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.\n\n 2. Default alive https://paulgraham.com/aord.html. 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.\n\n 3. 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.\n\nWe're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog. \n\n \n\n\nTHINGS WE CARE ABOUT\n\n - 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 https://posthog.com/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.\n\n - 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 https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.\n\n - Shipping fast: Why not now? https://posthog.com/handbook/values#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 https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.\n\n - 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 https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.\n\n - 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 https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.\n\n\n\n\nWHAT YOU'LL BE DOING\n\nClickHouse is the core piece of infrastructure at PostHog https://posthog.com/docs/how-posthog-works/clickhouse. Every product and customer relies on it to ingest, store, and query data.\n\nWe need someone to automate, manage, and maintain ClickHouse as we grow towards capturing trillions of events per year and having one of the world’s largest clusters.\n\nThis includes ClickHouse operations and scaling infrastructure, as well as node and instance-level performance optimization. We want to ensure that we have the right hardware deployed at the right time for each workload on ClickHouse.\n\nYou'll build systems and automations for the provisioning and scaling of our large ClickHouse clusters, handling over 100 PB's of data. You'll have the ability to investigate and experiment using the latest hardware that cloud providers have to offer in order to find the optimal setup for our solution. And yes, You'll have a budget to do this.\n\nYou'll be using Terraform, Ansible, and Kubernetes to automate the dynamic provisioning of instances and work on a bleeding edge ClickHouse implementation, like open format backed tables, and not just maintenance.\nWe're also building a query optimizer for ClickHouse, which means you will work on query performance tooling.\n\n\n\n\nYOU’LL FIT RIGHT IN IF:\n\n - You bring OLAP Database Experience. This role is focussed on ClickHouse, but if you bring strong experience with other OLAP Databases, that's great. We're looking for people that went into the internals of ClickHouse and other OLAP Databases, not high level users.\n\n - You bring experience in automating Dynamic provisioning instances. Strong experience with utilizing Terraform, Ansible and K8s is important.\n\n - You bring experience with Scale and Complexity! We're building and operating high-scale complex data storage solutions, we need you to have experience with the challenges this brings.\n\n - You bring the Stack we need. We build using Python, Terraform, Ansible, Kubernetes, AWS, and Zookeeper (An alternative to Zookeeper is fine) \n\n - You’re ready to do the best work of your career. We have incredible distribution, a big financial cushion and an amazing team. There’s probably no better place to see how far you can go.\n\n\n\nIf this sounds like you, we should talk.\n\nWe are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know.\n\n\n","compensation":{"compensationTierSummary":null,"scrapeableCompensationSalarySummary":null,"compensationTiers":[],"summaryComponents":[]}},{"id":"20ab9628-20ff-4ae3-bd6a-46ae7e9dc6b8","title":"Product Engineer","department":"Engineering","team":"Product Engineering","employmentType":"FullTime","location":"Remote","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-09-24T16:56:29.377+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"USA"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/20ab9628-20ff-4ae3-bd6a-46ae7e9dc6b8","applyUrl":"https://jobs.ashbyhq.com/posthog/20ab9628-20ff-4ae3-bd6a-46ae7e9dc6b8/application","descriptionHtml":"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.
We are:
Product-led. More than 500K 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.
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.
We're hiring for a range of roles here. What you end up working on will depend on your exact skillset and preferences, so choose your own adventure.
In general we seek Product Engineers who are:
Enthusiastic drivers. We need proactive people that can fully own projects and get them done, and know to get help when needed. This is what being a product engineer is all about. \"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.
Owning products and features from beginning to end. This means originating ideas based on your intuition, talking to users, and understanding our strategy and goals. It means testing MVPs in production with real users. It means iterating on their feedback, owning pricing, and ensuring the ongoing success of your work.
Collaborating with design (when necessary). Product engineers at PostHog are full stack, so we expect you to ship and own the basic UX of your work using our design system. From there, it's up to you to decide when to collaborate with our design team to iterate and polish the experience.
Talking to users. Good product engineers read feedback from users and iterate quickly. Great product engineers have users they're friendly with, talk with them frequently, bounce ideas off them, and iterate with them when they ship new things.
Doing support. Every week, one person in each engineering team is designated the Support hero. Their job is to investigate and resolve issues reported by customers for their product. Giving users support from real engineers, and shipping fixes and improvements in real-time, is one of the best ways to spark joy in users. This role will also include some on-call time, too.
Writing docs. We have a content team that will collaborate with you on reviewing, polishing, and improving your documentation, but the best person to document a new feature is the person who built it.
You've built things agents actually use. More and more of what we ship is used by agents, not people, and building for them is genuinely different. We want someone who's done it and has the scars: an API an agent can drive, an MCP server, evals, docs written for a machine. Side projects count.
Full-stack experience with relevant technologies – e.g. Python or similar, React or similar, something to do with big data is a bonus.
Experience taking a project from 0 to 1. You might have led a project, been a founder previously, or built an impressive side project.
Strong writing skills. We document everything, most of it publicly. The ability to communicate your ideas and make persuasive arguments is essential.
Have worked at a high-growth SaaS company before.
Extensive knowledge of Django and/or TypeScript-based React.
Experience building AI-native products, or integrating AI into existing software.
We are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know
#LI-DNI
","descriptionPlain":"ABOUT POSTHOG\n\nPostHog 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.\n\nWe launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:\n\n - A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking\n\n - PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data\n\n - Data warehouse https://posthog.com/context-warehouse/managed-warehouse so users can query product and customer data together using custom SQL insights.\n\nWe are:\n\n 1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.\n\n 2. Default alive https://paulgraham.com/aord.html. 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.\n\n 3. 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.\n\nWe're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog. \n\n \n\n\nTHINGS WE CARE ABOUT\n\n - 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 https://posthog.com/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.\n\n - 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 https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.\n\n - Shipping fast: Why not now? https://posthog.com/handbook/values#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 https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.\n\n - 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 https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.\n\n - 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 https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.\n\n\nWHO WE'RE LOOKING FOR\n\nWe're hiring for a range of roles here. What you end up working on will depend on your exact skillset and preferences, so choose your own adventure.\n\nIn general we seek Product Engineers who are:\n\n - Enthusiastic drivers. We need proactive people that can fully own projects and get them done, and know to get help when needed. This is what being a product engineer https://posthog.com/blog/what-is-a-product-engineer is all about. \"Are we there yet?\" is the wrong question.\n\n - 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.\n\n - 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 https://posthog.com/handbook/company/grown-ups, it's about being low-ego, flexible, and respectful.\n\n - 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.\n\n\nWHAT YOU'LL BE DOING\n\n - Owning products and features from beginning to end. This means originating ideas based on your intuition, talking to users, and understanding our strategy and goals. It means testing MVPs in production with real users. It means iterating on their feedback https://posthog.com/handbook/engineering/product-engineering, owning pricing, and ensuring the ongoing success of your work.\n\n - Collaborating with design (when necessary). Product engineers at PostHog are full stack, so we expect you to ship and own the basic UX of your work using our design system https://storybook.dev.posthog.dev. From there, it's up to you to decide when to collaborate with our design team https://posthog.com/handbook/engineering/product-design to iterate and polish the experience.\n\n - Talking to users. Good product engineers read feedback from users and iterate quickly. Great product engineers have users they're friendly with, talk with them frequently, bounce ideas off them, and iterate with them when they ship new things.\n\n - Doing support. Every week, one person in each engineering team is designated the Support hero https://posthog.com/handbook/engineering/support-hero. Their job is to investigate and resolve issues reported by customers for their product. Giving users support from real engineers, and shipping fixes and improvements in real-time, is one of the best ways to spark joy in users. This role will also include some on-call time https://posthog.com/handbook/engineering/on-call-rotation, too.\n\n - Writing docs. We have a content team that will collaborate with you on reviewing, polishing, and improving your documentation, but the best person to document a new feature is the person who built it.\n\n\nREQUIREMENTS\n\n - You've built things agents actually use. More and more of what we ship is used by agents, not people, and building for them is genuinely different. We want someone who's done it and has the scars: an API an agent can drive, an MCP server, evals, docs written for a machine. Side projects count. \n\n - Full-stack experience with relevant technologies https://posthog.com/handbook/engineering/stack – e.g. Python or similar, React or similar, something to do with big data is a bonus.\n\n - Experience taking a project from 0 to 1. You might have led a project, been a founder previously, or built an impressive side project.\n\n - Strong writing skills. We document everything https://posthog.com/handbook/company/culture#we-write-everything-down, most of it publicly. The ability to communicate your ideas and make persuasive arguments is essential.\n\n\nNICE TO HAVE\n\n - Have worked at a high-growth SaaS company before.\n\n - Extensive knowledge of Django and/or TypeScript-based React.\n\n - Experience building AI-native products, or integrating AI into existing software.\n\nWe are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know\n\n#LI-DNI","compensation":{"compensationTierSummary":null,"scrapeableCompensationSalarySummary":null,"compensationTiers":[],"summaryComponents":[]}},{"id":"8dc3f33a-b930-4c54-b4c4-3e6bd2ff28d3","title":"AI Research Engineer","department":"Engineering","team":"PostHog AI","employmentType":"FullTime","location":"Hybrid (UK)","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-08-18T19:01:08.379+00:00","isListed":true,"isRemote":true,"workplaceType":"Hybrid","address":{"postalAddress":{"addressRegion":"","addressCountry":"United Kingdom","addressLocality":"Cambridge"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/8dc3f33a-b930-4c54-b4c4-3e6bd2ff28d3","applyUrl":"https://jobs.ashbyhq.com/posthog/8dc3f33a-b930-4c54-b4c4-3e6bd2ff28d3/application","descriptionHtml":"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.
We are:
Product-led. More than 500K 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.
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.
PostHog is working on a self-driving product and is training its own Deep ML models. To do this, we have a new AI Research team.
We track more products across more dimensions than any other company on Earth. Because of this, we have petabytes of data across events, errors, session replays, revenue data, and more. It’s an exceptionally large amount of data relative to our company size, and we want to use it for our users' benefit. Just imagine how, with the vast amount of data we capture, we can automatically surface insights and suggest fixes.
As an AI Research Engineer, you will play a substantial part in making this happen. This team is brand new, so you will have real autonomy, be close to customers, and greatly influence what we actually ship.
On the finance side, we have around $150M on our balance sheet, we’re \"default alive,\" and we have a real business that has been scaling rapidly and running exceptionally efficiently with good margins for six years. We invest in what we believe moves the needle.
You'll be part of a team that researches what's next and what's better, and actually brings it into production.
Areas we’re exploring
Session replay analysis: We already detect issues in replays, but doing so is expensive and doesn’t scale. With better models (and a huge amount of DOM mutation data), we think we can make this faster, cheaper, and best-in-class.
User behavior prediction: Identifying drop-offs, suggesting improvements, and potentially improving conversion rates automatically without heavy manual analysis or agent overhead.
Synthetic user testing: Simulating users to catch confusing flows or breakages before release. If this works, it could remove one of the biggest bottlenecks in modern engineering: testing (rather than writing code).
A PhD is a plus, but a strong background in math is a must, or you have previous experience training models (strong math skills are still required).
Strong PyTorch experience.
Strong ability to code in Rust, CUDA, or C (with a preference for Rust).
Solid understanding of Transformers (not the movies).
A product mindset. you’ll be building things!
This is a unique role within PostHog and, as such, is a hybrid-remote position based out of our London office.
Pure theoretical expertise: this is not a Jupyter notebook job.
Someone who just wants to do research and publish. Yes, you can publish, but shipping takes priority.
We are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know
#LI-DNI
","descriptionPlain":"ABOUT POSTHOG\n\nPostHog 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.\n\nWe launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:\n\n - A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking\n\n - PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data\n\n - Data warehouse https://posthog.com/context-warehouse/managed-warehouse so users can query product and customer data together using custom SQL insights.\n\nWe are:\n\n 1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.\n\n 2. Default alive https://paulgraham.com/aord.html. 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.\n\n 3. 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.\n\nWe're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog. \n\n \n\n\nTHINGS WE CARE ABOUT\n\n - 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 https://posthog.com/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.\n\n - 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 https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.\n\n - Shipping fast: Why not now? https://posthog.com/handbook/values#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 https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.\n\n - 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 https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.\n\n - 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 https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.\n\n\nWHO WE'RE LOOKING FOR\n\nPostHog is working on a self-driving product and is training its own Deep ML models. To do this, we have a new AI Research team.\n\nWe track more products across more dimensions than any other company on Earth. Because of this, we have petabytes of data across events, errors, session replays, revenue data, and more. It’s an exceptionally large amount of data relative to our company size, and we want to use it for our users' benefit. Just imagine how, with the vast amount of data we capture, we can automatically surface insights and suggest fixes.\n\nAs an AI Research Engineer, you will play a substantial part in making this happen. This team is brand new, so you will have real autonomy, be close to customers, and greatly influence what we actually ship.\n\nOn the finance side, we have around $150M on our balance sheet, we’re \"default alive,\" and we have a real business that has been scaling rapidly and running exceptionally efficiently with good margins for six years. We invest in what we believe moves the needle.\n\n\n\nWHAT YOU'LL BE DOING\n\nYou'll be part of a team that researches what's next and what's better, and actually brings it into production.\n\n\nAreas we’re exploring\n\n - Session replay analysis: We already detect issues in replays, but doing so is expensive and doesn’t scale. With better models (and a huge amount of DOM mutation data), we think we can make this faster, cheaper, and best-in-class.\n\n - User behavior prediction: Identifying drop-offs, suggesting improvements, and potentially improving conversion rates automatically without heavy manual analysis or agent overhead.\n\n - Synthetic user testing: Simulating users to catch confusing flows or breakages before release. If this works, it could remove one of the biggest bottlenecks in modern engineering: testing (rather than writing code).\n\n\nJOB REQUIREMENTS\n\n - A PhD is a plus, but a strong background in math is a must, or you have previous experience training models (strong math skills are still required).\n\n - Strong PyTorch experience.\n\n - Strong ability to code in Rust, CUDA, or C (with a preference for Rust).\n\n - Solid understanding of Transformers (not the movies).\n\n - A product mindset. you’ll be building things!\n\n - This is a unique role within PostHog and, as such, is a hybrid-remote position based out of our London office.\n\n\nWHAT WE’RE NOT LOOKING FOR\n\n - Pure theoretical expertise: this is not a Jupyter notebook job.\n\n - Someone who just wants to do research and publish. Yes, you can publish, but shipping takes priority.\n\nWe are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know\n\n \n\n#LI-DNI\n\n","compensation":{"compensationTierSummary":null,"scrapeableCompensationSalarySummary":null,"compensationTiers":[],"summaryComponents":[]}},{"id":"1464036f-94d5-4dbd-aef8-fe99246a26d4","title":"Site Reliability Engineer (US - Pacific time)","department":"Engineering","team":"Cloud Foundations","employmentType":"FullTime","location":"San Francisco, CA","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[{"location":"Remote (US)","address":{"postalAddress":{"addressCountry":"United States"}}}],"publishedAt":"2026-08-06T08:48:53.622+00:00","isListed":true,"isRemote":false,"workplaceType":"OnSite","address":{"postalAddress":{"addressRegion":"California","addressCountry":"United States","addressLocality":"San Francisco"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/1464036f-94d5-4dbd-aef8-fe99246a26d4","applyUrl":"https://jobs.ashbyhq.com/posthog/1464036f-94d5-4dbd-aef8-fe99246a26d4/application","descriptionHtml":"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.
We are:
Product-led. More than 500K 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.
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.
We’re looking for people (in the US - Pacific timezone) that like deep ownership of production systems, people that are not afraid of working with stateful infrastructure and love working in AWS, VMs, automation, and making messy systems reliable.
In general we seek SRE’s who are:
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.
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.
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
You don't need to be an expert in every system we run on day one. But you do need to enjoy owning complex infrastructure and learning how the pieces fit together.
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
We are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know.
#LI-DNI
","descriptionPlain":"ABOUT POSTHOG\n\nPostHog 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.\n\nWe launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:\n\n - A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking\n\n - PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data\n\n - Data warehouse https://posthog.com/context-warehouse/managed-warehouse so users can query product and customer data together using custom SQL insights.\n\nWe are:\n\n 1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.\n\n 2. Default alive https://paulgraham.com/aord.html. 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.\n\n 3. 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.\n\nWe're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog. \n\n \n\n\nTHINGS WE CARE ABOUT\n\n - 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 https://posthog.com/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.\n\n - 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 https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.\n\n - Shipping fast: Why not now? https://posthog.com/handbook/values#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 https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.\n\n - 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 https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.\n\n - 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 https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.\n\n\nWHO WE'RE LOOKING FOR\n\nWe’re looking for people (in the US - Pacific timezone) that like deep ownership of production systems, people that are not afraid of working with stateful infrastructure and love working in AWS, VMs, automation, and making messy systems reliable.\n\nIn general we seek SRE’s who are:\n\n - 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.\n\n - 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.\n\n - 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 https://posthog.com/handbook/company/grown-ups, it's about being low-ego, flexible, and respectful.\n\n - 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.\n\n\nWHAT YOU'LL BE DOING\n\nYou 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)\nThat 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. \n\nYou'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.\n\n - Operating EKS clusters across several environments with Karpenter autoscaling, Cilium networking, and ArgoCD-driven GitOps deployments\n\n - Managing and evolving a multi AWS account organization, provisioning, networking, access control, and cross-account connectivity\n\n - Maintaining the Terraform/Terragrunt IaC platform - modules, automated plan-on-PR / apply-on-merge pipelines, and safe patterns for shared infrastructure\n\n - Improving operational tooling around deploys, schema changes, backups, restores, and incident response\n\n - Reducing operational load by identifying repeat pain points and eliminating them through code and self-healing automation\n\n - Optimizing cloud spend as you go\n\n - Participating in on-call and incident response, with a strong focus on making incidents rarer over time\n\nYou'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.\n\n\n\nREQUIREMENTS\n\n - 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)\n\n - Strong experience operating production infrastructure on AWS. Not just one account, but understanding organizational boundaries, IAM, and networking between many\n\n - Experience automating infrastructure using Terraform or Terragrunt at scale, including module design and state management\n\n - Solid understanding of Linux systems (disk, memory, networking, failure modes)\n\n - Experience supporting stateful systems (databases, queues, storage systems, etc.)\n\n - Ability to debug and reason about performance and reliability issues in production\n\n - You're comfortable owning systems end-to-end, including on-call responsibilities\n\nYou don't need to be an expert in every system we run on day one. But you do need to enjoy owning complex infrastructure and learning how the pieces fit together.\n\n\n\n\nNICE TO HAVE\n\n - Experience with GitOps workflows (ArgoCD) and CI/CD pipelines (GitHub Actions)\n\n - Experience with building AI agent-enabled base-level infra services for teams that move fast\n\n - Familiarity with multi-region infrastructure and the consistency/availability tradeoffs that come with it\n\nWe are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know.\n\n\n\n#LI-DNI","compensation":{"compensationTierSummary":null,"scrapeableCompensationSalarySummary":null,"compensationTiers":[],"summaryComponents":[]}},{"id":"3c592b84-8b34-4ae4-ae23-cadce8f2212d","title":"Product Manager (ex-founder or ex-product engineer)","department":"Product Management","team":"Product Management","employmentType":"FullTime","location":"Remote","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-10-06T12:22:51.673+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"US | EU"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/3c592b84-8b34-4ae4-ae23-cadce8f2212d","applyUrl":"https://jobs.ashbyhq.com/posthog/3c592b84-8b34-4ae4-ae23-cadce8f2212d/application","descriptionHtml":"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.
We are:
Product-led. More than 500K 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.
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.
Product management plays a slightly different role at PostHog than at most other companies and is incredibly important. Instead of micro-managing engineers, PMs are responsible for research, data, and setting high-level context across the organization. They work across multiple products to determine how products are being used, what the competitive landscape is like, and how users are feeling about PostHog. Using the usual PM jargon we could say PMs at PostHog are very discovery-focused and don’t engage in delivery almost at all.
Among other things, they:
Run growth reviews for products that have product-market-fit
Dive into data research projects to answer challenging questions without obvious answers
Organize user interviews
Provide just-in-time product feedback for new and existing features, following our principles of shipping and iterating quickly
Coach product engineers on \"how to do product\"
If you want to know more about our philosophy of building products, read our article “Product Management is broken. Engineers can fix it.”
You will be joining PostHog as a Product Manager, working with one of our small engineering teams (with the potential to cover more than one team/product after your onboarding period), with a heavy emphasis on analyzing data, talking to users and owning the commercial aspects of your product(s):
We have a growth review with every product every month. As the PM, you ensure we have the right metrics, dig into things that have changed, understand what users are doing, why they're churning, etc. You use the findings to figure out if we need to dig deeper into a trend or reprioritize what we're building.
Across our 10+ products (and counting!), we have thousands of paying customers and many more on the free tier. That’s a lot of users and a lot of data. Finding actionable patterns in this data is one of the key ingredients to reaching $100M ARR. Example questions you might be answering:
How does revenue/usage churn for your product compare across different segments?
Which behaviours lead to long-term retention for your product?
You keep an eye on the commercial side of things. Each of our products is competing with incumbents multiple times bigger both in revenue and employee size. You will lead the research into our competitors and the tooling landscape, and provide recommendations where we have the biggest untapped potential, whether it’s pricing, feature parity or even spinning out an adjacent product
Things you choose to pick up. This could be a data deep dive outside the scope of the repeating growth reviews. Or figuring out how to package and price a new product that we want to perform better in terms of usage or revenue. Or it could be rubber-ducking the engineers to help them figure out the UX for a new product concept. This is a highly autonomous role, and you’re expected to figure out where it makes the most sense to spend your time.
❌ Backlog grooming (it always sounded gross anyway)
❌ Deciding or approving what we build (though you’ll help surface the context needed to make good decisions)
❌ Shielding developers from users (instead, you should aim to invite an engineer for every user interview you do)
❌ Project management / writing gazillions of tickets, RFCs, or PRDs
❌ Coding and shipping new features yourself (small PRs and hackathon contributions are of course encouraged!)
You’ve been a technical founder or product engineer in a startup: We are explicitly looking for someone who has written code before and now wants to focus on the product and commercial side
You have strong product sense - meaning you can identify a product’s biggest selling points and weaknesses (both user experience and commercial) and turn them into actionable insights that inform your team’s product decisions
You’re familiar with business and product metrics (e.g. activation, retention, churn) and defining and tracking key product metrics. You don’t hesitate to write SQL (or another query language) to answer data questions
You’re very proactive/organized, so you don’t wait to be told what to do. Instead, you figure out what needs to happen, make it happen and keep multiple threads moving forward without letting things slip
You collaborate well as you default to transparency, share early, and seek feedback from the team and customers in an async-first world. Strong communication skills are the key to strong collaboration.
You have hands-on experience using observability products and understand how engineers use them to investigate, debug, and diagnose issues in production.
Nice-to-haves (We don’t expect you to tick all of these boxes, but at least 2-3 are a big plus):
You’ve worked on or PM’d an observability product before.
You have additional data modelling experience on top of writing queries.
You’ve worked on a developer tool or AI product before.
You’ve done a decent portion of interviewing users already. And looking at additional product management experience, you might have even worked with designers or engineers on new user experiences?
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!
#LI-DNI
","descriptionPlain":"ABOUT POSTHOG\n\nPostHog 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.\n\nWe launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:\n\n - A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking\n\n - PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data\n\n - Data warehouse https://posthog.com/context-warehouse/managed-warehouse so users can query product and customer data together using custom SQL insights.\n\nWe are:\n\n 1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.\n\n 2. Default alive https://paulgraham.com/aord.html. 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.\n\n 3. 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.\n\nWe're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog. \n\n \n\n\nTHINGS WE CARE ABOUT\n\n - 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 https://posthog.com/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.\n\n - 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 https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.\n\n - Shipping fast: Why not now? https://posthog.com/handbook/values#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 https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.\n\n - 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 https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.\n\n - 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.\n\n - 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 https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.\n\n\n\n\nPRODUCT AT POSTHOG\n\nProduct management plays a slightly different role at PostHog https://posthog.com/handbook/product/product-team than at most other companies and is incredibly important. Instead of micro-managing engineers, PMs are responsible for research, data, and setting high-level context across the organization. They work across multiple products https://posthog.com/handbook/product/product-team#small-team-membership to determine how products are being used, what the competitive landscape is like, and how users are feeling about PostHog. Using the usual PM jargon we could say PMs at PostHog are very discovery-focused and don’t engage in delivery https://www.svpg.com/discovery-vs-delivery/ almost at all.\n\nAmong other things, they:\n\n 1. Run growth reviews https://posthog.com/handbook/product/per-product-growth-reviews for products that have product-market-fit\n\n 2. Dive into data research projects to answer challenging questions without obvious answers\n\n 3. Organize user interviews https://posthog.com/handbook/product/user-feedback\n\n 4. Provide just-in-time product feedback for new and existing features, following our principles of shipping and iterating quickly\n\n 5. Coach product engineers on \"how to do product https://posthog.com/handbook/engineering/product-engineering\"\n\nIf you want to know more about our philosophy of building products, read our article “Product Management is broken. Engineers can fix it.” https://posthog.com/newsletter/product-management-is-broken\n\n\n\n\nWHAT YOU WILL BE DOING:\n\nYou will be joining PostHog as a Product Manager, working with one of our small engineering teams https://posthog.com/teams (with the potential to cover more than one team/product after your onboarding period), with a heavy emphasis on analyzing data, talking to users and owning the commercial aspects of your product(s):\n\n - We have a growth review https://posthog.com/handbook/product/per-product-growth-reviews with every product every month. As the PM, you ensure we have the right metrics, dig into things that have changed, understand what users are doing, why they're churning, etc. You use the findings to figure out if we need to dig deeper into a trend or reprioritize what we're building.\n\n - Across our 10+ https://posthog.com/pricing products (and counting!), we have thousands of paying customers and many more on the free tier. That’s a lot of users and a lot of data. Finding actionable patterns in this data is one of the key ingredients to reaching $100M ARR https://posthog.com/handbook/future. Example questions you might be answering:\n \n - How does revenue/usage churn for your product compare across different segments?\n \n - Which behaviours lead to long-term retention for your product?\n\n - You keep an eye on the commercial side of things. Each of our products is competing with incumbents multiple times bigger both in revenue and employee size. You will lead the research into our competitors and the tooling landscape, and provide recommendations where we have the biggest untapped potential, whether it’s pricing, feature parity or even spinning out an adjacent product\n\n - Things you choose to pick up. This could be a data deep dive outside the scope of the repeating growth reviews. Or figuring out how to package and price a new product that we want to perform better in terms of usage or revenue. Or it could be rubber-ducking the engineers to help them figure out the UX for a new product concept. This is a highly autonomous role, and you’re expected to figure out where it makes the most sense to spend your time.\n\n\n\n\nWHAT YOU WON’T BE DOING:\n\n❌ Backlog grooming (it always sounded gross anyway)\n\n❌ Deciding or approving what we build (though you’ll help surface the context needed to make good decisions)\n\n❌ Shielding developers from users (instead, you should aim to invite an engineer for every user interview you do)\n\n❌ Project management / writing gazillions of tickets, RFCs, or PRDs\n\n❌ Coding and shipping new features yourself (small PRs and hackathon contributions are of course encouraged!)\n\n\n\n\nYOU’LL FIT RIGHT IN IF:\n\n - You’ve been a technical founder or product engineer in a startup: We are explicitly looking for someone who has written code before and now wants to focus on the product and commercial side\n\n - You have strong product sense - meaning you can identify a product’s biggest selling points and weaknesses (both user experience and commercial) and turn them into actionable insights that inform your team’s product decisions\n\n - You’re familiar with business and product metrics (e.g. activation, retention, churn) and defining and tracking key product metrics. You don’t hesitate to write SQL (or another query language) to answer data questions\n\n - You’re very proactive/organized, so you don’t wait to be told what to do. Instead, you figure out what needs to happen, make it happen and keep multiple threads moving forward without letting things slip\n\n - You collaborate well as you default to transparency, share early, and seek feedback from the team and customers in an async-first world. Strong communication skills are the key to strong collaboration.\n\n - You have hands-on experience using observability products and understand how engineers use them to investigate, debug, and diagnose issues in production.\n\nNice-to-haves (We don’t expect you to tick all of these boxes, but at least 2-3 are a big plus):\n\n - You’ve worked on or PM’d an observability product before.\n\n - You have additional data modelling experience on top of writing queries.\n\n - You’ve worked on a developer tool or AI product before.\n\n - You’ve done a decent portion of interviewing users already. And looking at additional product management experience, you might have even worked with designers or engineers on new user experiences?\n\nIf 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! \n\n#LI-DNI","compensation":{"compensationTierSummary":null,"scrapeableCompensationSalarySummary":null,"compensationTiers":[],"summaryComponents":[]}},{"id":"8854fb74-8457-40cd-bc10-60125a0c0cd4","title":"Technical Customer Success Manager - Americas","department":"Sales & Customer Success","team":"Customer Success","employmentType":"FullTime","location":"Remote","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-06-26T07:37:48.731+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"USA"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/8854fb74-8457-40cd-bc10-60125a0c0cd4","applyUrl":"https://jobs.ashbyhq.com/posthog/8854fb74-8457-40cd-bc10-60125a0c0cd4/application","descriptionHtml":"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.
We are:
Product-led. More than 500K 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.
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.
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.
We do not care what your old job title was. We care that you want to talk to customers, own the relationship and help them get more from PostHog.
Some of our best TCSMs used to ship code. Now they ship happy customers. Ex-dev, ex-TAM, ex-something-else? All good, if you want to own customers and not only be near them!
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!
You can read Tyler's blog to see what a day as a TCSM looks like!
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).
❌ 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.
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.
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!
#LI-DNI
","descriptionPlain":"ABOUT POSTHOG\n\nPostHog 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.\n\nWe launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:\n\n - A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking\n\n - PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data\n\n - Data warehouse https://posthog.com/context-warehouse/managed-warehouse so users can query product and customer data together using custom SQL insights.\n\nWe are:\n\n 1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.\n\n 2. Default alive https://paulgraham.com/aord.html. 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.\n\n 3. 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.\n\nWe're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog. \n\n \n\n\nTHINGS WE CARE ABOUT\n\n - 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 https://posthog.com/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.\n\n - 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 https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.\n\n - Shipping fast: Why not now? https://posthog.com/handbook/values#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 https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.\n\n - 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 https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.\n\n - 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 https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.\n\n\nWHO WE’RE LOOKING FOR\n\n - 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.\n\n - You'll need to be incredibly helpful, technical enough to help our customers, and solve real problems without asking a sales engineer for help. \n\n - No going away and asking an expert by default. You will be the expert!\n\n - 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.\n\n - We do not care what your old job title was. We care that you want to talk to customers, own the relationship and help them get more from PostHog.\n \n - Some of our best TCSMs used to ship code. Now they ship happy customers. Ex-dev, ex-TAM, ex-something-else? All good, if you want to own customers and not only be near them!\n\n\n\n\nWHAT YOU’LL BE DOING\n\nYou’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! \n\nIt'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).\n\nDay to day, it looks like:\n\n - Building relationships with your users. You should know who the key people are at each company, and they should know you. \n\n - Owning their feedback and making sure it gets to the wider PostHog team.\n\n - Investigating technical issues. You're the first person to dig into customer issues, often solving them yourself rather than immediately passing to support.\n\n - Being super responsive to their Slack messages, support tickets, and emails.\n\n - Being their favorite ever Customer Success person to work with!\n\nMore 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!\n\n\n\nYou can read Tyler's blog to see what a day as a TCSM looks like! https://posthog.com/blog/customer-success-at-posthog\n\nThis role comprises a base salary component, plus a bonus https://posthog.com/handbook/cs-and-onboarding/how-we-work#how-contractual-bonus-works---technical-csms for hitting/exceeding customer retention targets. The salary in our compensation calculator is the OTE (80/20). \n\n\n\n\nWHAT YOU WON’T BE DOING\n\n❌ 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. \n\n❌ Aggressively pursuing expansion opportunities. This role is primarily focused on retention. \n\n\n\n\nREQUIREMENTS\n\n - 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. \n\n - 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.\n\n - 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.\n\n - 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.\n\n\nNICE TO HAVE\n\n - 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.\n\n - You’ve been in a Pre-sales or Technical Account Manager role before, bringing both technical expertise and commercial acumen.\n\nIf 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! \n\n#LI-DNI","compensation":{"compensationTierSummary":null,"scrapeableCompensationSalarySummary":null,"compensationTiers":[],"summaryComponents":[]}},{"id":"36d5ce14-851c-450f-879a-45cbb896225e","title":"Security Engineer ","department":"Engineering","team":"Security","employmentType":"FullTime","location":"Remote (EMEA)","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[{"location":"Remote (UK)","address":{"postalAddress":{"addressRegion":"Remote (UK)","addressCountry":"United Kingdom","addressLocality":""}}}],"publishedAt":"2026-09-14T10:01:44.488+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"European Union"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/36d5ce14-851c-450f-879a-45cbb896225e","applyUrl":"https://jobs.ashbyhq.com/posthog/36d5ce14-851c-450f-879a-45cbb896225e/application","descriptionHtml":"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.
We are:
Product-led. More than 500K 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.
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.
We are looking for an expert security generalist (in EU/UK) to assist with all things security at PostHog. Someone equally adept (and interested!) in building secure libraries, writing semgrep rules, hardening cloud deployments, improving network observability, and leading incident response.
Someone to take the reins of our security operations, build out our detection pipelines, and ensure that when something goes bump in the night, we have the observability to know exactly what happened.
We're a team that's building internal security products and agents - things like agents to automatically triage wiz alerts, automatically review pull requests, automatically assign vulnerability findings to the owning product team.
In this role you’ll:
Build from Scratch: You aren't maintaining someone else's legacy SIEM. You are shaping the security team, culture and tooling for a high-growth, open-source company.
Zero Bureaucracy: We hate meetings. We don't have \"Security Committees.\" You have the autonomy to make changes and move fast.
Transparency: We work in the open. You’ll be able to see (and contribute to) how we handled past incidents, like this NPM package compromise.
Direct Impact: Your work directly protects the data of thousands of customers. When you improve our security posture, the whole company (and our community) feels it.
Triage and Tune: You’ll own our Wiz alerts. You’ll be responsible for turning \"noise\" into \"actionable findings\" and ensuring we aren't just staring at a dashboard of issues that don't actually matter. We already get relatively few alerts, and we’d like to even further reduce that to just the ones that matter.
Incident detection, response: You’ll lead the charge on security incidents. Whether it’s a compromised NPM package or a suspicious IAM pattern, you’ll help coordinate the response and lead the post-mortem. You’ll also help build our IR runbooks.
Build Observability: You’ll build detection pipelines, and close our network-based observability gaps. We want to be able to trace network requests and suspicious activity all the way back to specific code paths.
Threat Hunting: You’ll proactively hunt for threats in our AWS environment. You won't just wait for an alert; you'll define what \"good\" looks like and build the telemetry to prove it.
The VDP: You’ll support our Vulnerability Disclosure Program, triaging reports from researchers and eventually transitioning us toward a formal bug bounty program.
Enable the Team: You’ll support our product squads with threat modeling and secure design reviews. We don't do \"Security says no\"; we do \"Security says 'here is how to do this safely.'\"
Help build our security culture: Our engineers trust the security team and view security as an enabler. You’ll be a crucial part of helping to continue this excellent (and uncommon) working relationship.
While this is not a Corporate security (MDM, endpoint, device trust) or Supply chain/CI-CD hardening role, in true PostHog style, there are opportunities to work on these as well.
Cloud Native: You have 3-5+ years of experience in security engineering with a heavy focus on AWS. You know your way around IAM, VPC logs, and CloudTrail like the back of your hand.
Detection Specialist: You’ve used CSPM/CNAPP tools (like Wiz or Prisma) and, more importantly, you know how to build detection pipelines that engineers actually trust.
Battle-Tested: You’ve led incident response before. You’re calm under pressure and know how to coordinate across teams to contain a threat.
High Autonomy: We don’t have a security SOC. You’ll be building this function from scratch, so you need to be comfortable deciding what’s important and executing on it without a manual.
Engineering skills: You bring strong engineering experience and next to digging into code to understand an exploit or a vulnerability, you can write code with the same proficiency as our product engineers.
Communication and attitude: As mentioned before we don't do \"Security says no\", we do \"Security says 'here is how to do this safely.” This is crucial for us, we need people that want to enable engineers and work with them, not limit them.
Incident management: Strong experience with incident response/incident detection
We are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know
#LI-DNI
","descriptionPlain":"ABOUT POSTHOG\n\nPostHog 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.\n\nWe launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:\n\n - A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking\n\n - PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data\n\n - Data warehouse https://posthog.com/context-warehouse/managed-warehouse so users can query product and customer data together using custom SQL insights.\n\nWe are:\n\n 1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.\n\n 2. Default alive https://paulgraham.com/aord.html. 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.\n\n 3. 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.\n\nWe're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog. \n\n \n\n\nTHINGS WE CARE ABOUT\n\n - 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 https://posthog.com/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.\n\n - 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 https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.\n\n - Shipping fast: Why not now? https://posthog.com/handbook/values#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 https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.\n\n - 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 https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.\n\n - 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 https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.\n\n\nWHO WE'RE LOOKING FOR\n\nWe are looking for an expert security generalist (in EU/UK) to assist with all things security at PostHog. Someone equally adept (and interested!) in building secure libraries, writing semgrep rules, hardening cloud deployments, improving network observability, and leading incident response.\n\nSomeone to take the reins of our security operations, build out our detection pipelines, and ensure that when something goes bump in the night, we have the observability to know exactly what happened. \n\nWe're a team that's building internal security products and agents - things like agents to automatically triage wiz alerts, automatically review pull requests, automatically assign vulnerability findings to the owning product team.\n\nIn this role you’ll:\n\n - Build from Scratch: You aren't maintaining someone else's legacy SIEM. You are shaping the security team, culture and tooling for a high-growth, open-source company.\n\n - Zero Bureaucracy: We hate meetings. We don't have \"Security Committees.\" You have the autonomy to make changes and move fast.\n\n - Transparency: We work in the open. You’ll be able to see (and contribute to) how we handled past incidents, like this NPM package compromise https://www.google.com/search?q=https://github.com/PostHog/posthog/issues/example.\n\n - Direct Impact: Your work directly protects the data of thousands of customers. When you improve our security posture, the whole company (and our community) feels it.\n\n\nWHAT YOU'LL BE DOING\n\n - Triage and Tune: You’ll own our Wiz alerts. You’ll be responsible for turning \"noise\" into \"actionable findings\" and ensuring we aren't just staring at a dashboard of issues that don't actually matter. We already get relatively few alerts, and we’d like to even further reduce that to just the ones that matter.\n\n - Incident detection, response: You’ll lead the charge on security incidents. Whether it’s a compromised NPM package or a suspicious IAM pattern, you’ll help coordinate the response and lead the post-mortem. You’ll also help build our IR runbooks.\n\n - Build Observability: You’ll build detection pipelines, and close our network-based observability gaps. We want to be able to trace network requests and suspicious activity all the way back to specific code paths.\n\n - Threat Hunting: You’ll proactively hunt for threats in our AWS environment. You won't just wait for an alert; you'll define what \"good\" looks like and build the telemetry to prove it.\n\n - The VDP: You’ll support our Vulnerability Disclosure Program, triaging reports from researchers and eventually transitioning us toward a formal bug bounty program.\n\n - Enable the Team: You’ll support our product squads with threat modeling and secure design reviews. We don't do \"Security says no\"; we do \"Security says 'here is how to do this safely.'\"\n\n - Help build our security culture: Our engineers trust the security team and view security as an enabler. You’ll be a crucial part of helping to continue this excellent (and uncommon) working relationship.\n\nWhile this is not a Corporate security (MDM, endpoint, device trust) or Supply chain/CI-CD hardening role, in true PostHog style, there are opportunities to work on these as well.\n\n \n\n\nREQUIREMENTS\n\n - Cloud Native: You have 3-5+ years of experience in security engineering with a heavy focus on AWS. You know your way around IAM, VPC logs, and CloudTrail like the back of your hand.\n\n - Detection Specialist: You’ve used CSPM/CNAPP tools (like Wiz or Prisma) and, more importantly, you know how to build detection pipelines that engineers actually trust.\n\n - Battle-Tested: You’ve led incident response before. You’re calm under pressure and know how to coordinate across teams to contain a threat.\n\n - High Autonomy: We don’t have a security SOC. You’ll be building this function from scratch, so you need to be comfortable deciding what’s important and executing on it without a manual.\n\n - Engineering skills: You bring strong engineering experience and next to digging into code to understand an exploit or a vulnerability, you can write code with the same proficiency as our product engineers.\n\n - Communication and attitude: As mentioned before we don't do \"Security says no\", we do \"Security says 'here is how to do this safely.” This is crucial for us, we need people that want to enable engineers and work with them, not limit them.\n\n\nNICE TO HAVE\n\n - Incident management: Strong experience with incident response/incident detection\n\nWe are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know\n\n#LI-DNI","compensation":{"compensationTierSummary":null,"scrapeableCompensationSalarySummary":null,"compensationTiers":[],"summaryComponents":[]}},{"id":"2a78f2f8-4fd3-413b-9c7d-55db568e68c1","title":"Finance Manager, Revenue Accounting","department":"Finance","team":"Finance","employmentType":"FullTime","location":"Remote (US)","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-09-14T22:39:48.748+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"United States"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/2a78f2f8-4fd3-413b-9c7d-55db568e68c1","applyUrl":"https://jobs.ashbyhq.com/posthog/2a78f2f8-4fd3-413b-9c7d-55db568e68c1/application","descriptionHtml":"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.
We are:
Product-led. More than 500K 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.
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.
PostHog bills on customer usage. This means we need to recognize revenue on usage basis. This involves figuring out what we actually earned and making sure the books show exactly that every month, on time, every time. And we need someone to own this entirely.
You’ll be expected to know where every dollar of revenue comes from, how it was recognized, why it was recognized that way, and exactly when it was collected. You’ve got plenty of company in tackling this with the finance team, the billing engineers and the revops team, all to ensure our GL tells the truth.
If you enjoy being in the weeds and seeing the direct impact of your work on a fast growing company, this could be the right fit for you.
Own daily revenue accounting operations for usage based billing - journal entries, deferrals, recognition schedules, reconciliations, collections, tackling billing questions, the works. you’re responsible for ensuring every revenue transaction is recorded correctly and nothing falls through the cracks. Don’t let that daunt you - you’ll get plenty of support!
Execute the revenue side of month-end and year-end close - work collaboratively with the team to hit closing deadlines every month, co-own the checklist, track what’s outstanding - making sure we report accurate financials on time
Manage accounts receivable - handling collections, keeping cash flowing smoothly and answering any billing questions from Sales or customers
Support our annual financial audit - organize revenue related documentation, implement controls, and get audit workpapers ready. Help make the audit painless
Own the finance side of our billing/accounting integration - we’re going live with the new billing ledger model, and you’ll own integrating it with Campfire, our accounting ERP
Automate the boring stuff - finding opportunities to make our revenue accounting operations more efficient as we grow.
Bonus points if you like pineapple on pizza! 🍍🍕
❌ FP&A
❌ Strategic finance
❌ Fundraising or investor relations.
5+ years of owning usage based revenue recognition experience in AI/SaaS companies
Strong working knowledge of GAAP and month-end/year-end close process
Comfortable working independently
Comfortable building processes and controls
Nice to haves
Relevant education in accounting
Been through a financial audit
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!
#LI-DNI
","descriptionPlain":"ABOUT POSTHOG\n\nPostHog 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.\n\nWe launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:\n\n - A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking\n\n - PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data\n\n - Data warehouse https://posthog.com/context-warehouse/managed-warehouse so users can query product and customer data together using custom SQL insights.\n\nWe are:\n\n 1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.\n\n 2. Default alive https://paulgraham.com/aord.html. 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.\n\n 3. 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.\n\nWe're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog. \n\n \n\n\nTHINGS WE CARE ABOUT\n\n - 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 https://posthog.com/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.\n\n - 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 https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.\n\n - Shipping fast: Why not now? https://posthog.com/handbook/values#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 https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.\n\n - 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 https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.\n\n - 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 https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.\n\n\nJOB SUMMARY\n\nPostHog bills on customer usage. This means we need to recognize revenue on usage basis. This involves figuring out what we actually earned and making sure the books show exactly that every month, on time, every time. And we need someone to own this entirely.\n\nYou’ll be expected to know where every dollar of revenue comes from, how it was recognized, why it was recognized that way, and exactly when it was collected. You’ve got plenty of company in tackling this with the finance team, the billing engineers and the revops team, all to ensure our GL tells the truth.\n\nIf you enjoy being in the weeds and seeing the direct impact of your work on a fast growing company, this could be the right fit for you.\n\n\n\n\nWHAT YOU’LL BE DOING\n\n - Own daily revenue accounting operations for usage based billing - journal entries, deferrals, recognition schedules, reconciliations, collections, tackling billing questions, the works. you’re responsible for ensuring every revenue transaction is recorded correctly and nothing falls through the cracks. Don’t let that daunt you - you’ll get plenty of support!\n\n - Execute the revenue side of month-end and year-end close - work collaboratively with the team to hit closing deadlines every month, co-own the checklist, track what’s outstanding - making sure we report accurate financials on time\n\n - Manage accounts receivable - handling collections, keeping cash flowing smoothly and answering any billing questions from Sales or customers\n\n - Support our annual financial audit - organize revenue related documentation, implement controls, and get audit workpapers ready. Help make the audit painless\n\n - Own the finance side of our billing/accounting integration - we’re going live with the new billing ledger model, and you’ll own integrating it with Campfire, our accounting ERP\n\n - Automate the boring stuff - finding opportunities to make our revenue accounting operations more efficient as we grow.\n\n - Bonus points if you like pineapple on pizza! 🍍🍕\n\n\n\n\nWHAT YOU WON'T BE DOING\n\n❌ FP&A\n\n❌ Strategic finance\n\n❌ Fundraising or investor relations.\n\n \n\n\nREQUIREMENTS\n\n - 5+ years of owning usage based revenue recognition experience in AI/SaaS companies\n\n - Strong working knowledge of GAAP and month-end/year-end close process\n\n - Comfortable working independently\n\n - Comfortable building processes and controls\n\nNice to haves\n\n - Relevant education in accounting\n\n - Been through a financial audit\n\nIf 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! \n\n#LI-DNI","compensation":{"compensationTierSummary":null,"scrapeableCompensationSalarySummary":null,"compensationTiers":[],"summaryComponents":[]}},{"id":"82ef4227-e7a6-4e59-a128-2b3333951e21","title":"Developer Marketer - Sales","department":"Marketing","team":"Developer Marketing","employmentType":"FullTime","location":"Remote","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[{"location":"Remote","address":{"postalAddress":{"addressCountry":"USA"}}}],"publishedAt":"2026-10-07T09:54:22.369+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"US | EU"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/82ef4227-e7a6-4e59-a128-2b3333951e21","applyUrl":"https://jobs.ashbyhq.com/posthog/82ef4227-e7a6-4e59-a128-2b3333951e21/application","descriptionHtml":"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 (existing text is fine)
We are:
Product-led. More than 500K 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.
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.
As a Developer Marketer for Sales, your job is to distil the sometimes chaotic happenings within PostHog into sales enablement. You'll be taking positioning and messaging from across PostHog and turning it into something Sales can actually use to win deals.
You'll use a mix of strong communication and engineering skills to do it. You'll collaborate closely with our sales team, our other PMMs, engineers, and users to strengthen our position as the default all-in-one devtool.
The work spans positioning, competitive intelligence, objection handling, customer storytelling, and the operating cadence that keeps it all current. PostHog ships fast and our product surface area is broad -- staying ahead of that, and making sure Sales doesn't fall behind it, is the core of the job. You'll also create positioning and messaging for platform features and areas without a dedicated PMM.
Marketers at PostHog are hands-on, T-shaped people who take on a lot of varied responsibilities to support users and other teams. You'll be one of the key voices for our company and comfortable being visible to customers, partners, and the sales team, often translating between them.
Owning sales enablement end-to-end. You'll be the person Sales goes to for positioning, competitive material, objection handling, and customer stories. You'll build and maintain the playbooks in the public handbook so Sales can find what they need in the moment they need it.
Translating PMM work into Sales-ready material. Our PMMs own product-level positioning and messaging for some products. You'll take that work and turn it into battlecards, talk tracks, discovery questions, and enablement sessions that Sales can actually use.
Filling positioning gaps. Some platform features and product areas don't have a dedicated PMM today. You'll own positioning for those areas so Sales has a clear story everywhere.
Surfacing insight from real customer conversations. Use cases, objections, and pain points are currently buried in Gong recordings and Slack threads. You'll pull signal out of those and feed it back into messaging, content, and product.
Shipping. A lot. This is not a job where you write a strategy deck and wait. You'll be shipping enablement every week -- battlecards, FAQs, training sessions, launch enablement -- and iterating fast based on what Sales actually finds useful.
Product Launch: Launch Plan: LLM Observability requests-for-comments-public#348
Price Cut Comms: RFC: Data warehouse pricing update Q3 2025 requests-for-comments-internal#818
❌ Writing whitepapers, mission statements, or sales decks nobody reads.
❌ Running formal certification programs or quarterly readiness training.
❌ Owning the CRM, sales ops, or pipeline metrics. That's Sales' job.
❌ Spending multiple quarters planning big projects which don't have immediate impact.
❌ Running yawn-worthy webinars and bombarding users with invitations to attend.
Excellent writing, researching, and communication skills
Development experience, though not necessarily in a formal role -- vibecoded side projects still count
Experience targeting developers as customers or writing for technical audiences
Experience building and maintaining sales enablement content that's actually used
Comfort working closely with Sales as your primary internal customer
Nice to have
Experience surfacing insights from call recordings (Gong, Granola, etc.)
Experience working with handbook-style documentation as the source of truth
Familiarity or experience working with devtool products
Experience working as a product marketer, growth marketer, or content marketer
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!
#LI-DNI
","descriptionPlain":"ABOUT POSTHOG\n\nPostHog 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.\n\nWe launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:\n\n - A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking\n\n - PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data\n\n - Data warehouse https://posthog.com/context-warehouse/managed-warehouse (existing text is fine)\n\nWe are:\n\n 1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.\n\n 2. Default alive https://paulgraham.com/aord.html. 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.\n\n 3. 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.\n\nWe're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog. \n\n \n\n\nTHINGS WE CARE ABOUT\n\n - 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 https://posthog.com/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.\n\n - 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 https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.\n\n - Shipping fast: Why not now? https://posthog.com/handbook/values#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 https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.\n\n - 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 https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.\n\n - 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 https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.\n\n\nOTHER COMPANIES WOULD CALL THIS BEING A PRODUCT MARKETER, BUT WE'RE LOOKING FOR SOMEONE WITH DEVTOOL EXPERIENCE, SO: DEVELOPER MARKETER.\n\nAs a Developer Marketer for Sales, your job is to distil the sometimes chaotic happenings within PostHog into sales enablement. You'll be taking positioning and messaging from across PostHog and turning it into something Sales can actually use to win deals.\n\nYou'll use a mix of strong communication and engineering skills to do it. You'll collaborate closely with our sales team, our other PMMs, engineers, and users to strengthen our position as the default all-in-one devtool.\n\nThe work spans positioning, competitive intelligence, objection handling, customer storytelling, and the operating cadence that keeps it all current. PostHog ships fast and our product surface area is broad -- staying ahead of that, and making sure Sales doesn't fall behind it, is the core of the job. You'll also create positioning and messaging for platform features and areas without a dedicated PMM.\n\nMarketers at PostHog are hands-on, T-shaped people who take on a lot of varied responsibilities to support users and other teams. You'll be one of the key voices for our company and comfortable being visible to customers, partners, and the sales team, often translating between them.\n\n\n\n\nWHAT YOU WILL BE DOING\n\n - Owning sales enablement end-to-end. You'll be the person Sales goes to for positioning, competitive material, objection handling, and customer stories. You'll build and maintain the playbooks in the public handbook so Sales can find what they need in the moment they need it.\n\n - Translating PMM work into Sales-ready material. Our PMMs own product-level positioning and messaging for some products. You'll take that work and turn it into battlecards, talk tracks, discovery questions, and enablement sessions that Sales can actually use.\n\n - Filling positioning gaps. Some platform features and product areas don't have a dedicated PMM today. You'll own positioning for those areas so Sales has a clear story everywhere.\n\n - Surfacing insight from real customer conversations. Use cases, objections, and pain points are currently buried in Gong recordings and Slack threads. You'll pull signal out of those and feed it back into messaging, content, and product.\n\n - Shipping. A lot. This is not a job where you write a strategy deck and wait. You'll be shipping enablement every week -- battlecards, FAQs, training sessions, launch enablement -- and iterating fast based on what Sales actually finds useful.\n\n\nEXAMPLE PUBLIC ISSUES/PROJECTS:\n\n - Product Launch: Launch Plan: LLM Observability requests-for-comments-public#348 https://github.com/PostHog/requests-for-comments-public/issues/348\n\n - Price Cut Comms: RFC: Data warehouse pricing update Q3 2025 requests-for-comments-internal#818 https://github.com/PostHog/requests-for-comments-internal/pull/818\n\n\n\n\nWHAT YOU WON'T BE DOING\n\n❌ Writing whitepapers, mission statements, or sales decks nobody reads.\n\n❌ Running formal certification programs or quarterly readiness training.\n\n❌ Owning the CRM, sales ops, or pipeline metrics. That's Sales' job.\n\n❌ Spending multiple quarters planning big projects which don't have immediate impact.\n\n❌ Running yawn-worthy webinars and bombarding users with invitations to attend.\n\n\n\n\nREQUIREMENTS\n\n - Excellent writing, researching, and communication skills\n\n - Development experience, though not necessarily in a formal role -- vibecoded side projects still count\n\n - Experience targeting developers as customers or writing for technical audiences\n\n - Experience building and maintaining sales enablement content that's actually used\n\n - Comfort working closely with Sales as your primary internal customer\n\nNice to have\n\n - Experience surfacing insights from call recordings (Gong, Granola, etc.)\n\n - Experience working with handbook-style documentation as the source of truth\n\n - Familiarity or experience working with devtool products\n\n - Experience working as a product marketer, growth marketer, or content marketer\n\nIf 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! \n\n#LI-DNI","compensation":{"compensationTierSummary":null,"scrapeableCompensationSalarySummary":null,"compensationTiers":[],"summaryComponents":[]}}],"apiVersion":"1"}