We are a young company with production customers, which means your work goes in front of real users quickly and your name is on it. It also means the job is broader than a title suggests, and that suits some people and not others.
Read these before applying. If they sound like a downside, we are probably not the right place.
A discovery sprint that ends in a recommendation not to build is a successful sprint. We would rather lose the build than sell you a model you did not need.
If a system informs a decision about a person, the reason travels with the output. This is not an add-on we quote separately.
Whoever replies to an enquiry is someone who will work on it. There is no layer between the client and the engineer.
Handover means your team can run it. Monitoring, drift checks and documentation are part of the build, not an upsell.
If none of these fit but you think you should be here, write anyway and tell us what you have built.
You will train models on messy real data and ship them into production behind proper access controls. We care more about what you have deployed than what you have read.
React and TypeScript on the front, FastAPI and PostgreSQL behind it. You will own features end to end, including the schema and the tests.
We take students seriously, because both of our founders teach for a living. You will work on shipped systems with review, not a side project nobody uses.
Send something you have built and a paragraph on what was hard about it. That tells us more than a CV does, though send that too.
A link to something working, or a repository. A paragraph on the hardest decision in it. Your CV.
A reply within a week either way. Then a conversation with an engineer, then a paid short piece of real work.
We assess on work resembling the job. Nobody here inverts a binary tree under time pressure, so we do not test for it.
One email to the address below, with whatever you think shows your work best. A person reads every one.