Small team, load-bearing work
The systems here run live sports and real academies with real revenue. That means the work is unusually consequential for a team this size — and unusually unglamorous. If you want a job where nobody notices when it works, you will fit.
Say the uncomfortable thing
Our public security page lists what we have not built. That habit starts internally: we would rather hear a hard estimate than a comfortable one.
Write the test that catches it
When something breaks in production, the fix is not done until there is a test that would have caught it. This is not negotiable and it is why our release notes read like engineering notes.
Build bilingual by default
Every string goes through a translation layer and every layout works right-to-left. Not as a phase — as the way you write the first version.
Talk to the people using it
Engineers here read support tickets. The distance between building something and hearing what it did is measured in days, not quarters.
Open roles
Nothing here fits?
Write to us anyway with something you built and why it was hard. We have made roles for people before, and we would rather meet you early than fill a vacancy late.
How we hire
- 01
A real conversation
Thirty minutes. What you have built, what you want next, what we are actually working on. No riddles.
- 02
Work sample
A scoped, paid task close to the real job — not a whiteboard algorithm you will never use again. Usually a day.
- 03
Review together
We go through your work with the people you would work with. You get to ask us the hard questions here.
- 04
Offer
A number, a scope and a start date. We do not negotiate by attrition.
Interested?
Send your CV and one thing you are proud of to careers@tkdsmena.com.