I moved to Dubai eight years ago thinking I understood the Middle East. I did not. And when I started taking on projects that served users in Riyadh, I realized I knew even less than I thought.
The first Saudi government portal I worked on, I made a mistake that still makes me cringe. I designed the entire interface left-to-right, in English, and figured I would just flip it for Arabic later. Flip it. Like it was a mirror. Like Arabic speakers were just English speakers who happened to read the other way. I spent two weeks on a layout that completely fell apart the moment someone pasted actual Arabic content into it. The text did not just reverse, the entire visual hierarchy collapsed. Call-to-action buttons that felt natural in English looked lost in Arabic. The information architecture I was so proud of assumed a reading pattern that half the users did not follow.
I had to rebuild the whole thing from scratch. That was a 5,000 AED lesson in humility.
The bilingual thing is not just about layout
If you are a senior product designer in Riyadh, or looking to work there, you already know the obvious stuff. The Vision 2030 momentum. The flood of government digitization contracts. The sheer volume of new startups that need someone who can actually ship, not just make Figma look pretty. What you might not know is the stuff that only becomes visible after you have shipped a few products that real Saudis use every day.
The bilingual thing is not just about layout. It is about trust. Saudi users have been burned by bad localization for years. Government apps where the Arabic feels like Google Translate. Bank portals where the switch language button literally breaks the navigation. When you design an interface that genuinely works in both languages, where the Arabic does not feel like an afterthought, users notice. I have had users message me specifically about the Arabic version of an app, thanking me because "finally something that reads like a human wrote it." That feedback means more than any NPS score.
I learned this the hard way on the Voyacher travel platform. Voyacher serves the Qatar and broader Gulf market, mostly Arabic-speaking travelers booking flights and packages. The design challenge was not just making a booking flow. It was building something that felt native to a user in Doha or Riyadh, not a skinned version of a Western travel site. Cultural patterns around travel booking are different here. Group bookings with extended family. Last-minute decisions during Eid breaks. Payment preferences that do not match the Stripe checkout you copied from a Dribbble shot. I redesigned the entire booking experience from the ground up, and the version that shipped works seamlessly RTL and LTR without a single layout hack. That came from failing at it once before.
Enterprise design in Saudi is a different sport
Another thing nobody tells you: enterprise design in Saudi is a different sport. At Valmont Industries, I led UX for five enterprise apps serving agriculture across 40 countries. Heavy stuff. Data tables with 47 data points per row. Irrigation dashboards that actual farmers look at at 5 AM before heading out. The kind of complexity where a bad dropdown menu literally costs someone a day of crop yield.
When I consolidated those five legacy apps into a single unified platform, the hardest part was not the visual design. It was convincing stakeholders that "clean and simple" does not mean "less powerful." Saudi enterprise clients, especially government-adjacent ones, tend to equate features with value. More buttons, more tables, more everything. Your job as a designer is to push back without sounding like you do not understand their business. That takes years to learn.
I built a 60-plus component design system to support that consolidation. The design-to-dev handoff time dropped 40 percent, which sounds impressive until you realize the previous handoff process involved annotated PDFs and Slack threads that spiraled into 200 messages. So yeah, 40 percent improvement. The real win was that the system worked. Engineers stopped asking me the same questions every sprint. The components handled edge cases I had not even thought of because the engineers had already solved them within the system. That is what a real design system does. It is not a Figma library you show off in your portfolio. It is a thing that makes your teammates not hate you.
The code advantage
These days I code more than I used to. React, Next.js, TypeScript. I use AI tools like Claude and Cursor and n8n to move faster, but I am not one of those designers who thinks AI replaces thinking. It replaces typing. There is a difference. When I built FinFlow, a savings app I designed and shipped as a freelance project, I wrote most of the frontend myself. It is hard to design a component you cannot build. And in Riyadh, where the talent market is still catching up to the ambition, being a designer who can also read a pull request gives you leverage that pure visual designers simply do not have.
The best part about designing for the Saudi market right now is that things are not settled. There is no dominant design pattern for government services yet. No one has figured out the perfect mobile banking flow for a population that skews young, digital-native, and impatient. Every project feels like you are building the first version of something, because in many cases you are. That is rare. In most mature markets, you spend your career optimizing existing patterns by two percent. Here you get to define the pattern.
The worst part is the timeline expectations. Everything is urgent. Everything was supposed to launch yesterday. You learn to say no a lot. You learn to ship the version that solves 80 percent of the problem and iterate live, because waiting for perfection means the project gets canceled or handed to someone who says yes faster. That is not a Saudi problem specifically, but the pace of transformation here amplifies it. Vision 2030 is not sitting around waiting for your design review.
If you are a senior product designer considering Riyadh, or already working there and wondering if your experience is normal: it probably is. Designing here means navigating bilingual interfaces, enterprise clients with deep skepticism, and deadlines that should be illegal. It also means shipping work that millions of people actually use, in a market where good design is genuinely scarce and genuinely valued.
I would take that trade any day.