Every job here starts with a reviewer account
Most software fails in the specification, not the implementation. That is the problem Moksy works on — and the way in is to do the work first. You apply as a reviewer, you review real plans, and we hire from the people already doing it well.
How it is structured
- 14 Disciplines we hire into (The roles the platform itself names when a plan says who you would need to hire.)
- 3 Levels in every one of them (Junior, mid-weight and senior in every discipline.)
- 1 Way in — the reviewer application (The reviewer application. There is no separate job application.)
Why it works this way round
A CV tells us what somebody says they can do. A review tells us what they actually caught — on a real plan, in their own field, where being wrong costs somebody money. By the time we offer anybody a job here, we have read their judgement.
It works in both directions. Before you commit to us, you have seen the work, been paid for it, and found out whether you want more of it. Nobody arrives on their first day surprised by what the job is.
The disciplines below are not titles invented for a careers page. They are the roles the platform itself names when a plan says who you would need to hire.
The fourteen disciplines
Junior, mid-weight and senior in each. Reviewers come from all of them.
Solution architect
How the whole thing fits together, and what it costs to be wrong.
Technical lead
Holding a build together and the people doing it.
Backend engineer
The part users never see and always feel.
Frontend engineer
The part they do see, on the devices they actually own.
Data engineer
Models, pipelines, and the questions they have to answer.
DevOps engineer
Getting it shipped, repeatedly, without drama.
Site reliability engineer
Keeping it up, and knowing first when it is not.
Security engineer
Finding it before somebody less friendly does.
QA engineer
The person who reads what was promised and checks.
UX designer
What the work is for, from the side of the person doing it.
UI designer
Making it legible, and making it ours.
Product manager
Deciding what not to build, and defending it.
Delivery manager
Sequence, dependencies, and the honest date.
Business analyst
Turning what somebody wants into what somebody can build.
The route in
Four steps, and the first one is the application.
Apply as a reviewer
This is the job application — there is no separate one. Your discipline, your level, and the categories you can actually judge. Everyone submits the same details through the same process, including anyone we want to move on quickly.
Get accredited
Calibration against work with known answers. Accreditation is held per category and it is earned, not granted — we cannot wave anybody through it, and would not want a reviewer we had.
Take real work, and get paid for it
Fees are visible before you accept, held in escrow while you work, and released when the review is accepted. This is paid work from the first one, not a trial.
We hire from the people doing the work
When a role opens in your discipline we look at who has been reviewing well in it. Some people are offered a job in weeks; some stay reviewers because they prefer it. Both are a good outcome.
What we will not do
- Ask you to do unpaid work as a test — reviews are paid from the first one.
- Grant accreditation because we like you. It is calibrated, or it is worth nothing.
- Skip the details for somebody we want quickly. The process is the same length for everyone.
- Hire you a level above where you are so we can pay you below it.
- Keep a vacancy open we have no intention of filling.