Member of Technical Staff
Sign up free to see how well your resume matches this role.
What you'll do
- Own product surface end to end: the interface, the backend that supports it, and the data model underneath.
- Decide what the right thing to build is, build it, and handle user feedback.
- Ship to production in your first week.
What they're looking 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 build genuinely good interfaces, and you can go as deep on the backend as the feature requires.
- You can hold a complicated workflow in your head and find the version of it that's simple enough to ship.
- Speed with taste. You ship fast, and you're opinionated about what not to build.
- You go to the source. You'll read the customer's actual documents, join the actual call, and look at hundreds of real outputs.
Nice to have
- founder or ex-founder
- founding team experience
- early engineer at a startup with a serious engineering culture
- EF / YC / Antler
- early or stealth-stage startup
- design sense you can defend
- open source you genuinely maintain
Summarised by NextRaise from the employer’s description, which follows in full below.
Full description from employer
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 Product Engineer owns the surfaces people actually work in. A coordinator planning a month of inspections across a fleet of auditors. A reviewer signing off on a technical file. These are dense, stateful workflows where the interface carries real consequences, and where the person using it has done the job for twenty years and will know immediately if the software doesn't understand it.
You own product surface end to end: the interface, the backend that supports it, and the data model underneath. Every customer runs the work differently, so there's no template to fall back on. You decide what the right thing to build is, build it, and are the one who hears about it when it's 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 build genuinely good interfaces, and you can go as deep on the backend as the feature requires.
You can hold a complicated workflow in your head and find the version of it that's simple enough to ship.
Speed with taste. You ship fast, and you're opinionated about what not to build.
You go to the source. You'll read the customer's actual documents, join the actual call, and look at hundreds of real outputs.
Signals we like, none of them required:
founder or ex-founder, founding team experience, early engineer at a startup with a serious engineering culture, EF / YC / Antler, early or stealth-stage startup, design sense you can defend, open source you genuinely maintain.
This is probably not for you if
You want a strict boundary between work and life. We run one of the most ambitious startup cultures in Europe: fast paced, extremely high ownership, and in person in Shoreditch.
You want a well-defined ticket handed to you each morning.
You want to specialise narrowly and stay in your lane.
What you get
Real equity, and compensation that reflects a high bar
Genuine ownership of product surface area from day one, with the founders in the room
Relocation support and visa sponsorship, handled properly
Lunch and dinner covered, 24/7 gym access, and any tool that makes you faster
A small team with high standards, high trust, and no politics
If this sounds like your kind of problem, apply. A short note on the hardest thing you've built goes further with us than a polished CV.
Company
Company facts come from this company's own listings. We only show what the postings themselves carry.