PostHog Handbook Library / Forward Deployed Engineering

1,199 words. Estimated reading time: 6 min.

How forward deployed engineers work

The engagement lifecycle

Every engagement moves from opportunity through scoping and delivery to close. For each stage, see the engagement lifecycle.

Scoping engagements

Before delivery starts, every engagement needs a measurable outcome, a rough timeline, and a shared definition of "done." We write this down as a short brief and send it to the customer to confirm before committing. Scope small: it's cheaper to expand a tight scope than to unwind a loose one.

While scoping, we always ask: Is the described problem indicating a deeper pattern? Understanding the real problem space and our ability to identify structure problems that may cause long-term problems matters more than anything else in making an engagement succeed.

What it costs

Pricing depends on shape, effort, and commercial context, so exact numbers live in the FDE calculator and the commercial reference, not here. The philosophy:

Never invent an exact number on the spot. If a customer asks, say you'll get them a quote within a day and route it through the account owner.

Customers can also apply their prepaid credits toward an FDE engagement on a discretionary basis, provided there is justifiable account-level upside. This needs approval from Simon (Ben B as backup).

Principles

These are the defaults we bring to every engagement to deliver delightful customer outcomes.

Judgment over volume

As AI handles more of the production, an FDE's value is less in how much they can produce and more in the judgment they bring to it. When generation is cheap, the scarce skills are the ones a model can't supply for you:

We hire and grow for this, and we give people room to exercise it rather than a script to follow.

Improvement loop

Doing the work and improving how we work are the same activity. Every engagement teaches us something: a recurring question, a pattern that held, a place the process drifted. We capture those, gate the ones that hold, and graduate them to the right level of generality: a customer question becomes a topical reference, a cross-customer pattern becomes a lesson or a playbook entry, a hard-won rule becomes a standard.

The result is a team knowledge base that gains weight over time, so the floor is higher on every new engagement.

Compounding work

We earn the right to compound by getting it right for one customer first.

That means we focus hard on a single customer's problem and deliver real, measurable value for them as quickly as possible. Only once it has worked in the real world do we think about scaling it out to N customers. We don't try to make a solution general or scalable across the customer base until later, because generalizing too early usually means solving nobody's problem well.

In practice:

Sprints

The FDE team works in fortnightly Sprints that run from Monday to the Friday of the following week. Stand-ups are on Mondays and Wednesdays at 2.30pm UK / 9.30am ET.

On the closing Friday of a Sprint, a GitHub Action automatically closes the current Sprint's issue and creates a new issue for the next Sprint. FDE team members are expected to populate it before Sprint kick-off, which takes place at the Monday stand-up.

Working as a team

We're still new as a team and figuring things out as we go. To ensure everybody is pulling in the right direction and not duplicating work, we:

In general, at PostHog we bias for sharing imperfect work early, so that peers can help shape the direction of that work, rather than waiting for something to be perfectly ready before making it visible to the team.

Canonical URL: https://posthog.com/handbook/forward-deployed-engineering/how-we-work

GitHub source: contents/handbook/forward-deployed-engineering/how-we-work.md

Content hash: 351311132de7b0e2