Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
We’ve proven that to be successful with our customers, we don’t need to stack multiple people all doing different roles for a customer.
With the right person working with them, who has the right balance of commercial and technical skills, we can get them excited enough to switch to PostHog and stick with us for a long time.
Technical Account Executives own the initial relationship with customers who get in touch via the website and want to speak with a human before signing up to PostHog. It’s early days, so you’ll cover the full spectrum of customers from high-velocity startups looking to move quickly, to more complex strategic engagements with Mid-Market/Enterprise customers.
They’ll also do warm outbound to users from large companies who sign up for PostHog themselves. Their focus is guiding the customer on their initial evaluation of PostHog as well as right-sizing their contract according to their needs.
This means:
Winning new business. You'll find your way to the right people at prospective customers — engineers, PMs, founders — and show them why PostHog beats whatever they're using now. You own the whole deal, first call to close and beyond, and you’re comfortable in your ability to meet and exceed a quarterly target.
Owning customer feedback and making sure it gets to the wider PostHog team. You’ll work directly with product teams, we don’t believe in bureaucracy here.
Being hyper responsive is a must. You need to feel like an extension of a customer’s existing team. We try to do as much customer comms in Slack as possible.
You’ll need to be an expert on all PostHog products, so that you can help customers see the value and adopt them.
Comfortable with outbound. You'll earn meetings through relevance and creativity – not through volume and pressure. We do weird outbound.
Switching contexts comfortably. Prospect and triage leads in the morning, enterprise evaluation in the afternoon, async Loom response to a customer question in between. You adjust tone, depth, and approach for each without losing quality.
Turning both inbound and outbound lead flow into a real pipeline that converts. Lots of people get in touch with us. Not all of them are deals. You should be able to tell the difference quickly, prioritize who PostHog will be a good fit for and close them efficiently.
This is a great role for someone who has been an AE before and has owned longer term customer relationships, but equally good if you have been a technical sales engineer who is confident in their ability to carry a quota
This role has a base salary component plus commission for hitting/exceeding sales targets. The salary in our compensation calculator is your expected total pay for on-target earnings.
❌ 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.
❌ Automating everything. A big part of this role will be ‘inefficiently’ building a lot of white glove, 1-1 customer relationships, so you can’t just rely on email sequences.
You’re able to go deep on understanding PostHog’s products, including more technical ones like feature flags and data warehouse. You don’t need to be a developer, but the ability to get into the details will give you confidence and really help you bring more value to customer conversations. For example, you should be able to advise on configuration best practices to companies with multiple products and applications, advising on the pros and cons of different SDKs, and how to implement PostHog into their existing stack.
Commercially-minded. You’re excited about not only helping customers go from 0 to 1 with PostHog - but also growing and retaining revenue. If we’ve never spoken to a particular customer, you’ll get creative to get them to engage.
Strong customer focus. You need to help our users and remove any blockers to them using Posthog effectively.
Good at handling relationships strategically. Helping a customer achieve their goals over time, expanding their usage and buying more and more products from us as they do so, while saying no to customers who we’re not right for.
You write well. We're remote-first and async-default. You'll write follow-up emails, Slack summaries, evaluation plans, and Loom scripts. Unclear writing slows your customers and your team down.
You’ve managed a book of business and/or are comfortable leading multi-threaded deal cycles across various technical organizations, legal and procurement.
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 built outbound campaigns before – not just executed someone else's sequences.
You've shipped something (a tool, a workflow, an automation) that made your team more effective. We want to hear about it.
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\nProduct development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.\n\nPostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.\n\nWe started with open-source product analytics, launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products https://posthog.com/products, including:\n\n - PostHog Code https://posthog.com/code, the only AI devtool that understands your product, not just your codebase.\n\n - A built-in data warehouse https://posthog.com/docs/data-warehouse, so users can query product and customer data together using custom SQL insights.\n\n - PostHog AI https://posthog.com/ai, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.\n\nWe are:\n\n 1. Product-led. More than 450,000 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\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\nWHAT YOU’LL BE DOING\n\nWe’ve proven that to be successful with our customers, we don’t need to stack multiple people all doing different roles for a customer.\n\nWith the right person working with them, who has the right balance of commercial and technical skills, we can get them excited enough to switch to PostHog and stick with us for a long time.\n\nTechnical Account Executives own the initial relationship with customers who get in touch via the website and want to speak with a human before signing up to PostHog. It’s early days, so you’ll cover the full spectrum of customers from high-velocity startups looking to move quickly, to more complex strategic engagements with Mid-Market/Enterprise customers.\n\nThey’ll also do warm outbound to users from large companies who sign up for PostHog themselves. Their focus is guiding the customer on their initial evaluation of PostHog as well as right-sizing their contract according to their needs.\n\nThis means:\n\n - Winning new business. You'll find your way to the right people at prospective customers — engineers, PMs, founders — and show them why PostHog beats whatever they're using now. You own the whole deal, first call to close and beyond, and you’re comfortable in your ability to meet and exceed a quarterly target.\n\n - Owning customer feedback and making sure it gets to the wider PostHog team. You’ll work directly with product teams, we don’t believe in bureaucracy here.\n\n - Being hyper responsive is a must. You need to feel like an extension of a customer’s existing team. We try to do as much customer comms in Slack as possible.\n\n - You’ll need to be an expert on all PostHog products, so that you can help customers see the value and adopt them.\n\n - Comfortable with outbound. You'll earn meetings through relevance and creativity – not through volume and pressure. We do weird outbound.\n\n - Switching contexts comfortably. Prospect and triage leads in the morning, enterprise evaluation in the afternoon, async Loom response to a customer question in between. You adjust tone, depth, and approach for each without losing quality.\n\n - Turning both inbound and outbound lead flow into a real pipeline that converts. Lots of people get in touch with us. Not all of them are deals. You should be able to tell the difference quickly, prioritize who PostHog will be a good fit for and close them efficiently.\n\nThis is a great role for someone who has been an AE before and has owned longer term customer relationships, but equally good if you have been a technical sales engineer who is confident in their ability to carry a quota\n\nThis role has a base salary component plus commission for hitting/exceeding sales targets. The salary in our compensation calculator is your expected total pay for on-target earnings.\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 - ❌ Automating everything. A big part of this role will be ‘inefficiently’ building a lot of white glove, 1-1 customer relationships, so you can’t just rely on email sequences.\n\n\nREQUIREMENTS\n\n - You’re able to go deep on understanding PostHog’s products, including more technical ones like feature flags and data warehouse. You don’t need to be a developer, but the ability to get into the details will give you confidence and really help you bring more value to customer conversations. For example, you should be able to advise on configuration best practices to companies with multiple products and applications, advising on the pros and cons of different SDKs, and how to implement PostHog into their existing stack.\n\n - Commercially-minded. You’re excited about not only helping customers go from 0 to 1 with PostHog - but also growing and retaining revenue. If we’ve never spoken to a particular customer, you’ll get creative to get them to engage.\n\n - Strong customer focus. You need to help our users and remove any blockers to them using Posthog effectively.\n\n - Good at handling relationships strategically. Helping a customer achieve their goals over time, expanding their usage and buying more and more products from us as they do so, while saying no to customers who we’re not right for.\n\n - You write well. We're remote-first and async-default. You'll write follow-up emails, Slack summaries, evaluation plans, and Loom scripts. Unclear writing slows your customers and your team down.\n\n - You’ve managed a book of business and/or are comfortable leading multi-threaded deal cycles across various technical organizations, legal and procurement.\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 built outbound campaigns before – not just executed someone else's sequences.\n\n - You've shipped something (a tool, a workflow, an automation) that made your team more effective. We want to hear about it.\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":"3f190a45-7810-47f9-b77d-169b806ea266","title":"Backend Engineer (Europe/UK timezone)","department":"Engineering","team":"Ingestion","employmentType":"FullTime","location":"Remote (EMEA)","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[{"location":"Remote (UK)","address":{"postalAddress":{"addressRegion":"Remote (UK)","addressCountry":"United Kingdom","addressLocality":""}}}],"publishedAt":"2026-08-06T08:48:44.502+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"European Union"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/3f190a45-7810-47f9-b77d-169b806ea266","applyUrl":"https://jobs.ashbyhq.com/posthog/3f190a45-7810-47f9-b77d-169b806ea266/application","descriptionHtml":"Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
We're seeking a Europe/UK based ingestion pipeline engineer who:
Thrives on challenges of building systems that process billions of events per day
Gets excited about designing elegant and efficient systems that can handle terabytes of data without giving people insomnia
Understands the importance of data integrity and reliability for customers
The ideal candidate has experience with high-throughput data processing systems such as:
Analytics platforms
Metric collection systems
Log aggregation engines
Streaming and batch-processing pipelines
We use a mixture of Node.JS and Rust for high-throughput processing. We store most of our data in Kafka, PostgreSQL, Clickhouse, S3, and Redis, but with the growing volume of data, we're constantly re-evaluating our technological choices. We're looking for someone who understands the principles of designing distributed systems and can use them to pick the best tools for the job.
At PostHog you won't get stuck maintaining an obscure microservice or working in the shadows of the product org, instead, you will:
Own the entire service from end-to-end: No committees or overzealous PMs, the destiny of the ingestion pipeline will be in your hands.
Build open-source software: You'll be able to show your Rust-fu to your friends and family (and security researchers too).
Build in the hot path: Your code will decide whether our customers and engineers have a good time or not.
Start from first principles: No cookie-cutter solutions here, you'll be safe from AI agents for a good while.
See immediate results: Small, confident, frequent steps forward – that's how we like to move.
Our team is spread across North America and Europe and we're looking for another engineer in Europe or the UK.
We're growing very quickly at PostHog, so quickly that the numbers in our job descriptions often get out of date. Our ingestion pipeline is currently processing 10s of billions of events a month and we're hoping to add one more zero to that soon. You’ll be responsible for developing the infrastructure to capture all that data, process it reliably, and provide it to other parts of PostHog's platform, such as product analytics, feature flags, CDP, and more.
Experience working with highly scalable, event-driven distributed systems
You have developed multi-tenant software-as-a-service products
Experience with Node.JS, Go, Rust, or similar languages
You have worked with Kafka and PostgreSQL, Redis, or similar systems at scale
You know how to ship changes quickly without breaking things
Experience with customer data platforms or similar data analytics systems
You've carried a pager and have dealt with incidents
You're comfortable with provisioning and maintaining cloud infrastructure
Experience with benchmarking and profiling tools
Knowledge of observability systems and practices
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\nProduct development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.\n\nPostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.\n\nWe started with open-source product analytics, launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products https://posthog.com/products, including:\n\n - PostHog Code https://posthog.com/code, the only AI devtool that understands your product, not just your codebase.\n\n - A built-in data warehouse https://posthog.com/docs/data-warehouse, so users can query product and customer data together using custom SQL insights.\n\n - PostHog AI https://posthog.com/ai, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.\n\nWe are:\n\n 1. Product-led. More than 450,000 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\nWHO WE’RE LOOKING FOR\n\nWe're seeking a Europe/UK based ingestion pipeline engineer who:\n\n - Thrives on challenges of building systems that process billions of events per day\n\n - Gets excited about designing elegant and efficient systems that can handle terabytes of data without giving people insomnia\n\n - Understands the importance of data integrity and reliability for customers\n\n\nThe ideal candidate has experience with high-throughput data processing systems such as:\n\n - Analytics platforms\n\n - Metric collection systems\n\n - Log aggregation engines\n\n - Streaming and batch-processing pipelines\n\n\nWe use a mixture of Node.JS and Rust for high-throughput processing. We store most of our data in Kafka, PostgreSQL, Clickhouse, S3, and Redis, but with the growing volume of data, we're constantly re-evaluating our technological choices. We're looking for someone who understands the principles of designing distributed systems and can use them to pick the best tools for the job.\n\n\n\n\nWHAT MAKES THIS ROLE UNIQUE \n\nAt PostHog you won't get stuck maintaining an obscure microservice or working in the shadows of the product org, instead, you will:\n\n - Own the entire service from end-to-end: No committees or overzealous PMs, the destiny of the ingestion pipeline will be in your hands.\n\n - Build open-source software: You'll be able to show your Rust-fu to your friends and family (and security researchers too).\n\n - Build in the hot path: Your code will decide whether our customers and engineers have a good time or not.\n\n - Start from first principles: No cookie-cutter solutions here, you'll be safe from AI agents for a good while.\n\n - See immediate results: Small, confident, frequent steps forward – that's how we like to move.\n\n\n\n\nWHAT YOU’LL BE DOING\n\nOur team is spread across North America and Europe and we're looking for another engineer in Europe or the UK.\n\n\nWe're growing very quickly at PostHog, so quickly that the numbers in our job descriptions often get out of date. Our ingestion pipeline is currently processing 10s of billions of events a month and we're hoping to add one more zero to that soon. You’ll be responsible for developing the infrastructure to capture all that data, process it reliably, and provide it to other parts of PostHog's platform, such as product analytics, feature flags, CDP, and more.\n\n\n\n\nREQUIREMENTS\n\n - Experience working with highly scalable, event-driven distributed systems\n\n - You have developed multi-tenant software-as-a-service products\n\n - Experience with Node.JS, Go, Rust, or similar languages\n\n - You have worked with Kafka and PostgreSQL, Redis, or similar systems at scale\n\n - You know how to ship changes quickly without breaking things\n\n\n\n\nNICE TO HAVE \n\n - Experience with customer data platforms or similar data analytics systems\n\n - You've carried a pager and have dealt with incidents\n\n - You're comfortable with provisioning and maintaining cloud infrastructure\n\n - Experience with benchmarking and profiling tools\n\n - Knowledge of observability systems and practices\n\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":"b42fd20b-b647-4f42-b725-b29ca472cba8","title":"Technical Account Manager - EMEA","department":"Sales & Customer Success","team":"Sales & Customer Success","employmentType":"FullTime","location":"Remote (EMEA)","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-01-14T07:21:31.414+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"European Union"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/b42fd20b-b647-4f42-b725-b29ca472cba8","applyUrl":"https://jobs.ashbyhq.com/posthog/b42fd20b-b647-4f42-b725-b29ca472cba8/application","descriptionHtml":"Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
We’re looking for someone who is:
A natural relationship builder. You get energy from meeting new people in a customer org, finding out what they care about, and connecting dots between teams. You're the person who ends up knowing the head of platform, the VP of engineering, and the CTO's chief of staff – not just the one engineer who signed up.
Comfortable selling to senior leaders. You can hold your own in a conversation with a VP or C-level exec, talk about their business priorities in their language, and make the case for PostHog as a strategic platform decision rather than a point tool.
Technical enough to be credible. You don't need to be a developer, but you need to confidently demo every PostHog product, speak to how they fit together, and know when to pull in somebody else on the team for deeper technical work. No going away and \"getting back to you\" on basic product questions.
Great at reading the signs of which customers to focus on. You'll be laser-focused on accounts that match our ICP and have real expansion potential, and not spend time where you can't have an impact.
Good at maintaining long-term relationships past the initial sale. You own the relationship and sell new products as fast as we build them.
We’re building every tool a product engineer needs to build better products, and our strategy is working – we’re finding customers organically using two, three, or even four PostHog tools at a time. Your challenge is to drive multi-product adoption without forcing people into using tools they don’t need.
We have over 1,000 organizations signing up to use PostHog every week. We have product-market fit and loads of customers happily self-serving to large contract values, but staying focused on the biggest opportunities is increasingly challenging as a result.
We've proven that our customers do best when a small number of people own the relationship end-to-end. The TAM+CSM pair work together on all of our current customers with expansion potential – you bring the commercial and relationship depth, your CSM brings the technical depth, and together you're an extension of the customer's team.
Technical Account Managers have an existing book of business. These are engaged, high-paying ($20k+/yr) customers who we think have huge expansion potential. Some of these people have never talked to us before!
Your focus:
Multi-threading. Most of our customers start with one champion in one team. Your job is to turn that into relationships across product, engineering, data, platform, and leadership – so PostHog becomes the default choice whenever a new team has a question, our products can answer.
Selling up. Expansion and cross-sell often require a senior sponsor. You'll build relationships with directors, VPs, and execs, understand their goals, and position PostHog against those. When a customer is evaluating a platform decision, you want to be in the room.
Driving multi-product adoption. We're finding customers organically using two, three, or even four PostHog tools at a time. Your challenge is to accelerate that without forcing people into tools they don't need.
Owning customer feedback and getting it to the wider PostHog team. You'll work directly with product teams – we don't believe in bureaucracy here.
Being hyper responsive. You need to feel like an extension of a customer's existing team. We try to do as much customer comms in Slack as possible.
Partnering closely with a CSM. You'll jointly own the account strategy, trade off who leads which conversations, and make sure the customer experiences a single, coordinated team.
This role has a base salary component plus commission for hitting/exceeding sales targets - the salary in our compensation calculator is your expected total pay for on-target earnings.
❌ 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.
❌ Owning the deep technical implementation work solo. Your CSM partner takes the lead on that, and you'll tag in where it helps the commercial conversation.
❌ Automating everything. A big part of this role will be ‘inefficiently’ building a lot of white-glove, 1-1 customer relationships, so you can’t just rely on email sequences.
Strong relationship-building skills across seniority levels. You can move fluidly from a conversation with an IC engineer to a 30-minute slot with a VP, and leave both feeling like you understood what they care about. You enjoy meeting new people inside an account and finding reasons to stay in touch.
Commercially-minded. You're excited about growing and retaining revenue. If we've never spoken to a particular customer, you'll get creative to engage them. You think in terms of account strategy over 12-24 months, not just the next deal.
Able to go broad on PostHog's products. You should be able to demo any of our products confidently and articulate the value of each, including the more technical ones like Feature Flags and Data Warehouse. You don't need to be a developer – your CSM partner handles the deep technical work – but you need enough fluency to be credible with a technical audience and know when to bring your CSM in.
Good at handling relationships strategically. Helping a customer achieve their goals over time, expanding their usage and buying more products from us as they do so, while saying no to customers we're not right for.
Strong customer focus. You need to help our users and remove any blockers to them using PostHog effectively.
Experience selling or managing accounts with senior technical buyers (VP Engineering, CTO, Head of Platform, Head of Data).
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 the owner of several customers in the $20k-100k+ ARR range previously, with evidence of growing them through expansion and cross-sell rather than just renewal.
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\nProduct development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.\n\nPostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.\n\nWe started with open-source product analytics, launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products https://posthog.com/products, including:\n\n - PostHog Code https://posthog.com/code, the only AI devtool that understands your product, not just your codebase.\n\n - A built-in data warehouse https://posthog.com/docs/data-warehouse, so users can query product and customer data together using custom SQL insights.\n\n - PostHog AI https://posthog.com/ai, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.\n\nWe are:\n\n 1. Product-led. More than 450,000 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\nWHO WE’RE LOOKING FOR\n\nWe’re looking for someone who is:\n\n - A natural relationship builder. You get energy from meeting new people in a customer org, finding out what they care about, and connecting dots between teams. You're the person who ends up knowing the head of platform, the VP of engineering, and the CTO's chief of staff – not just the one engineer who signed up.\n\n - Comfortable selling to senior leaders. You can hold your own in a conversation with a VP or C-level exec, talk about their business priorities in their language, and make the case for PostHog as a strategic platform decision rather than a point tool.\n\n - Technical enough to be credible. You don't need to be a developer, but you need to confidently demo every PostHog product, speak to how they fit together, and know when to pull in somebody else on the team for deeper technical work. No going away and \"getting back to you\" on basic product questions.\n\n - Great at reading the signs of which customers to focus on. You'll be laser-focused on accounts that match our ICP and have real expansion potential, and not spend time where you can't have an impact.\n\n - Good at maintaining long-term relationships past the initial sale. You own the relationship and sell new products as fast as we build them.\n\nWe’re building every tool a product engineer needs to build better products, and our strategy is working – we’re finding customers organically using two, three, or even four PostHog tools at a time. Your challenge is to drive multi-product adoption without forcing people into using tools they don’t need.\n\nWe have over 1,000 organizations signing up to use PostHog every week. We have product-market fit and loads of customers happily self-serving to large contract values, but staying focused on the biggest opportunities is increasingly challenging as a result.\n\n\n\n\nWHAT YOU’LL BE DOING\n\nWe've proven that our customers do best when a small number of people own the relationship end-to-end. The TAM+CSM pair work together on all of our current customers with expansion potential – you bring the commercial and relationship depth, your CSM brings the technical depth, and together you're an extension of the customer's team.\n\nTechnical Account Managers have an existing book of business. These are engaged, high-paying ($20k+/yr) customers who we think have huge expansion potential. Some of these people have never talked to us before!\n\nYour focus:\n\n - Multi-threading. Most of our customers start with one champion in one team. Your job is to turn that into relationships across product, engineering, data, platform, and leadership – so PostHog becomes the default choice whenever a new team has a question, our products can answer.\n\n - Selling up. Expansion and cross-sell often require a senior sponsor. You'll build relationships with directors, VPs, and execs, understand their goals, and position PostHog against those. When a customer is evaluating a platform decision, you want to be in the room.\n\n - Driving multi-product adoption. We're finding customers organically using two, three, or even four PostHog tools at a time. Your challenge is to accelerate that without forcing people into tools they don't need.\n\n - Owning customer feedback and getting it to the wider PostHog team. You'll work directly with product teams – we don't believe in bureaucracy here.\n\n - Being hyper responsive. You need to feel like an extension of a customer's existing team. We try to do as much customer comms in Slack as possible.\n\n - Partnering closely with a CSM. You'll jointly own the account strategy, trade off who leads which conversations, and make sure the customer experiences a single, coordinated team.\n\nThis role has a base salary component plus commission for hitting/exceeding sales targets - the salary in our compensation calculator is your expected total pay for on-target earnings.\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❌ Owning the deep technical implementation work solo. Your CSM partner takes the lead on that, and you'll tag in where it helps the commercial conversation.\n\n❌ Automating everything. A big part of this role will be ‘inefficiently’ building a lot of white-glove, 1-1 customer relationships, so you can’t just rely on email sequences.\n\n\nREQUIREMENTS\n\n - Strong relationship-building skills across seniority levels. You can move fluidly from a conversation with an IC engineer to a 30-minute slot with a VP, and leave both feeling like you understood what they care about. You enjoy meeting new people inside an account and finding reasons to stay in touch.\n\n - Commercially-minded. You're excited about growing and retaining revenue. If we've never spoken to a particular customer, you'll get creative to engage them. You think in terms of account strategy over 12-24 months, not just the next deal.\n\n - Able to go broad on PostHog's products. You should be able to demo any of our products confidently and articulate the value of each, including the more technical ones like Feature Flags and Data Warehouse. You don't need to be a developer – your CSM partner handles the deep technical work – but you need enough fluency to be credible with a technical audience and know when to bring your CSM in.\n\n - Good at handling relationships strategically. Helping a customer achieve their goals over time, expanding their usage and buying more products from us as they do so, while saying no to customers we're not right for.\n\nStrong customer focus. You need to help our users and remove any blockers to them using PostHog effectively.\n\n\nNICE TO HAVE\n\n - Experience selling or managing accounts with senior technical buyers (VP Engineering, CTO, Head of Platform, Head of Data).\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 the owner of several customers in the $20k-100k+ ARR range previously, with evidence of growing them through expansion and cross-sell rather than just renewal.\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":"8dc3f33a-b930-4c54-b4c4-3e6bd2ff28d3","title":"AI Research Engineer","department":"Engineering","team":"PostHog AI","employmentType":"FullTime","location":"Hybrid (UK)","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-07-07T08:27:59.605+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":"Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
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\nProduct development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.\n\nPostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.\n\nWe started with open-source product analytics, launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products https://posthog.com/products, including:\n\n - PostHog Code https://posthog.com/code, the only AI devtool that understands your product, not just your codebase.\n\n - A built-in data warehouse https://posthog.com/docs/data-warehouse, so users can query product and customer data together using custom SQL insights.\n\n - PostHog AI https://posthog.com/ai, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.\n\nWe are:\n\n 1. Product-led. More than 450,000 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\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":"1803b1de-d33b-4542-8e38-b6c4954cb789","title":"Backend Engineer","department":"Engineering","team":"Growth - Billing","employmentType":"FullTime","location":"Remote","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-08-06T08:49:09.307+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"US | EU"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/1803b1de-d33b-4542-8e38-b6c4954cb789","applyUrl":"https://jobs.ashbyhq.com/posthog/1803b1de-d33b-4542-8e38-b6c4954cb789/application","descriptionHtml":"Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
Someone has to make sure PostHog actually gets paid. That's us.
We have 14+ usage-based products, subscription add-ons, and soon seat-based pricing with credit pools. Every dollar PostHog makes flows through what we build. If we screw up, customers lose trust and churn - doesn't matter how good the product is. Execs, product, and GTM teams can't make good decisions without the data we provide.
We launch new products all the time and we always want to do what makes sense for customers rather than fit things into a rigid existing system. That means we need to build billing infrastructure that's modular enough to support whatever we throw at it next, fast enough to iterate on without breaking things, and reliable enough that the numbers are always right. Getting all three perfect at once is impossible - finding the right balance is the main challenge. Are we there yet? Not even close. But you'll help us get there faster.
Scaling our billing system to $100M+ revenue (the hundy) by the end of 2026, and well beyond (the billy?).
Building billing primitives flexible enough that launching a new pricing model doesn't require rearchitecting everything.
Making our usage reporting and limiting near-realtime.
Turning usage and messy raw invoice data into actionable internal reports, accurate forecasts, and compliant financials.
Making all of the above go brrr.
Example projects:
PostHog is generally very open about what we build, but our billing repo understandably isn't. Here's a taste of what we're working on right now though (see our team page for more):
Implementing a new, ledger-based revenue model and re-building all dashboards and investor reports on top of it.
Making billing the source of truth for pricing, subscriptions and invoicing.
Shipping 5+ pricing launches and changes this quarter, including two new pricing models.
Strong backend engineer. Python, SQL, and complex data modeling should feel like home.
Edge cases make you excited, not anxious.
Experience with data pipelines, task queues, and workflow orchestration - we still have a lot of Celery but are leaning more into Temporal and Dagster.
If you've done something manually twice (or seen someone else do it) - you're already building an automation or an internal tool to make it easier.
Happy paths are maybe 10% of billing. You treat error handling, rollbacks, and retries as the actual work - not TODOs you'll \"get to later\".
You don't need someone to tell you what to build. You've started a company, led a major project from scratch, or shipped an impressive side project.
Nice to haves:
You've built and scaled usage-based billing systems before (and have the scars to prove it).
You get weirdly excited about revenue modeling, forecasting and accounting ledgers.
You have a decent guess which one of these we made up: Q2C / AR / B2R / GAAP / ASC 606 / NRR.
This role is not for you if:
You only want to work with other engineers - billing touches every team at PostHog, from product to finance to GTM to marketing.
You need clearly defined requirements before you start building.
You think billing is a solved problem - we thought so too, once.
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\nProduct development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.\n\nPostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.\n\nWe started with open-source product analytics, launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products https://posthog.com/products, including:\n\n - PostHog Code https://posthog.com/code, the only AI devtool that understands your product, not just your codebase.\n\n - A built-in data warehouse https://posthog.com/docs/data-warehouse, so users can query product and customer data together using custom SQL insights.\n\n - PostHog AI https://posthog.com/ai, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.\n\nWe are:\n\n 1. Product-led. More than 450,000 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\nWHO WE’RE LOOKING FOR\n\nSomeone has to make sure PostHog actually gets paid. That's us.\n\nWe have 14+ usage-based products, subscription add-ons, and soon seat-based pricing with credit pools. Every dollar PostHog makes flows through what we build. If we screw up, customers lose trust and churn - doesn't matter how good the product is. Execs, product, and GTM teams can't make good decisions without the data we provide.\n\nWe launch new products all the time and we always want to do what makes sense for customers rather than fit things into a rigid existing system. That means we need to build billing infrastructure that's modular enough to support whatever we throw at it next, fast enough to iterate on without breaking things, and reliable enough that the numbers are always right. Getting all three perfect at once is impossible - finding the right balance is the main challenge. Are we there yet? Not even close. But you'll help us get there faster.\n\n\n\n\nWHAT YOU'LL BE DOING\n\n - Scaling our billing system to $100M+ revenue (the hundy https://www.linkedin.com/posts/posthog_scaling-with-product-led-growth-going-from-activity-7419734364248317952-GQFX) by the end of 2026, and well beyond (the billy?).\n\n - Building billing primitives flexible enough that launching a new pricing model doesn't require rearchitecting everything.\n\n - Making our usage reporting and limiting near-realtime.\n\n - Turning usage and messy raw invoice data into actionable internal reports, accurate forecasts, and compliant financials.\n\n - Making all of the above go brrr.\n\nExample projects:\n\nPostHog is generally very open about what we build, but our billing repo understandably isn't. Here's a taste of what we're working on right now though (see our team page https://posthog.com/teams/billing for more):\n\n - Implementing a new, ledger-based revenue model and re-building all dashboards and investor reports on top of it.\n\n - Making billing the source of truth for pricing, subscriptions and invoicing.\n\n - Shipping 5+ pricing launches and changes this quarter, including two new pricing models.\n\n\n\n\nYOU’LL FIT RIGHT IN IF:\n\n - Strong backend engineer. Python, SQL, and complex data modeling should feel like home.\n\n - Edge cases make you excited, not anxious.\n\n - Experience with data pipelines, task queues, and workflow orchestration - we still have a lot of Celery but are leaning more into Temporal and Dagster.\n\n - If you've done something manually twice (or seen someone else do it) - you're already building an automation or an internal tool to make it easier.\n\n - Happy paths are maybe 10% of billing. You treat error handling, rollbacks, and retries as the actual work - not TODOs you'll \"get to later\".\n\n - You don't need someone to tell you what to build. You've started a company, led a major project from scratch, or shipped an impressive side project.\n\nNice to haves:\n\n - You've built and scaled usage-based billing systems before (and have the scars to prove it).\n\n - You get weirdly excited about revenue modeling, forecasting and accounting ledgers.\n\n - You have a decent guess which one of these we made up: Q2C / AR / B2R / GAAP / ASC 606 / NRR.\n\nThis role is not for you if:\n\n - You only want to work with other engineers - billing touches every team at PostHog, from product to finance to GTM to marketing.\n\n - You need clearly defined requirements before you start building.\n\n - You think billing is a solved problem - we thought so too, once.\n\n\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":"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":"Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
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\nProduct development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.\n\nPostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.\n\nWe started with open-source product analytics, launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products https://posthog.com/products, including:\n\n - PostHog Code https://posthog.com/code, the only AI devtool that understands your product, not just your codebase.\n\n - A built-in data warehouse https://posthog.com/docs/data-warehouse, so users can query product and customer data together using custom SQL insights.\n\n - PostHog AI https://posthog.com/ai, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.\n\nWe are:\n\n 1. Product-led. More than 450,000 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\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":"ddb7032a-f85f-4029-b17f-790c612fec6d","title":"BizOps Manager (sales focused)","department":"Sales & Customer Success","team":"New Business Sales","employmentType":"FullTime","location":"Remote","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-06-17T22:50:06.291+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"US | EU"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/ddb7032a-f85f-4029-b17f-790c612fec6d","applyUrl":"https://jobs.ashbyhq.com/posthog/ddb7032a-f85f-4029-b17f-790c612fec6d/application","descriptionHtml":"Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
PostHog runs on a usage-based, product-led model where the line between self-serve and sales-led is genuinely blurry which makes the revenue problems here more interesting than at most companies. Sales-led revenue is close to half the business and spans AEs, CSMs, TAMs and onboarding, and right now it doesn't have a dedicated operating engine. That's the role.
This is an analytical role at heart. You'll own the numbers everyone trusts for sales-led revenue: the metrics layer, the forecast, the monthly growth review, and the honest read on what actually drives revenue versus what we've assumed. You'll also own sales compensation and build the proactive systems that surface problems before anyone has to ask. You're building the systems, definitions and source of truth where none exist today, with direct exposure to execs and no routing through anyone.
A sales revenue source of truth: Build the trustworthy activation, expansion and attribution metrics layer for the sales led motion. Work out what actually correlates with revenue vs what we've assumed (e.g. whether our ICP score tracks real revenue outcomes). Dig into open metric questions, e.g. how NRR rolls up and the deltas in it. Be the person we trust for \"what's really happening with sales led revenue\"
Monthly sales growth review: own the cadence end to end: prep, analysis, and a clear read on what's driving and blocking growth. Surface gainers, losers, new vs expansion revenue, and where mature customer growth is slowing. Don't let signal wait for the monthly meetings: run lightweight weekly/biweekly updates pushed to sales leads and reps so the numbers reach people without being pulled. Treat the review as a decision making tool: leading indicators, levers and gaps, not just numbers.
Pipeline & forecast discipline: own pipeline hygiene, deal stage definitions and forecast accuracy, working collaboratively with the Revenue Leader. Design the minimum viable process that gives reliable signal without burying reps in CRM admin. Be opinionated about the data, metrics and roadmap for Salesforce and Vitally.
Decision support: run win/loss analysis, set discounting and pricing guardrails (with the analysis behind them), implement ongoing tests across the sales funnel and design small experiments on the sales motion with an honest read on whether they worked.
Sales compensation: Design, model and maintain rep comp plans so incentives actually point at company revenue goals. Own quota setting and the modeling behind it. Run comp scenarios and pressure test them before they ship. Own comp planning each cycle, from first model to rolled out plan. Give reps and leads live visibility into attainment throughout the quarter and flag proactively when someone is tracking behind.
Triggers & proactive monitoring: build alerting on the things that actually move sales led revenue: deals slipping stages, forecast diverging from pacing mid quarter, reps falling behind attainment, churn or expansion signals, ICP score outliers. Catch problems early and route them to the right rep or lead with a recommended action, so the monthly review becomes synthesis rather than discovery.
❌ Owning Salesforce and Vitally as software, or building GTM tooling and automation. This isn't a GTM engineering or CRM admin role.
❌ Broader cross funnel revenue work
Background in RevOps, bizops, sales ops, finance, or a strategy/analytics role with real revenue exposure.
You write your own SQL (or equivalent), because the questions worth answering here don't have a dashboard, you get to the answer yourself.
Experience in usage-based / PLG revenue models where the line between self serve and sales led is blurry.
Able to get opinionated on sales compensation quickly, whether or not you've designed plans before, and you understand how incentives change behavior at the margin.
You build monitoring and updates that surface problems early, rather than waiting to be asked, and without creating bureaucracy.
Sales, finance and product will trust your numbers because you've earned it, not because you own them.
Hands on Salesforce (or similar CRM) reporting.
Have designed or run sales compensation plans before.
Experience standing up a revops/salesops function for the first time, rather than inheriting a mature one.
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\nProduct development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.\n\nPostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.\n\nWe started with open-source product analytics, launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products https://posthog.com/products, including:\n\n - PostHog Code https://posthog.com/code, the only AI devtool that understands your product, not just your codebase.\n\n - A built-in data warehouse https://posthog.com/docs/data-warehouse, so users can query product and customer data together using custom SQL insights.\n\n - PostHog AI https://posthog.com/ai, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.\n\nWe are:\n\n 1. Product-led. More than 450,000 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\nJOB SUMMARY\n\nPostHog runs on a usage-based, product-led model where the line between self-serve and sales-led is genuinely blurry which makes the revenue problems here more interesting than at most companies. Sales-led revenue is close to half the business and spans AEs, CSMs, TAMs and onboarding, and right now it doesn't have a dedicated operating engine. That's the role.\n\nThis is an analytical role at heart. You'll own the numbers everyone trusts for sales-led revenue: the metrics layer, the forecast, the monthly growth review, and the honest read on what actually drives revenue versus what we've assumed. You'll also own sales compensation and build the proactive systems that surface problems before anyone has to ask. You're building the systems, definitions and source of truth where none exist today, with direct exposure to execs and no routing through anyone.\n\n\n\n\nWHAT YOU'LL BE DOING\n\n - A sales revenue source of truth: Build the trustworthy activation, expansion and attribution metrics layer for the sales led motion. Work out what actually correlates with revenue vs what we've assumed (e.g. whether our ICP score tracks real revenue outcomes). Dig into open metric questions, e.g. how NRR rolls up and the deltas in it. Be the person we trust for \"what's really happening with sales led revenue\"\n\n - Monthly sales growth review: own the cadence end to end: prep, analysis, and a clear read on what's driving and blocking growth. Surface gainers, losers, new vs expansion revenue, and where mature customer growth is slowing. Don't let signal wait for the monthly meetings: run lightweight weekly/biweekly updates pushed to sales leads and reps so the numbers reach people without being pulled. Treat the review as a decision making tool: leading indicators, levers and gaps, not just numbers.\n\n - Pipeline & forecast discipline: own pipeline hygiene, deal stage definitions and forecast accuracy, working collaboratively with the Revenue Leader. Design the minimum viable process that gives reliable signal without burying reps in CRM admin. Be opinionated about the data, metrics and roadmap for Salesforce and Vitally.\n\n - Decision support: run win/loss analysis, set discounting and pricing guardrails (with the analysis behind them), implement ongoing tests across the sales funnel and design small experiments on the sales motion with an honest read on whether they worked.\n\n - Sales compensation: Design, model and maintain rep comp plans so incentives actually point at company revenue goals. Own quota setting and the modeling behind it. Run comp scenarios and pressure test them before they ship. Own comp planning each cycle, from first model to rolled out plan. Give reps and leads live visibility into attainment throughout the quarter and flag proactively when someone is tracking behind.\n\n - Triggers & proactive monitoring: build alerting on the things that actually move sales led revenue: deals slipping stages, forecast diverging from pacing mid quarter, reps falling behind attainment, churn or expansion signals, ICP score outliers. Catch problems early and route them to the right rep or lead with a recommended action, so the monthly review becomes synthesis rather than discovery.\n \n \n\n\nWHAT YOU WON’T BE DOING\n\n❌ Owning Salesforce and Vitally as software, or building GTM tooling and automation. This isn't a GTM engineering or CRM admin role.\n\n❌ Broader cross funnel revenue work\n\n\n\n\nREQUIREMENTS\n\n - Background in RevOps, bizops, sales ops, finance, or a strategy/analytics role with real revenue exposure.\n\n - You write your own SQL (or equivalent), because the questions worth answering here don't have a dashboard, you get to the answer yourself.\n\n - Experience in usage-based / PLG revenue models where the line between self serve and sales led is blurry.\n\n - Able to get opinionated on sales compensation quickly, whether or not you've designed plans before, and you understand how incentives change behavior at the margin.\n\n - You build monitoring and updates that surface problems early, rather than waiting to be asked, and without creating bureaucracy.\n\n - Sales, finance and product will trust your numbers because you've earned it, not because you own them.\n\n\nNICE TO HAVE\n\n - Hands on Salesforce (or similar CRM) reporting.\n\n - Have designed or run sales compensation plans before.\n\n - Experience standing up a revops/salesops function for the first time, rather than inheriting a mature one.\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":"Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
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.
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\nProduct development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.\n\nPostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.\n\nWe started with open-source product analytics, launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products https://posthog.com/products, including:\n\n - PostHog Code https://posthog.com/code, the only AI devtool that understands your product, not just your codebase.\n\n - A built-in data warehouse https://posthog.com/docs/data-warehouse, so users can query product and customer data together using custom SQL insights.\n\n - PostHog AI https://posthog.com/ai, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.\n\nWe are:\n\n 1. Product-led. More than 450,000 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\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\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":"84de4a11-ad69-4b1d-abf9-c7d7b46152d9","title":"Business Development Lead - Americas","department":"Sales & Customer Success","team":"New Business Sales","employmentType":"FullTime","location":"Remote","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[],"publishedAt":"2026-07-02T17:10:39.158+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"USA"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/84de4a11-ad69-4b1d-abf9-c7d7b46152d9","applyUrl":"https://jobs.ashbyhq.com/posthog/84de4a11-ad69-4b1d-abf9-c7d7b46152d9/application","descriptionHtml":"Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
PostHog is building every product companies need to run their business – and more than 100,000 companies have already installed us, mostly through word of mouth. Now we're ready to go find the ones who don't know about us yet. This role is the architect of that motion.
You'll help build and scale our playbook – from targeting logic to tooling stack to coaching cadence to disqualification criteria. You'll have a small, high-potential team, a product that engineers love, transparent pricing that makes outbound easier (not harder), and a set of sales leaders who care more about pipeline quality than activity volume.
If you've been frustrated by BDR orgs that optimize for dials-per-day and ignore whether the meetings are any good, this is the opposite of that. We want the pipeline and we want to not ruin our brand.
Why join this team specifically:
PostHog's brand is a true advantage – prospects have often heard of us or used the free tier. Cold outreach here is warmer than most.
The New Business Sales team has a strong track record. Your pipeline will be worked by experienced, technical AEs who know how to close.
We value learning, being creative and standing out in the market more than a playbook you've done a thousand times.
PostHog's culture is async, remote-first, and low-meeting. You'll spend your time building and coaching, not sitting in standups.
1–2+ years managing or formally leading a BDR/SDR team as a player-coach, with direct responsibility for hiring, coaching, and performance management. \"Team lead\" with informal authority counts if you can demonstrate coaching impact on rep performance. We are structured for speed and autonomy, so your leadership style needs to fit our model. This is less command & control, and more set context, build systems, coach selectively & judge on outputs.
Prior individual quota-carrying experience. You've personally prospected, booked meetings, and ideally closed deals. You know what good looks like because you've done it, not just managed it. You’ll do it again here.
Demonstrated ability to think in data, systems, and loops – even at a smaller scale. You know how to build the operating system the team runs on. You've designed or significantly improved a prospecting workflow, built reporting from scratch, or created a repeatable process where one didn't exist before.
Hands-on experience with Clay.com. You've built tables, enrichment workflows, and automated sequences in Clay – not just used outputs someone else created. If you can show us a Clay workflow you designed, that's a strong signal.
Salesforce proficiency. You can build reports, create custom fields, manage lead/contact data hygiene, and don't need someone else to configure your CRM.
AI-capable, with experience building automation. You've used AI tools (LLMs, AI writing assistants, workflow automation) to improve prospecting efficiency. You should be able to articulate specific examples: \"I built X using Y and it improved Z by W%.\"
Excellent written communication. Your outreach sequences, coaching notes, and Slack messages are clear, concise, and sharp. PostHog is an async-first company – writing quality matters.
Comfort with ambiguity and distributed ownership. This is a build role, not a maintain role. You'll be handed a rough playbook and expected to own it with your team, and you’ll have a company full of drivers who will give you “yes, and…” feedback
Strong preference, but-not a dealbreaker:
Experience in a product-led sales (PLS) or product-led growth (PLG) company where the buyer often starts with a free/self-serve tier before engaging sales.
Familiarity with selling to engineers and engineering managers as the primary buyer persona.
Experience with PostHog or competing products as a user or seller.
Own the outbound pipeline engine. Iterate on the targeting strategy, account selection criteria, and signal-based prioritization that tells your team who to reach and why now. Start with what doesn't scale, then systematize it.
Manage and develop a team of cracked BDRs, some of whom are here already (Andreas, Lorena, Melad). Coach daily on messaging, objection handling, qualification discipline, and outreach quality. Run weekly 1:1s focused on skill development, not just activity review. Build a ramp plan that treats the trajectory of learning as the primary leading indicator in the first 60 days.
Build the tooling and automation layer. Help design and maintain Clay.com workflows, Salesforce enrichment processes, and AI-assisted sequence generation without being a slop-cannon. You should be able to build a Clay table from scratch, not just use one someone else built.
Own the metrics and reporting. Build pipeline generation dashboards, track leading indicators (response rates, meeting quality scores, AE acceptance rates), and produce a weekly pipeline generation report. Instrument everything in PostHog, Lemlist, and Salesforce to make it so.
Coach qualification discipline. Implement and coach a qualification framework that ensures meetings passed to AEs are qualified. Disqualification is a feature, not a failure – build the taxonomy and track the reasons.
Iterate on messaging and channels. A/B test outreach sequences across email, LinkedIn, video, X, Discord, TikTok and creative channels. Maintain a living playbook that captures what works, what doesn't, and why.
Collaborate with the TAE team on target refinement. Use feedback loops from AE deal outcomes to continuously sharpen targeting.
You report to Ben (Revenue Leader). You'll work closely with Abhishek (GTM Engineer) on tooling and data infrastructure.
Helpful links:
PostHog BDR job listing – the role you'll be hiring for and managing
PostHog's ICP documentation – the targeting foundation you'll build on
PostHog's public handbook on how we work – the culture you'll operate within
#LI-DNI
Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
We’re looking for people (US - Central/Eastern 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\nProduct development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.\n\nPostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.\n\nWe started with open-source product analytics, launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products https://posthog.com/products, including:\n\n - PostHog Code https://posthog.com/code, the only AI devtool that understands your product, not just your codebase.\n\n - A built-in data warehouse https://posthog.com/docs/data-warehouse, so users can query product and customer data together using custom SQL insights.\n\n - PostHog AI https://posthog.com/ai, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.\n\nWe are:\n\n 1. Product-led. More than 450,000 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\nWHO WE'RE LOOKING FOR\n\nWe’re looking for people (US - Central/Eastern 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":"a4e7b7bc-e22a-4b4a-8797-5ea8e2186756","title":"Site Reliability Engineer - ClickHouse","department":"Engineering","team":"ClickHouse","employmentType":"FullTime","location":"Remote (EMEA)","shouldDisplayCompensationOnJobPostings":false,"secondaryLocations":[{"location":"Remote (UK)","address":{"postalAddress":{"addressRegion":"Remote (UK)","addressCountry":"United Kingdom","addressLocality":""}}}],"publishedAt":"2026-08-06T08:49:04.261+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"European Union"}},"jobUrl":"https://jobs.ashbyhq.com/posthog/a4e7b7bc-e22a-4b4a-8797-5ea8e2186756","applyUrl":"https://jobs.ashbyhq.com/posthog/a4e7b7bc-e22a-4b4a-8797-5ea8e2186756/application","descriptionHtml":"Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
PostHog Code, the only AI devtool that understands your product, not just your codebase.
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
Default alive. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
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.
We’re looking for people (EU/UK based) 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.
We run one of the largest self-managed ClickHouse installations on AWS, at petabyte scale, and we’re actively preparing it for the next 10–50× of growth. This role sits at the centre of that effort.
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 data-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).
Managing large fleets of EC2-based VMs, disks, and networking for data-intensive workloads
Improving operational tooling around deploys, schema changes, backups, restores, and incident response
Working closely with ClickHouse engineers to turn database-level needs into infra-level solutions
Reducing operational load by identifying repeat pain points and eliminating them through code and self-healing automation
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 are not afraid of working with stateful infrastructure
Prior experience with ClickHouse or other OLAP databases
Strong experience operating production infrastructure on AWS
Hands-on experience with VM-based systems (EC2), not just managed PaaS
Experience automating infrastructure using tools like Terraform, Ansible, or similar
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 a ClickHouse expert on day one. We’ll teach you the database internals, but you do need to enjoy owning complex infrastructure.
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\nProduct development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.\n\nPostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.\n\nWe started with open-source product analytics, launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products https://posthog.com/products, including:\n\n - PostHog Code https://posthog.com/code, the only AI devtool that understands your product, not just your codebase.\n\n - A built-in data warehouse https://posthog.com/docs/data-warehouse, so users can query product and customer data together using custom SQL insights.\n\n - PostHog AI https://posthog.com/ai, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.\n\nWe are:\n\n 1. Product-led. More than 450,000 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\nWHO WE'RE LOOKING FOR\n\nWe’re looking for people (EU/UK based) 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\nWe run one of the largest self-managed ClickHouse installations on AWS, at petabyte scale, and we’re actively preparing it for the next 10–50× of growth. This role sits at the centre of that effort.\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 data-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).\n\n - Managing large fleets of EC2-based VMs, disks, and networking for data-intensive workloads\n\n - Improving operational tooling around deploys, schema changes, backups, restores, and incident response\n\n - Working closely with ClickHouse engineers to turn database-level needs into infra-level solutions\n\n - Reducing operational load by identifying repeat pain points and eliminating them through code and self-healing automation\n\n - Participating in on-call and incident response, with a strong focus on making incidents rarer over time\n\n - You’ll have room to design and automate, not just respond to alerts.\n\nYou should join this team if you like deep ownership of production systems, and are not afraid of working with stateful infrastructure\n\n \n\n\nREQUIREMENTS\n\n - Prior experience with ClickHouse or other OLAP databases\n\n - Strong experience operating production infrastructure on AWS\n\n - Hands-on experience with VM-based systems (EC2), not just managed PaaS\n\n - Experience automating infrastructure using tools like Terraform, Ansible, or similar\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 a ClickHouse expert on day one. We’ll teach you the database internals, but you do need to enjoy owning complex infrastructure.\n\n \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":[]}}],"apiVersion":"1"}