Forward Deployed Engineer

About the role

About Seamflow

Every plane, medical device, lift, battery and building has to be tested, inspected and certified before it reaches the world. It's the invisible layer that keeps the physical economy safe, and it still runs on Word documents, PDFs, spreadsheets and email. Seamflow is the software layer for that industry. We build AI-powered workflows for certification bodies, notified bodies and inspection companies: scheduling and resource planning, technical review, conformity assessment, field inspection, and document intelligence over messy real-world files.

Where we are:

- Live in production inside some of the largest enterprises in the industry

- $4.5M seed, 14x oversubscribed, co-led by Northzone and Initialized Capital, the funds behind Spotify, Klarna, Coinbase and Reddit. Angels include Charlie Songhurst and Mario Götze.

- Demand is outstripping what we can build. That's the reason this role exists.

The team

Most of our engineers were olympiad medallists in maths, physics or informatics before they were engineers. The team has come to us from Google, Amazon, X, Yandex, McKinsey and Bain, and from founding-engineer seats at startups that went on to multi-billion-dollar valuations. We hire against a very high bar, and this role exists to raise it further.

The role

A Forward Deployed Engineer thinks in customer workflows, not tickets or isolated features. Certification work cannot be understood from a desk. How a notified body actually runs a technical review lives in people's heads, in inherited spreadsheets, and in documents almost nobody outside the industry has read. Going and finding that out is the job, not the preparation for it.

You sit inside the operation, learn how the work genuinely gets done, and translate it into systems that hold up in the field. You run the call, write the spec, build the frontend, the backend and the model layer, and ship it. Then you watch someone use it and find out what you got wrong. You'll ship to production in your first week.

What we're looking for

We care far more about raw engineering strength than about matching a list of technologies. If you're excellent, we'll hire you whether you've spent the last three years in Rust, Go, Python, TypeScript, C++ or something we haven't heard of. Our stack is learnable in a fortnight. Judgement, speed and standards are not.

What we're actually screening for:

- You've built something hard and put it in front of real users. Not a prototype, not a course project. Something that ran, broke, and got fixed.

- You can sit with a non-technical expert and come away with the real workflow. Not the one on the process diagram. The one they actually follow.

- You build the whole thing. Interface, backend, data model, model layer. You don't hand off the half you find less interesting.

- Speed with taste. You ship fast, and you're opinionated about what not to build. Half of this job is knowing which customer request generalises and which one doesn't.