Legal problems, honestly stated, in Arabic and English.
The interesting work here is not the model. It is ranking bilingual legal text well enough that the amending agreement surfaces, and building a system confident enough to refuse.
Open roles
-
Legal engineer
A qualified lawyer who writes code, or an engineer who has sat through a diligence exercise. The playbooks, the trigger logic and the refusal rules are written by this role.
Riyadh -
Retrieval engineer
The hardest problem here is ranking Arabic and English legal text so the amending document is not at position 1,640. Search and IR background matters more than an ML title.
Riyadh or remote in-Kingdom -
Arabic NLP
Extraction from scanned bilingual documents, and defined-term alignment across two versions of one agreement. Genuinely unsolved, genuinely useful.
Riyadh -
Solutions lead
Sitting with firms while their playbook gets written down for the first time. Half consulting, half product feedback, and the deployments live or die on it.
Riyadh
Apply through the contact form with Careers selected and a CV attached. It is read by somebody who will reply, before it is filtered by anything.
Before you apply
- It is early
- Small team, unfinished product, and you will find things on this site described more confidently than they are built.
- We publish our failures
- The status page carries an incident where we failed silently for thirty-six hours. Writing those up is part of everyone's job here.
- No third-party audit yet
- We say so on the security page. If a badge on the wall matters to you, we do not have one.
- Arabic is not optional
- Not for every role, but the product is bilingual at its core and a team that cannot read the Arabic output cannot check it.