Careers

A transcript is not
a feature flag.

Whollify is the system an institution runs on: admissions, courses, evaluation, messaging, attendance, records. When it is wrong, somebody's result is wrong. That is not a drawback of the job. It is the job.

The work

What you would actually be doing.

01

Records a degree rests on

Results, transcripts, and the full history of how each one was arrived at. Years later, somebody proves what they studied using what we stored. There is no version of that being roughly right.

02

Assessment that holds up

Thousands of students explaining their work to each other, live, and every one of those sessions scored, recorded and checked. Getting that to be fair at that volume is the most interesting problem here.

03

Built for the phone in their hand

Our students are on mid-range phones and data that comes and goes. If someone loses signal halfway through being assessed, that cannot cost them the mark. Most products treat this as an edge case. For us it is the normal case.

04

Every school, its own school

A university, a polytechnic and a bootcamp each run on Whollify without ever seeing each other. Twelve parts of a school join up into one place, and each institution decides which of them it turns on.

How we work

Four things we have had to decide.

Not values on a wall. Each of these came out of something we got wrong once and now choose deliberately.

Slow where it counts

We move quickly on how things look and slowly on anything that touches a student's result. Those two get very different standards, and we are comfortable being slow on the second.

Their conditions, not ours

Everything is tried on the same phones and the same connection our students have. If it only works on good office wifi, it is not finished.

The school owns its data

We look after it; we do not own it. Anything a school puts into Whollify it can take back out, and we built it that way rather than only promising it on a policy page.

Put it in front of a real class

New work goes to a real class doing real coursework, and we sit with them while it breaks. Almost everything we know came from that rather than from planning it.

Who we look for

Not only engineers.

You cannot build the system a school runs on with only people who have never run one. Half of what is hard here is institutional, not technical.

Engineers who want work where being wrong actually matters
People who have run a registry, an exams office, or a timetable
Teachers and lecturers who have felt every gap in what they were given to work with
Designers who can make something complicated feel obvious

No open roles right now.

We are heads down on the system. Roles are posted here when they exist, and never before, because an advertised job that does not exist wastes the time of exactly the people we want.

If you would be hard to replace, write to hello@whollify.com anyway.

Tell us what you have built or run. Not a cover letter.

Curious what you would be working on? See what the platform does.