Careers
Build the version that is allowed to say no
Most of this field optimises for output that looks convincing. We optimise for output somebody can defend in an archive, a registry or a court - which is a harder engineering problem and a much more interesting one.
How we work
- Remote, with UK/EU overlap hours.
- Domain experts in the room, not in a feedback form.
- Written proposals before code on anything structural.
- Nobody ships a feature they cannot explain the failure mode of.
Open roles
Four roles, all of them hands-on
We are small enough that every role touches the pipeline and talks to the people using it.
Fit
What we look for, honestly
- You are suspicious of output that looks too good
- You would rather ship a blank than a plausible guess
- You can read a domain expert's objection as a design constraint
- You write things down, because a restoration nobody can reproduce is not one
Nothing here fits, but you want to work on this?
Write to us anyway. Tell us about a time you shipped something less impressive because it was more correct - that is the whole interview, really.
support@docovly.com