PostHog Handbook Library / Forward Deployed Engineering

782 words. Estimated reading time: 4 min.

Forward deployed engineering overview

Forward Deployed Engineering (FDE) is PostHog's team of engineers who work with our biggest customers on short-term projects to deliver measurable, delightful outcomes. Depending on the engagement, that might mean hands-on engineering in their codebase (migrations, instrumentation, custom workflows, dashboards, experiments), or it might mean setting up the right foundations and enabling their team to follow PostHog best practices without ever touching code.

We work across the whole customer lifecycle, from new business and migrations with TAEs, to expansion with TAMs, to retention with CSMs. We then feed what we learn back into the product to benefit the wider PostHog user base.

We bias for action and hyper-focus on solving the customer's most important problem first, delivering the best measurable outcome. Compounding isn't the goal, but it's a natural by-product of excellent work: the patterns we see across engagements become reusable artifacts, skills, and product improvements, so the next customer starts further ahead.

FDE isn't just technical execution. AI has made people faster at building things, so the value we add is judgment, taste, and reasoning: prioritizing what matters most for the customer, helping them find the root of their problem, then planning and building production-ready solutions inside the customer's environment.

We sit between the customer, sales and CS, and product engineering. See how we work for how we operate day to day.

What makes a good FDE

FDEs need to navigate and operate autonomously within a customer's environment. We hire people who embody PostHog's values, but on top of that, the following characteristics make a good FDE:

What an FDE does

We don't maintain a fixed list of services; however we do track all our previous engagements so as not to reinvent the wheel. If a customer has a real problem where hands-on engineering can make a difference, we're interested in seeing if we can help. In practice, we often:

You can also check out our FDE Menu of Services, which covers the services FDE offers (though it's by no means an exhaustive list), how we've priced past engagements, and case studies from real customers.

What an FDE isn't

When FDE gets involved

The FDE team is small, so we're deliberate about where we spend time. Typical triggers:

Who to talk to

If you have a customer who might need FDE help, or you're trying to figure out whether something fits, the fastest path is to talk to the team directly. Bring the customer, the product area, and a one-line description of what they're trying to do. That's enough for us to tell you whether it's FDE-shaped and what happens next. If you're routing something formally from sales, CS, or engineering, the full intake path is in how to get an FDE involved.

Canonical URL: https://posthog.com/handbook/forward-deployed-engineering/overview

GitHub source: contents/handbook/forward-deployed-engineering/overview.md

Content hash: c92e93b9f159f540

Static reader notes
  • MDX_COMPONENT_STATIC_ADAPTER: Adapted interactive MDX components for static reading: PrivateLink, SmallTeam.