Home About Case Studies Hire Me Contact
Currently available for select engagements

Hire UI/UX Designer in Jordan
Senior, direct, no layers

Hire a UI/UX Designer in Jordan — remote, senior-only delivery shaped for Jordan buyers: A UI/UX designer makes products people understand on first sight: research with real users, flows that remove friction, and interfaces your developers can actually build.

Jordan — UI/UX Designer

A senior ui/ux designer in Jordan

A UI/UX designer makes products people understand on first sight: research with real users, flows that remove friction, and interfaces your developers can actually build. For a buyer in Amman or elsewhere in Jordan, the engagement is remote by design: briefs, reviews, and handover happen over calls and shared documents, and the work is judged on delivered scope, not on office hours. Scopes are agreed in writing before work starts, and billing follows the payment routes businesses in Jordan normally use for cross-border remote work. Book a free discovery call and we will test the fit on one real workflow before any wider scope is agreed.

Jordan's tech scene is small but outward-looking: Amman-based startups, outsourcing teams, and family businesses that sell across the Gulf. Buyers here tend to be practical — they want work that plugs into the systems they already run rather than a rebuild, and they judge a remote hire on responsiveness and clean handover. For development work, the sharpest demand in Jordan is in startups and outsourcing teams that need senior builders who can own a codebase end to end.

Arabic is the working language, and English is widely used in Jordanian business, tech, and outsourcing teams, so briefs and documentation in English land without friction. Jordan runs on UTC+3 year-round, so a morning call in Amman lines up with mid-morning in the Gulf and a workable afternoon slot for much of Europe.

Jordanian buyers usually want a short written scope and a trial task before a longer retainer, and they judge the trial on communication as much as on output. Buyers in Jordan usually ask first who owns the code, and whether their own team can maintain it after handover.

What you get

What this engagement covers in Jordan

  • User research with your real customers, not personas invented in a workshop.
  • Flows mapped before screens: the path a user takes, where they drop off, and what removes that friction.
  • Interfaces designed for the devices and connections your customers have, including the payment and messaging surfaces in CliQ instant payments, JoMoPay, local bank apps, and WhatsApp Business storefronts.
  • A design system your developers can build from: components, states, and rules, not one-off screens.
  • Prototype testing with real users before build, so expensive mistakes are found in design, not after launch.
  • Handover files and guidance that developers can use without guessing.
The systems Jordan businesses actually run

Built on your stack, not on top of it

Design work runs in standard tools with files your developers can open and build from, and research grounded in your customers' devices, languages, and habits — including local surfaces in CliQ instant payments, JoMoPay, local bank apps, and WhatsApp Business storefronts where they shape the flow.

In Jordan, the local surfaces matter more than a generic stack list: CliQ instant payments, JoMoPay, local bank apps, and WhatsApp Business storefronts are where customers pay, message, and discover. The engagement covers those integrations first when they carry real orders or conversations, and treats the rest as secondary.

Work that touches customer data is handled under Jordan's Personal Data Protection Law (2023) and standard e-commerce consumer rules: access is kept to a minimum, data stays in approved tools, and anything that needs a lawyer's view is flagged rather than guessed at. This page is general information about services, not legal advice.

How it works

From kickoff to delivery in Jordan

  1. Research the real user

    Real customers, real tasks, real friction — observed before any screen is drawn.

  2. Map the flow

    The end-to-end journey is mapped and simplified, including payments and messaging through CliQ instant payments, JoMoPay, local bank apps, and WhatsApp Business storefronts where they sit in the flow.

  3. Design and test

    Screens are prototyped and tested with real users, and the friction points found are fixed in design.

  4. Hand over to build

    A design system and developer-ready files are delivered, with support while the build is underway.

Why Omer

Why hire Omer

  • Research with real users, not invented personas
  • Flows fixed before screens are polished
  • Designed for your customers' devices
  • A system developers can build from
  • Testing that finds mistakes before build
  • Remote working shaped for Jordan — UTC+3 overlap and communication in the languages your team uses
Outcomes

What changes in practice

The realistic outcome is a product people understand on first use: fewer drop-offs, fewer support questions about basics, and a design your developers can build without rework.

That is the standard this engagement is measured against: not a launch announcement, but work the team still uses months later, maintained by your own team with documentation handed over at the end. Browse all hire engagements or discuss your project in Jordan directly.

FAQ

Questions, answered

How do working hours work with a hire in Jordan?
Working hours are agreed at kickoff around the overlap between Jordan (UTC+3) and your schedule, with a weekly call in that window and written updates between calls, so nothing waits on a timezone.
How are payment and contracting handled in Jordan?
Scope is agreed in writing first, then billed against milestones by bank transfer or Wise in USD or JOD, against a written scope. Quotes are confirmed before work starts, and invoices are kept clean for your records.
Do you also build the product?
Design is the focus here, with developer-ready handover. Build can be scoped separately, and the design is made to be buildable either way.
How is design tested?
With real users doing real tasks on prototypes, before build. Their friction points drive revisions, not internal opinion.
Does design cover our local market?
Yes. Flows account for the devices, languages, and payment and messaging surfaces your customers use, including CliQ instant payments, JoMoPay, local bank apps, and WhatsApp Business storefronts.
Currently available for select engagements

Ready to get started?

The best way to explore working together is a quick conversation. Reach out through your preferred channel and let us discuss your project.