About the role
Capabilio turns what a person has actually demonstrated into a record they and their college can trust. That record is only worth something if every number in it can be traced back to real evidence, and if student data is handled with care. You will build and protect the system that does that.
You will work directly with the founder and own large parts of the product from design to production: the web app, the database and the APIs behind it. The stack is TypeScript, React and Next.js on Postgres with Supabase. AI models are used to generate and explain, never to invent facts.
You will also help lay the foundations for Android and iOS apps, so the choices you make now, such as how sign-in works and how logic is shared, decide how cheap mobile is later.
What the work looks like
A normal stretch might mean taking a feature from a rough idea to production: sketching the data model, writing the migration, building the API and the screen, adding tests, and watching it after release.
Other days are about keeping things true and safe: checking that a rating can be explained from its evidence, closing an authorization gap, or tracing why a student's number did not move.
You will read a lot of existing code, and you are expected to leave it clearer than you found it. Releases are small and frequent, and nothing ships without a test that would fail if it broke.
What you will do
- Ship features across the web app, APIs and database, from idea to production
- Keep scoring, ratings and every number in the product traceable to real evidence
- Protect student data: authorization checks, input validation and safe handling of secrets
- Write tests and keep releases safe and uneventful
- Prepare the codebase for mobile apps: token-based sign-in, shared logic and push notifications
- Watch production for errors, slow routes and AI failures, and fix what you find
- Review changes, your own and later other people's, with security in mind
- Write down decisions that other engineers will need later
What you bring
- Strong TypeScript and React, with Next.js experience
- Solid Postgres and SQL, and you have worked with row-level security or similar access rules
- You have shipped and run something real in production
- You write code others can maintain
- You build security in: validate input and check authorization on every route
- You ship in small steps and can estimate honestly
- You are comfortable owning a problem without a detailed spec
Nice to have
- Supabase experience
- React Native or Expo
- Experience with AI model APIs and measuring their output
- Testing with Vitest or a similar tool
- Experience with education or assessment products
Your first proof
After we read your application, this is the kind of problem you would work on. You see it now so nothing is a surprise.
Imagine a messy list of quiz attempts: some repeated, some with missing answers, some timed out. Write the smallest scorer you would trust to turn it into a rating, with tests. Tell us what it cannot tell you.
Your first months
- Week one: set up, read the codebase and ship a small fix to production
- Month one: take one real feature end to end, with tests
- Month two: review how authorization and secrets are handled across the APIs and fix the highest risks you find
- Month three: lead the first step towards mobile, such as token-based sign-in
- Ongoing: keep releases small, safe and uneventful
How we work
Capabilio is a small team building something people use to make real decisions about their careers. That shapes how we work.
- Show evidenceWe back claims with something real: a test, a number, a link, a user. When we do not know, we say so.
- Be honest about what is not workingBad news early is useful. A bug, a wrong question or a missed deadline is easier to fix when we hear about it.
- Keep the next step clearEvery task ends with a clear next step and an owner, so nothing sits waiting.
- Own your workYou are trusted with real problems and expected to see them through, and to ask for help early.
What you can expect from us
- Clear scope for each task
- Direct feedback on your work, including what is not working
- A direct line to the founder
- An answer from us either way after your interview
- This role is hybrid. We will agree the details of when and where we work together before you accept.
How we interview
Four steps, in this order. You always know which one you are in.
- 1Send proofA link to something you built and ran: a repository, a live app or a write-up. Tell us what you would change about it.
- 2We read itWe read the code, the history and your note, and ask what you would do differently.
- 3Write the small scorerThe brief under Your first proof: a scorer for messy quiz attempts, with tests. It is written down before you start.
- 4Talk it throughWe walk through your scorer together, then through a real part of our system and how you would change it. Either way, you hear the answer from us.