Flexible by default
Most roles are hybrid or fully remote. Choose the setup that helps you do your best work — a few days in the office when a build needs a room and a whiteboard, or working from wherever your thinking is sharpest.
Careers
Work that reaches production.
Meramia is a small, senior team of forward-deployed engineers working inside client organisations across the UAE and the wider GCC. No roles are open today. What follows is how the work is arranged, so the shape of it is clear before an opening appears.
Our policies
Trusted, supported, free to do the work.
Good engineering follows from conditions, not from encouragement. These six commitments describe the conditions we hold to, and they hold whether a role is open or not.
Trusted with the outcome
People here are handed problems, not tickets. You own a slice of the delivery from first sketch to hand-over, and the question at the end is whether it runs in production — never how many hours it took to get there.
Forward-deployed, beside operators
Engineering happens inside the client team and on the client platform. You sit with the people whose working day the system changes. It is the uncomfortable way to build software, and the fastest way to learn what actually holds.
Small teams, short lines
Teams stay small and senior on purpose. Nothing sits between a question and the person who can answer it, and the engineer closest to the work makes the call on how it gets built.
Thinking that gets written down
Architecture, trade-offs and the reasoning behind a decision are written before they are built, and revised when reality disagrees. The document is part of the engineering rather than a chore appended to it.
In region, in both languages
The work spans Arabic and English and stays inside the data boundaries our clients are held to. Regional context — regulation, language, how an organisation actually approves things — is part of the engineering, not a translation applied afterwards.
What we look for
Three things, weighed above a CV.
- 01
Judgment under uncertainty
Client problems arrive underspecified and the data is rarely what the brief claimed. We look for people who narrow a question before answering it, and who say plainly when a promising approach appears not to hold.
- 02
Craft that survives hand-over
Every system we build is handed to the operators who will run it after we leave. Code, models and documentation are written for the engineer who inherits them, which is a higher bar than making a demonstration work once.
- 03
Care with other people's data
We work inside client systems holding contracts, payroll and correspondence. Governance is not a phase at the end of a project; it is a habit that shows in how someone handles a credential, a sample export, or a screenshot.
Open roles
Nothing open right now.
We are not hiring at the moment. When that changes, each role will be described on this page — the work, the team it joins, and how the hiring conversation runs — and announced on our LinkedIn page the same day.
Following the LinkedIn page is the reliable way to hear about an opening first. If your work is close to what we do and you would rather not wait, the enquiry form reaches us directly — say what you build and where you have shipped it.
Vacancies0 open
This page is the register of record. An opening appears here the moment it is approved, with its own description; until then the count above stays at zero rather than collecting speculative titles.