Founding Deployment Strategist (DS)

Unhurdled; Dubai; Vor Ort; AED 300.000 - 600.000; Vollzeit

Zusammenfassung

Unhurdled is seeking a founding Deployment Strategist in Dubai to connect customer reality with our platform. You will work with customer teams and engineers to define problems, select starting points and ensure adoption is embedded in deployment. You’ll shape how we understand customers and deliver useful change.

You will build deployment plans, map flows, align ownership and drive measurable outcomes with lean resources. Early-stage, high-impact work awaits.

Qualifikationen

• You understand how work actually moves.
• You can find a problem worth paying to solve.
• You have made change stick with lean resources.
• You use AI and understand where it breaks.
• You earn trust through useful action.

Aufgaben

• Lead discovery with operators and decision-makers. Map the records, responsibilities and exceptions behind the work.
• Define a focused deployment: the user, the outcome, the approval boundaries and the evidence needed to judge success.
• Translate customer needs into a practical plan with engineers, and keep scope honest as new information appears.
• Help teams adopt the workflow through testing, training and a clear way to surface problems.
• Measure what changes after launch and use the findings to improve the deployment and our wider approach.

Jobbeschreibung

The best opportunity for AI is often hidden inside a routine that everyone has learned to work around. You’ll find it in the handover, the approval chain or the spreadsheet that holds an entire process together.

As a founding Deployment Strategist, you’ll connect that reality to what we build. You’ll work alongside customer teams and engineers to define the problem, choose the right starting point and make adoption part of the deployment. This role will shape how Unhurdled understands customers and delivers useful change.

What you’ll build with us

• Lead discovery with operators and decision-makers. Map the records, responsibilities and exceptions behind the work.
• Define a focused deployment: the user, the outcome, the approval boundaries and the evidence needed to judge success.
• Translate customer needs into a practical plan with engineers, and keep scope honest as new information appears.
• Help teams adopt the workflow through testing, training and a clear way to surface problems.
• Measure what changes after launch and use the findings to improve the deployment and our wider approach.

Who we’re looking for

You understand how work actually moves.

You have worked inside an operation or helped change one. You can trace a request through inboxes, records, approvals and handovers, including the exceptions people forget to mention. Freight, property or construction experience is especially useful.

You can find a problem worth paying to solve.

You distinguish an irritation from a recurring cost. You can establish a baseline, identify who owns the problem and who can approve the spend, then agree an outcome that the customer and engineers can both test.

You have made change stick with lean resources.

You have taken ambiguous customer or operational work through to adoption without a ready-made process. Tell us what you changed when the first plan met a busy team, conflicting priorities or an exception nobody had anticipated.

You use AI and understand where it breaks.

You have used AI to improve real work and checked the result. You can discuss inputs, tool access, evaluations and human approvals with engineers. You can test a workflow yourself and explain why a convincing demo might fail in daily use.

You earn trust through useful action.

Operators tell you what is really happening because you listen and follow through. You can run a difficult scope conversation, challenge a weak brief and help a reluctant user get started. You stay accountable after the workshop ends.

How we work

You choose useful work without waiting for a task queue. When a route closes, you investigate another, bring a recommendation and follow through. You ask for help before a blocked decision becomes a missed commitment.

You catch weak assumptions, generic reasoning and fabricated details. You check AI outputs before passing them to a colleague or customer. The tools can do more of the work; you still own its quality.

You tell the truth early.

You flag doubts while there is still time to act. You can disagree with a founder, admit uncertainty and change your mind when the evidence changes. Manufactured agreement helps nobody.

You take endurance seriously.

You want to do demanding work well over time. You protect the habits and recovery that sustain your judgement, make realistic commitments and raise unsustainable workloads before exhaustion makes the decision for you.

Your first chapter

Take a workflow from discovery to a deployment brief that a customer and an engineer can both use. Establish the baseline, agree ownership and help the first users make it part of their day.

Why join at the beginning?

You’ll help decide what we build, which customers we pursue and what good work looks like here. Expect incomplete systems, direct customer contact and decisions whose consequences you can see. We want people who enjoy making something work while the answers are still taking shape.

Early-stage experience carries more weight here than a corporate title. What matters is evidence that you can build, learn and take responsibility when resources are lean. If you developed that judgement inside a larger organisation or took an unusual route, show us the work.

YOUR NEXT CHAPTER

Let’s build
something useful.

Tell us about an operation you improved, the workaround you uncovered and what changed for the people doing the work. Include an assumption you got wrong and how you corrected it.