PRDuck:Join top engineers fromand more to improve your alignment with AILearn how to improve alignment with AI→

Meet your PMF Engineer.

Pixel duckling typing fast with finished boxes stacking up beside it

AI made writing code fast and easy.

Blindfolded pixel duckling throwing a dart nowhere near the board

What is hard is knowing what to build next.

So most teams still guess.

Two pixel chairs, one holding a duck and one sitting empty

For most of software history, that meant getting them on a call.

Find them. Convince them. Send the invite. Wait. And by then the problem is weeks old.

Pixel duckling beside a pipeline funnelling envelopes into a neat stack

That was fine when shipping took months.

Now the bottleneck is not can we build it. It is what should we build.

Pixel duckling in a headset interviewing another duckling across a table

So we made a role for it.

They help you catch your best users while the thing they love or hate is still on the screen.

Pixel duck pointing from a pinned sketch to the finished thing that matches it

You ship what users actually asked for.

Somebody had to invent the job first.

Forward Deployed Engineer. Growth Engineer. GTM Engineer. Each one was a single company's answer to work the industry had no title for yet.

Pixel-art briefcase with a hard hat and a visitor badge

Forward Deployed EngineerPalantir

Palantir put engineers inside the customer instead of behind the product.

Pixel-art chart with one line rising steeply

Growth EngineerFacebook

Facebook gave one team signups instead of features. Now every company has one.

Pixel-art funnel dropping envelopes through to a sealed one

GTM EngineerClay

Clay needed it three years ago. Now it is a line in everyone's budget.

A forward-deployed engineer, but for product discovery.

The job

So what do they actually do?

Discovery stops being something you schedule. It runs continuously, while people are still inside the product.

01Find

Find the usersworth listening to

They open your analytics and pull the cohort whose feedback is worth having. Not whoever happens to answer a survey.

02Trigger

Catch them inthe moment

The ask fires the next time one of those users touches a flow you care about. Inside the product, while the thing they love or hate is still on the screen.

03Translate

Turn it intosomething buildable

Users talk it through with agents that know your codebase and your priorities. Your PMF engineer steps in with the follow-ups that turn a complaint into an implementation-ready PRD.

04Close

Then closethe loop

Did you ship it. Did the users who asked come back and use it. Did the product get better. That answer decides what gets asked next.

Pixel duck in glasses and headphones working at a laptop

They own

The asking

Which users get asked and when the ask fires. Plus the evidence sitting under every PRD that reaches your queue.

Three pixel ducks working a planning board together

You still own

The building

The roadmap and the code. Your PMF engineer hands your team a ranked queue. They do not take the decision off you.

You are not short of

feedbackthe right feedback

From the users who matter, at the moment it is still true.

Learn from people who have done 0 to 1.

We embed one of our own with a small number of teams each quarter.