From your brief to an engineer in your team.
Four steps, run by people who understand forward deployed work. You stay in control of who joins your team.
The four steps
- 1BriefTell us the problem
Not only the job description: the problem, where the data lives, the systems involved and what is blocking you.
- 2MatchWe match the engineers
People who understand FDE work read the brief and match engineers whose shipped work fits the problem.
- 3InterviewYou meet the shortlist
You interview the engineers on your actual problem. You decide who joins your team.
- 4StartThey start in your team
In your environment, with your tools and your data. We stay in touch through the first weeks.
Step one
What makes a good brief
A job description tells us the title. A good brief tells us the problem, which is what we match on.
Write your briefThe outcome
What should be running, and for whom, when the engineer is done.
The systems
Where the data lives and which systems the work has to connect to.
The constraints
Security, compliance, cloud and location rules the engineer must work within.
The people
Who owns the problem, and who will use what gets built.
Before day one
Get the waiting out of the way
Most lost time in a new FDE's first weeks is waiting for access. These four things prevent it.
Name an owner
One person on your side who owns the problem and can make decisions.
Start access early
Accounts, network and security review requested before the start date.
Point at real data
Access to the real data, or a clear path to it, rather than a sample.
Introduce the users
The people who will use the result, so the engineer can meet them in week one.
Who reads our brief?
People who understand forward deployed work, not a general recruiting desk. The first thing we do is make sure we understand the problem, not only the job title.
Do we interview the engineers ourselves?
Yes. You interview every engineer on the shortlist, on your actual problem, and you decide who joins your team.
What do you need from us before an engineer starts?
Someone who owns the problem on your side, the people the engineer should work with, and a start on access requests so the engineer is not waiting on accounts in the first week.
Can the engineer work on site?
Yes. Tell us in the brief whether the role is remote, hybrid or on site, and where.
What if the fit is wrong?
Tell us as early as you can. We will talk it through with you and the engineer, and agree what happens next.
Hire FDEs
Tell us the problem. We will match the engineers.
Someone who understands forward deployed work reads every brief and replies with a view on the engineers you need, how many, and the hiring option that fits.