Build the system schools run on.
We are building the operating system for education in a region where getting this right changes how institutions are run. Small team, unusually direct work, and problems that are genuinely hard.
Kampala
Where we are
Remote-friendly
How we work
Long-term
What we build for
Four honest reasons, and one warning.
The work is consequential
Attendance registers, fee collection, exam results. When this software is slow or wrong, a school’s week is worse and a family gets the wrong information about their child. Very little software you will write has this direct a line to someone’s day.
Short distance to impact
You will speak to the people using what you build, and ship changes in days rather than quarters. No layer of product managers translating a school’s problem into a ticket by the time it reaches you.
Hard problems, honestly
Multi-tenant isolation, capability-based permissions, timetable constraint solving, offline-tolerant data entry on poor connections. These are real engineering problems, not a CRUD app with a design system.
Built to last
We optimise for the platform still being maintainable in five years — which means tests, audit trails and saying no to one-off customer branches. If that sounds slow, this will frustrate you.
Read this before you apply.
Write things down
Decisions live in documents and in code comments, not in someone’s memory.
Security is not a phase
Permission checks, tenant scoping and audit are part of the feature, not a hardening sprint afterwards.
Configuration over special cases
We do not fork the product for one school. We make the behaviour configurable for every school.
Say what is not done
Internally and to customers. A known gap is manageable; a surprise is not.
We hire ahead of the posting.
Rather than list requisitions that go stale, these are the areas where an exceptional person changes what we can do. If that is you, write to us — a specific message about your work beats a form every time.
Backend engineering
NestJS, PostgreSQL, Prisma. Multi-tenancy, authorisation, audit, background jobs and the data model underneath every school module.
Frontend engineering
Next.js, React, TypeScript, MUI. Dense administrative interfaces that have to be fast on a mid-range Android phone over an uneven connection.
Customer success
Onboarding schools, migrating their records, training their staff, and turning what you hear in a staff room into a product decision.
Sales & partnerships
Relationships with schools, school groups and education bodies across the region. Consultative, long-cycle, trust-led — not a call-list job.
How to get our attention
Send something you built and tell us what was hard about it and what you would do differently. We read every one of those. A generic CV with a cover letter addressed to “Hiring Manager” tells us nothing about whether you would enjoy this work.
Write to usNot looking to join, but know someone?
Referrals from people who understand the work are how small teams hire well. Point them at this page, or tell us about them directly.