Fourteen people in Addis Ababa, working on the evidence under everyday agreements — the loans, permits and contracts that stop moving when a signature does. We are hiring across 5 roles.
Work that matters to someone outside this building. The whole problem rather than a ticket from it. An answer within ten days of the first call, with reasons — including when the answer is no.
Small enough that everyone knows which document broke, and why it broke.
Across engineering, compliance and the desks that sit with customers.
Tuesday to Thursday in the office; the rest of the week wherever you work best.
Four conversations and one paid exercise, then a decision either way.
None of them is a beanbag. This is a small company doing regulated work in a market that has never had it, which is either the appeal or it is not.
The documents moving through eFirma release loans, award permits and start jobs. When we are careless, someone waits a fortnight for a signature that should have taken an hour.
Registrars, loan officers and clerks are a taxi ride away, not a persona in a deck. Most of what is good about the product came out of watching one of them use it.
Proclamation 1205/2020 decides what a signature has to prove. Building inside that is harder and considerably more satisfying than building without it.
A team of fourteen cannot afford specialists in a queue. You will take something from the question to the thing running in production, and stay responsible for it.
Amharic is not a language file bolted on at the end. If you care about how a product reads in two scripts at once, there is a great deal of that work here.
Decisions, runbooks and post-mortems, in writing and without blame. It is how a small team keeps its reasoning after the person who had it moves on.
Everything below is how the company already runs, not an ambition for after the next raise. If any of it stops being true, this section changes.
Three days together in Addis for the work that needs a room, two wherever you are useful. No core hours beyond the overlap that makes that work.
Addis AbabaProposals go round as a page before they go round as a meeting. Anyone can disagree in the margin, including with the founders.
Async firstEvery change is read by someone else before it goes out, and it goes out weekly rather than quarterly. Small releases are how we keep them boring.
Weekly releasesOne rotation across the engineers, one week in six, compensated. Whoever is woken up gets to fix the cause rather than file it.
1 week in 6Private cover for you, a partner and children, from the day you start rather than after probation.
Equity for every full-time role, with the terms explained in plain language before you sign anything.
An annual allowance for courses, certification or a conference, and the days off to actually attend.
Twenty-two days plus public holidays, and a founder who will ask why if you finish the year with most of it left.
Sixteen weeks for a primary carer, four for a second, and a phased return that is planned rather than improvised.
The machine you work fastest on, and a monthly allowance for data and transport — the two things that actually stop work here.
We are asking you to spend a working day on us. The least we can do is say in advance exactly what the day consists of, and pay for the part that is real work.
Thirty minutes with whoever the role reports to. What you want next, what the job actually is, and whether the two have anything to do with each other.
An hour on work you have already done — a system you built, a policy you wrote, a rollout you got wrong. Bring something real; we would rather discuss it than a puzzle.
A scoped piece of work drawn from something we genuinely had to do, about half a day, paid at a day rate. You keep it either way, and we discuss it together afterwards.
A conversation with Saba or Dawit about where the company is going and what you would own in it. An offer or a no follows within two working days, with reasons.
Own the services a signature has to survive: envelopes, the audit trail, retention, and the API institutions build against. Python and PostgreSQL, on the parts that still have to be true in ten years.
Build the signing experience for someone on a mid-range Android phone and an uncertain connection — because that is who most signers are. TypeScript and React, bilingual from the first screen.
Hold the line between what the Proclamation asks for and what we ship. You will answer regulators, run customer security reviews, and have the final word on the claims made on this website.
Take a bank or an agency from a signed contract to their first sealed document, then to their thousandth. Part project management, part teaching, part finding out what the paperwork really looks like.
Own the Amharic across the interface, every notification a signer receives, and the documents themselves. Not translation after the fact — the second half of how the product reads.
Write to us anyway. Tell us what you have built or fixed and what you would want to own here — a paragraph is plenty. We read every one, and two of the people on this team arrived that way.
I came from the side of the room that says no. Here I get asked what the law actually requires before the thing is built, which is a considerably better use of a lawyer.
The nice thing about evidence is that it is checkable. Nobody has to be persuaded that my work is correct — they can verify the document and see for themselves.
No cover letter of the usual kind, no portal, no form that loses your work. An email to a person who will read it, and a reply either way.
