Small team, unusually specific problems
Bilingual interfaces, payroll arithmetic that has to be exactly right, and an audit trail someone will read in a dispute. If that sounds like the good part rather than the tedious part, we should talk.
What the work is actually like
- You will work in two languages
- Every feature ships in Arabic and English. Reading Arabic is not a requirement; caring whether it renders correctly is.
- Correctness beats velocity
- A payroll run that is wrong by two currency units is wrong. Things here are built to be checked, not just shipped.
- Small surface, deep detail
- Six modules, one record. You will get to know a domain properly rather than skimming twenty of them.
- Written decisions
- Design notes and plans are written down before code. Arguing with a document is cheaper than arguing with a branch.
Open roles
There are no open roles listed right now.
We would rather show an empty list than advertise a vacancy that does not exist. If your work is relevant, send it anyway — it gets read, and it is kept on file for when a role opens.
How hiring runs
- 1
A short reply
Every application gets an answer, including the ones that are a no.
- 2
A conversation
What you have built and what you want to build next. Not a quiz.
- 3
Real work
A problem close to what the job is, paid if it takes more than an evening.
- 4
A decision
With reasons, either way, and quickly enough to be useful to you.