Engineering

Forward Deployed Engineer

The role in one line

You take a signed customer from their existing CRM, PRM or spreadsheet to a partner program running in production, and then feed what you learn back into the product.

London, UKFull timeRemote1 day a month in office£85,000 to £115,000

Remote. The whole team spends one day a month together in the London office, and that is the only day anyone is expected in.

This role pays £85,000 to £115,000 base. The range is the range: we do not hold back a band and we do not expect you to negotiate against yourself.

Apply for this role All open roles

Airstride promises customers their partner program is live in 24 hours. Someone has to make that true, and that someone is a forward deployed engineer.

You are the first engineer a new customer meets. You read their data wherever it currently sits, map it onto Airstride, connect their CRM, apply their branding and hand them a portal that is already populated with their partners, tiers, deals and collateral. Nobody starts from a blank canvas, which means the work of filling it lands on you.

This is not a support role with an engineering title. You write code, you ship it, and when a migration exposes something the product cannot do yet, you are the one who builds it.

What you will do

Run customer migrations end to end, from a first look at their data to a partner program in production.
Connect and debug CRM integrations across Attio, folk, Zoho, HubSpot, Salesforce, Pipedrive and Dynamics 365.
Write the import and transformation code that turns whatever a customer arrives with into a populated Airstride tenant.
Configure white-label branding and SSO so partners sign in to the customer's brand rather than ours.
Take the rough edges you hit during an onboarding and turn them into product changes, not runbooks.
Sit on calls with partnership leaders and translate what they describe into how the platform should behave.

What we are looking for

You have shipped production TypeScript, and you are comfortable in a React and Node codebase.
You have worked directly with customers before and you want more of it, not less.
You are fluent with APIs, webhooks and the shape of CRM data: objects, custom fields, ownership, pipelines.
You can hold your own on a call with a revenue team and explain a technical constraint without jargon.
You finish things. A migration that is ninety percent done is a migration that has not happened.

Nice to have

You have worked at a company selling to revenue or partnership teams.
You have built against Salesforce or HubSpot APIs in anger.
You have been the first or second engineer somewhere.

Why does this role exist?

Every PRM on the market hands a new customer an empty portal and an invoice for professional services. We decided not to do that, so the setup work moved from the customer to us. This role is that decision made real.

It also happens to be the best seat in the company for learning what the product actually needs. You see every customer's data, every integration edge case and every workflow we do not support yet, before anyone else does.

Posted 13 August 2026

How we hire

The same process for every role, published so you know what you are walking into.

Application
You send the form on the role page. Every application is read by a person, and you get an answer either way.
Intro call
A conversation with someone on the team about what you have done and what you want next. This is also your chance to work out whether you want the job.
The practical
A working session on a real problem from the role, done together rather than set as homework. No take-home tests you never hear back about.
Meet the team
You talk to the people you would work with, including a founder. We answer anything you want to ask about the company, the numbers and the plan.
Offer
If it is a yes from both sides, we make an offer and explain how we arrived at it.

Apply for this role

No account to create and nothing to upload. Send us your name, your email and a link, and a person will read it.