About the role
You will work on the real Capabilio codebase, a production TypeScript app used by students, and learn how it is built and kept safe. This is not a practice project: your changes can ship.
You will work with the founder, learn how a feature goes from idea to production, and get direct review on every change. We care about tests, clear code and honest bug reports, so those are the habits you will practise.
It is an unpaid internship, so we keep the scope clear, start with small well-defined tasks and make sure you learn something real from each one.
What the work looks like
Most work starts small: a bug with a clear way to reproduce it, a missing test, a confusing error message, or a loading state that feels broken. You read the code around it, make the change, write or update the test, and open it for review.
As you get comfortable the tasks grow into small features. Along the way you will learn how we handle sign-in, data access and secrets, and why each of those is done the way it is.
When you are stuck, ask early. A question after twenty minutes is better than silence after two days.
What you will do
- Fix bugs and ship small, well-tested features
- Add tests for behaviour that is not covered yet
- Improve error messages, accessibility and loading states
- Write clear bug reports and pull request descriptions
- Read code and ask questions until you understand it
- Learn how authentication, data access and secrets are handled, and why
What you bring
- You can write TypeScript or JavaScript and have built at least one project
- You know basic Git and SQL
- You can explain what you built and what you would change
- You ask for help early and take review comments well
- You can commit steady hours each week for the length of the internship
Nice to have
- React or Next.js
- Open-source contributions
- Experience writing tests
- Some Postgres experience
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.
Show us a project you built. In a short note, tell us one bug you found late, how you found it, and the test you would write to catch it.
Your first months
- Week one: set up the project locally and make a first small fix
- Weeks two to four: ship a few small, tested changes
- Month two: take a small feature from idea to review
- Ongoing: pick up bugs and tests alongside the founding engineer
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 a project you built, with a short note on one bug you found late and how you found it.
- 2We read itWe read your code and your note.
- 3Write the testThe brief under Your first proof: describe the test that would have caught your bug, and write it if you can.
- 4Talk it throughWe go through your project and your test together. Either way, you hear the answer from us.