Software engineering in Dubai
Our Dubai office covers Gulf business hours, which matters more than it sounds: a design decision that needs your team and ours in the same conversation is the difference between a same-day answer and a three-day round trip.
What being here actually changes
Plenty of firms list a Dubai address. The parts that make a practical difference are unglamorous: overlapping working hours, awareness that the regional working week does not always match the calendar your offshore team uses, and having sat in a room with a UAE regulator's requirements rather than reading about them.
It also changes what we assume about the build. Arabic support is not a late localisation task — right-to-left layout affects component design, iconography and data entry from the first wireframe, and retrofitting it is disproportionately expensive. If your users include Arabic speakers, that is a design constraint rather than a translation step.
What we work on regionally
Financial services and fintech
Payments and lending platforms built for regional schemes and the reporting obligations that come with a UAE licence.
Government and semi-government
Citizen and enterprise systems where data residency and procurement rules shape the architecture before anything is designed.
Logistics and trade
Freight, customs and port-adjacent systems, where the integration surface is regional and the documents are unforgiving.
Retail and hospitality
Commerce and booking platforms with multi-currency, multi-language and regional payment method support.
Bilingual product work
Arabic and English interfaces where RTL is designed in rather than bolted on, including mixed-direction content.
Cloud with residency constraints
Architectures constrained to UAE regions, including the exit and oversight evidence regulators expect.
Working across the region
The practical constraint on a Gulf engagement is usually the working week rather than the timezone. Where your organisation runs a Sunday-to-Thursday week and part of a delivery team does not, Thursday afternoon and Friday become a scheduling problem, and it is better resolved as a working agreement at the start than absorbed as friction for a year.
We also plan for Ramadan and the Eid holidays as fixed constraints rather than surprises, because pace and availability genuinely change and a schedule that ignores them is a schedule that slips.
Gulf business hours covered from Dubai, with US hours from California
Working-week overlap agreed explicitly at engagement start
Ramadan and Eid planned into the schedule, not discovered in it
Arabic and RTL treated as a design constraint from the first wireframe
Data residency established with your compliance function before design
Common questions
People. It is one of our two locations, alongside California. For work with UAE regulatory or residency constraints, having engineers in the timezone who have dealt with those requirements is the substantive part — an address on a website is not.
Keep exploring.
Let's build what's next.
Tell us where you are and where you want to be. We'll bring the engineering, the AI, and the governance to get you there.