FDEGulf
Menu ☰
ProgramCertificateNewsletterGuideGet Assessed for FreeHire FDEsReserve your seat

The Gulf is deploying AI. Be the Forward Deployed Engineer who ships it.

25 hands-on lessons · 5 live workshops · your own AI project · earn a certificate

Starts  · Only 25 seats · early bird until December 14

// who it's for

  • > going for an FDE roleFDE roles in Dubai pay $80k–140k a year. Prepare yourself for change.
  • > moving into AINo ML background needed if you already ship production code.
  • > staying where you areYour company is starting AI projects. Let them pay for you →

How much do Forward Deployed Engineers earn in the Gulf?

FDE Gulf estimates · annual salaries in USD.

Dubai / UAE

$80k–140k

Commercial and consulting deployment roles.

Doha / Qatar

$76k–125k

AI engineering roles in a market shaped by government deployments.

Abu Dhabi / UAE

~$100k

Housing and relocation vary by employer.

Riyadh / KSA

~$115k

Check whether an offer includes housing and transport allowances.

Some FDE roles in the Gulf.

14 roles · 12 companies · 4 cities ·

The FDE Gulf Program

A five-week online program for engineers who want to deploy AI inside a client’s business. Follow one project from the first scoping call to the moment another team can operate it.

Become the engineer a client trusts to deploy AI.

Change what you can show in your next interview. Walk a hiring manager through a decision you owned, a failure you recovered from and a result the client could measure.

  1. 01Engineer

    Describe a client workflow and establish its baseline.

  2. 02Field-ready builder

    Connect the system to real constraints and prove it works.

  3. 03FDE Gulf Certified

    Earn nine Skill Cards and pass the capstone review.

  4. 04Your next role

    Bring a redacted case study and a verifiable credential to interviews.

The field curriculum.

January 4 – February 5, 2027 · 25 lessons · 5 live workshops

Goal
Map the Gulf client landscape and ship a first prototype on in-region models and tools.
Progression
landscape → hosting → context → tools → prototype
Promise
Arrive at a Gulf client with a working prototype in 48 hours.
Live workshop, Thu Jan 7

MCP server over a Gulf service API.

The Gulf Deployment LandscapeBuyers · Sovereign AI · Estates · Vendor Rules · Calendar
  • Buyers ministries and authorities, semi-government groups, banks and insurers, energy, family conglomerates, who owns budget vs who owns IT
  • Sovereign AI national AI strategies, in-country compute, G42 and Core42, HUMAIN, local-model preference, what "sovereign" means in a tender
  • Estates Microsoft, Oracle and SAP footprints, on-prem data centres, government clouds, Arabic-first legacy applications
  • Vendor Rules vendor registration, Etimad, local partner, in-country value and local-content requirements
  • Calendar Sunday–Thursday vs Monday–Friday weeks, Ramadan hours, national-day and year-end freezes, Hijri dates in systems
Models and Hosting in RegionModel Selection · In-Region Endpoints · Sovereign Cloud · Self-Hosting · Arabic Models · Cost
  • Model Selection capability tiers, reasoning effort, context window, multimodal input, open-weight vs hosted, own-task tests over benchmarks
  • In-Region Endpoints hyperscaler regions in UAE, KSA, Qatar and Bahrain, model availability lag, tool calling, structured outputs, batch and caching support by region
  • Sovereign Cloud national and government clouds, Core42, HUMAIN, when a tender requires them, onboarding lead time
  • Self-Hosting open-weight models, vLLM, GPU sizing, quantization, throughput, patching and upgrades
  • Arabic Models Jais, ALLaM, Fanar, Falcon Arabic, MSA vs Gulf dialect, frontier vs regional model, bilingual prompts
  • Cost input, output and cached tokens, cost per task, provisioned throughput, quota planning
Context and HarnessInstructions · AGENTS.md · Context Assembly · Coding Agents · Permissions · Headless Runs
  • Instructions system prompt structure, constraints, examples, output contracts, prompt versioning
  • AGENTS.md standing instructions per repo, scope, client conventions, shared team guidance
  • Context Assembly what to load and when, retrieval vs long context, filtering tool results, compaction, filesystem offloading, memory limits
  • Coding Agents Claude Code, Codex, Cursor on an unfamiliar client codebase, repo exploration, plan before edit
  • Permissions allow and deny rules, sandboxing, hooks and test gates, offline work, no client data in public tools
  • Headless Runs CLI and SDK mode, scripted tasks, CI jobs, agent SDKs vs own loop
Tools and MCPTool Design · MCP Servers · Auth · Agent Skills · Tool Results
  • Tool Design naming, schemas, descriptions, granularity, errors a model can act on, read vs write tools
  • MCP Servers tools, resources, prompts, stdio vs HTTP transport, wrapping REST and SOAP, hosting
  • Auth OAuth, API keys, per-user tokens, on-behalf-of, scopes
  • Agent Skills packaged procedures, progressive loading, scripts with instructions, client playbooks as skills
  • Tool Results pagination, truncation, filtering, large payloads, code execution instead of many calls
The 48-Hour PrototypeUse-Case Pick · Baseline · Thin Slice · Demo · Next Step
  • Use-Case Pick volume, error cost, data availability, clear owner, what to reject
  • Baseline handling time, error rate, 30 real cases, manual labels
  • Thin Slice one input, one path, real data sample, hard-coded edges, no UI polish
  • Demo live on client data, shown failures, objections, decision log
  • Next Step what to rebuild, what to keep, risk list, acceptance metric

Goal
Work inside the client’s environment and connect to the systems, identities and registries it runs on.
Progression
access → identity → legacy data → national rails → tenant deployment
Promise
Make the first real call into client systems without breaking their rules.
Live workshop, Thu Jan 14

From VDI to the first call against a legacy API.

Working Inside the Client EnvironmentAccess · Networks · Tenants · Dev Setup · Change Control
  • Access VPN, VDI, jump hosts, client-issued laptops, service accounts, access-request lead times
  • Networks private endpoints, egress allowlists, proxies, TLS inspection, air-gapped setups, package mirrors
  • Tenants client cloud subscription, landing zones, in-country regions, on-prem GPU
  • Dev Setup client Git and CI, branch rules, container registry, secrets vault, no local data copies
  • Change Control CAB, release windows, freeze periods, ticketing, approval chain
Identity and PermissionsSSO · RBAC · Agent Identity · Secrets · UAE Pass, Nafath, Tawtheeq
  • SSO OIDC, SAML, Entra ID, group claims, conditional access
  • RBAC roles, row- and document-level security, inheritance, least privilege
  • Agent Identity service principal vs on-behalf-of user, token exchange, scoped credentials, per-tool permissions
  • Secrets vaults, rotation, managed identities, no keys in prompts or logs
  • UAE Pass, Nafath, Tawtheeq national digital identity, login and signing flows, citizen- and resident-facing services, sandbox access, when an agent may act for a user
Enterprise Systems and Legacy DataCore Systems · APIs · Databases · Files · Sync
  • Core Systems SAP OData and BAPI, Oracle EBS and Fusion REST, Dynamics 365, ServiceNow, core banking and insurance platforms
  • APIs REST, SOAP, GraphQL, pagination, rate limits, undocumented endpoints, API gateways
  • Databases read replicas, views, schema discovery, SQL generation guardrails, query cost limits
  • Files SFTP drops, CSV and Excel exports, SharePoint, shared drives, email attachments
  • Sync batch vs change data capture, webhooks, queues, freshness, reconciliation
Gulf Identifiers, Registries and RailsNational IDs · Company Records · E-Invoicing · Payments · Addresses
  • National IDs Emirates ID, Iqama and Saudi national ID, QID, formats, expiry, Arabic and English name fields
  • Company Records trade licence, commercial registration, establishment and tax registration numbers, lookup and verification
  • E-Invoicing ZATCA Fatoora phases, XML and QR requirements, UAE e-invoicing model, what an agent may generate vs submit
  • Payments IBAN formats, instant-payment schemes (Aani, sarie), WPS payroll files, reconciliation
  • Addresses Saudi National Address, Makani, PO boxes, free-text addresses, geocoding
Deploying in the Client TenantPackaging · Infrastructure as Code · CI/CD · Runtime · Model Gateway
  • Packaging containers, base images, dependency pinning, offline builds
  • Infrastructure as Code Terraform, client modules, environments, drift
  • CI/CD client pipelines, approvals, artifact promotion, secrets injection
  • Runtime Kubernetes, serverless, managed agent runtimes, autoscaling, GPUs
  • Model Gateway one endpoint for many providers, keys, quotas, logging, fallback routing

Goal
Build agents that read Arabic and English, act through workflows and hand risky decisions to people.
Progression
documents → retrieval → agent loop → human review → channels
Promise
Give users cited answers in their language, with a person in control of every risky step.
Live workshop, Thu Jan 21

Arabic and English document pipeline to a cited answer.

Arabic Text and DocumentsParsing · OCR · Arabic Text · Extraction · Validation
  • Parsing PDF text vs scan, layout models, tables, stamps and signatures, vision-model parsing
  • OCR Arabic print and handwriting, mixed-script pages, confidence scores, human-review threshold
  • Arabic Text normalization (alef, hamza, ta marbuta, diacritics, tatweel), Arabic-Indic digits, code-switching, Arabizi, dialect vs MSA
  • Extraction schemas, structured outputs, name transliteration variants, Hijri and Gregorian dates, ID and IBAN formats
  • Validation cross-field checks, source spans, confidence, exception queue
Retrieval in Arabic and EnglishChunking · Cross-Lingual Search · Reranking · Permissions · Grounding
  • Chunking structure-aware splits, tables, metadata, parent-child, bilingual documents
  • Cross-Lingual Search multilingual embeddings, BM25 with Arabic normalization, hybrid, query rewriting, Arabic question over English sources and the reverse
  • Reranking rerankers, Arabic support, top-k tuning, latency trade-off
  • Permissions ACL-aware retrieval, per-user filters, tenant isolation
  • Grounding citations, source spans, answer language vs source language, stale documents, refusal when nothing is found
Workflow and the Agent LoopDecomposition · Patterns · State · Tool Orchestration · Errors · Idempotency
  • Decomposition process to steps, deterministic vs model steps, where an agent is the wrong tool
  • Patterns prompt chain, router, parallel, orchestrator-worker, evaluator loop, subagents with isolated context
  • State case state, checkpoints, resumability, durable execution, queues, workflow engines such as Temporal
  • Tool Orchestration plan-act-observe loop, parallel calls, tool-choice control, stop conditions, max turns, token and cost budgets
  • Errors tool failures, malformed output, retries with feedback, loop detection, replayable runs
  • Idempotency write actions, dedup keys, exactly-once effects, compensation
Human in the LoopApprovals · Escalation · Review UI · Feedback Capture · Audit
  • Approvals maker-checker, thresholds by amount or risk, dual control, delegation of authority
  • Escalation confidence triggers, exception queues, SLA timers, handoff with full context
  • Review UI diff view, source evidence, edit and approve, bulk actions
  • Feedback Capture corrections as labels, reason codes, feeding evals
  • Audit who approved what, immutable log, replay
Channels and Arabic UXTeams · WhatsApp · Email and Documents · Embedded · RTL and Voice
  • Teams bots, adaptive cards, message extensions, tenant app approval
  • WhatsApp Business Platform API, templates, 24-hour window, opt-in, handoff to a human agent
  • Email and Documents inbox triggers, drafted replies, Outlook add-ins, generated Word and Excel in both languages
  • Embedded widgets in the client's existing app, SSO pass-through, streaming UI
  • RTL and Voice bidirectional rendering, language switching, mixed-language replies, Arabic speech input, dialects

Goal
Prove the system is accurate, reliable, secure and compliant before anyone depends on it.
Progression
evals → reliability → security → data residency → sector rules
Promise
Bring evidence to the release decision, not a demo.
Live workshop, Thu Jan 28

Release decision with bilingual evals and a red team.

Evals in Two LanguagesDataset · Arabic Graders · Agent Evals · Regression · Online
  • Dataset real cases in Arabic, English and mixed, dialect samples, costly mistakes, versioning
  • Arabic Graders normalization before matching, judge-model bias toward English, native-speaker calibration, transliteration tolerance
  • Agent Evals task success, tool-call correctness, trajectory checks, step count and cost
  • Regression baseline vs candidate, per-case diff, per-language threshold, CI gate
  • Online sampled production traces, user feedback, drift by language
Reliability EngineeringTimeouts and Retries · Fallbacks · Rate Limits · Safe Writes · Failure Injection
  • Timeouts and Retries budget per step, backoff, jitter, retry limits
  • Fallbacks secondary model, cached answer, rule-based path, human takeover
  • Rate Limits quotas, queues, backpressure, concurrency caps, batch windows
  • Safe Writes idempotency keys, dry-run mode, confirmation before irreversible actions, compensation
  • Failure Injection tool down, slow API, bad document, provider outage, expected behaviour for each
SecurityThreat Model · Prompt Injection · Tool Permissions · Data Leakage · Red Teaming
  • Threat Model assets, trust boundaries, OWASP Top 10 for LLM applications
  • Prompt Injection untrusted documents and emails, tool-output injection, instruction isolation, content filters
  • Tool Permissions least privilege, read-only defaults, allowlists, sandboxed code execution
  • Data Leakage PII redaction, logging hygiene, cross-tenant retrieval, exfiltration through tools and links
  • Red Teaming attack set in Arabic and English, automated runs, findings to fixes, the client's penetration test
Data Residency and PrivacyClassification · UAE · KSA · Qatar · Cross-Border
  • Classification national and client schemes, NDMO levels, Dubai data classes, tagging at ingestion
  • UAE PDPL, DIFC and ADGM regimes, free zone vs onshore
  • KSA PDPL, transfer rules, in-Kingdom hosting expectations
  • Qatar PDPPL, special-nature data
  • Cross-Border where prompts, logs, embeddings and backups live, model-provider data handling, residency per component
Sector RulesGovernment · Banking · Insurance and Health · Cyber Controls · Evidence
  • Government government cloud requirements, clearances, Arabic-first service standards
  • Banking CBUAE, SAMA and QCB expectations, outsourcing and cloud rules, model-risk management
  • Insurance and Health health-data localisation, patient-data rules, regulator approvals
  • Cyber Controls NCA ECC and cloud controls, UAE information-assurance standards, penetration tests
  • Evidence audit log, DPIA input, access reviews, retention and deletion, what the auditor asks for

Goal
Release safely, run the system in production and hand it to a team that can own it.
Progression
release → observability → incidents → handover → career
Promise
Leave a system the client’s team can run without you.
Live workshop, Thu Feb 4

Incident drill and capstone review.

Release EngineeringVersioning · Shadow Mode · Canary · Feature Flags · Rollback
  • Versioning prompts, models, tools and eval sets in Git, pinned model versions, changelog
  • Shadow Mode run beside the human process, compare outcomes, no writes
  • Canary first users, traffic split, stop conditions, expansion gates
  • Feature Flags per-team and per-capability switches, kill switch
  • Rollback previous-version restore, data and state compatibility, timed rehearsal
Observability and CostTracing · Metrics · Quality Signals · Alerts · Token Economics · Caching
  • Tracing OpenTelemetry GenAI conventions, spans per model and tool call, trace IDs across client systems
  • Metrics latency, time to first token, p95 targets, error rate, tool success rate
  • Quality Signals approval and edit rates, sampled grading, escalation rate
  • Alerts thresholds an operator can act on, noise control, ownership, dashboards for engineers and for the business owner
  • Token Economics cost per case, input vs output, context growth, small model first, escalation rules, batch for offline work
  • Caching prompt caching, response and embedding cache, invalidation, provisioned throughput, load tests
Incidents and OperationsRunbooks · Triage · Provider Events · Postmortem · Hypercare
  • Runbooks symptoms, checks, fixes, contacts, tested by a second engineer
  • Triage model, tool, data or infrastructure fault, reading a trace, reproducing from logs
  • Provider Events outages, rate-limit changes, model deprecations and migrations, re-running evals
  • Postmortem timeline, root cause, new eval case, added guardrail
  • Hypercare first-week support, issue queue, fix vs change request
HandoverCode and Infra Transfer · Documentation · Local Team Training · Outcome · Reusable Kit
  • Code and Infra Transfer repos, IaC, pipelines, secrets ownership, licences
  • Documentation architecture, data flows, eval suite, runbook, known limits
  • Local Team Training client engineers run a release and a rollback unaided, operators handle exceptions, Arabic operator guides, national-talent upskilling requirements
  • Outcome baseline vs live, sample sizes, what the numbers do not prove
  • Reusable Kit templates, MCP servers, eval harness, lessons back to the product team
Becoming an FDE in the GulfDecomposition Interview · System Design · Live Build · Portfolio · Regional Employers
  • Decomposition Interview vague client problem to plan, clarifying questions, trade-offs out loud
  • System Design agent in a regulated client environment, residency, failure modes
  • Live Build timed task on unfamiliar data and APIs
  • Portfolio capstone case study, repo, redaction, Skill Cards
  • Regional Employers labs and hyperscalers, sovereign-AI companies, integrators and consultancies, in-house teams at banks and government entities

Who it’s for

audience.diff · 6 changesfde-gulf/audience.md +3 −3
  1. 01+Engineers who already write production code and want to deploy AI inside client organizations in the Gulf.
  2. 02+Engineers who use coding agents such as Claude Code, Codex or Cursor and want to own delivery past the prototype.
  3. 03+Practitioners who want feedback on a running system and its handover from people who deploy for a living.
  4. 04−Beginners looking for an introduction to coding.
  5. 05−Anyone looking for an introductory AI course or pure theory.
  6. 06−Anyone who needs a certificate based on attendance.

The journey · 9 Skill Cards · 1 certificate

Engineer → FDE

After FDE Gulf you become the engineer people trust when AI has to work inside real client systems, under Gulf data rules and on a real deadline. Nine Skill Cards prove each step, and one certificate shows you can take a deployment from the first conversation to handover.

  1. SC / 01 · Client Scoping

    Turn a vague client request into a scoped, testable brief

    • Map the process, measure a baseline (cycle time, error rate, cost per case) and inventory the data you can access
    • Write a one-page brief with a named owner and an acceptance test on a labelled sample
  2. SC / 02 · Gulf Systems Context

    Map the data, hosting and identity constraints of a Gulf deployment

    • Classify data under UAE and KSA PDPL and Qatar’s PDPPL, and choose in-region endpoints or sovereign cloud
    • Plan UAE Pass or Nafath sign-in and record every decision in a residency diagram with named sign-offs
  3. SC / 03 · System Design

    Design an LLM system the client can run, afford and secure

    • Choose models, RAG or long context, MCP tool calls and structured outputs, with a token cost per task
    • Record each trade-off in an architecture decision and build a thin end-to-end slice first
  4. SC / 04 · Retrieval Quality

    Make every answer traceable to the client’s own sources

    • Run Arabic OCR and normalization, then hybrid BM25 and embedding search with a reranker
    • Measure recall@k and citation precision on a golden set, and trace bad answers to their chunk
  5. SC / 05 · Production Evals

    Prove each release beats the baseline before it ships

    • Build eval datasets, Arabic and English LLM-as-judge rubrics and agent trajectory checks
    • Gate every release in CI with a threshold for each data slice
  6. SC / 06 · Agent Reliability

    Keep agent workflows correct when tools, models and APIs fail

    • Handle state, timeouts, rate limits, idempotency keys and prompt injection in tool results
    • Prove recovery with bounded retries, fallbacks, human escalation and failure injection
  7. SC / 07 · Deployment Safety

    Ship to the client tenant without risking their operations

    • Package with containers and IaC, and run CI/CD with managed secrets behind a model gateway
    • Release through shadow mode, a canary and an approval gate, with a rehearsed rollback
  8. SC / 08 · Observability

    Trace latency, cost and quality for every request

    • Instrument OpenTelemetry traces with token cost, quality signals and prompt and model versions
    • Set SLOs and alerts, and debug any failed run end to end from a single trace
  9. SC / 09 · Handover & Measurement

    Hand over a system the client’s team can operate and extend

    • Transfer code and infrastructure with runbooks and an on-call triage path
    • Train operators to lead an incident drill alone, and measure the outcome against the week-one baseline

Credential preview

FDE Gulf Certified

After all nine cards are reviewed and your capstone passes, you receive the FDE Gulf certificate and a public verification link.

Already deploying? Get assessed for free ↗

Talent Pool

After certification, we make the introduction.

After certification you can join the FDE Gulf Talent Pool. Companies in the UAE and KSA can use it to find engineers who already understand local constraints. We make the introduction.

See how hiring works →

Is this your field?

Twelve short client scenarios will help you decide where to start.

Take the FDE Fit Test

Plan your five weeks.

What you get

  • 25 project-based lessons
  • 5 live workshops
  • Practitioner review of 9 Skill Cards + capstone
  • A redacted case study you can show in interviews
  • FDE Gulf Certificate with a public verification link
  • Entry to the Talent Pool + priority introductions to hiring companies
  • 12 months of access to all materials

Pricing & payment

Early bird: 5,499 AED until

Regular price: 6,999 AED

Limited to 25 seats in the first cohort.

Training a team? 4 seats for 14,999 AED →

7-day refund window after the readiness check. Enrollment terms

Live workshop schedule

Times will be listed in Dubai (UTC+4) and Riyadh / Doha (UTC+3). The cohort starts January 4, 2027. Individual workshop times will be announced.

  1. Week 1Live workshop, Thu Jan 7: MCP server over a Gulf service API.
  2. Week 2Live workshop, Thu Jan 14: From VDI to the first call against a legacy API.
  3. Week 3Live workshop, Thu Jan 21: Arabic and English document pipeline to a cited answer.
  4. Week 4Live workshop, Thu Jan 28: Release decision with bilingual evals and a red team.
  5. Week 5Live workshop, Thu Feb 4: Incident drill and capstone review.

Reserve your seat

Early bird 5,499 AED until December 14. 25 seats in the first cohort.

Reserve your seat

Five practitioners. One field program.

Jakub

Jakub has 20+ years building and integrating systems. He focuses on context, tool use and human approval.

Marcin

Marcin has 15 years with SAP and complex workflows. He connects models to real client APIs.

Marcin

Marcin prototypes AI applications and tests them against the tasks people actually do. He has used low-code and no-code tools to try out product ideas before committing to a full build. His work on digital claims and payments informs how he chooses test cases and measures whether a prototype is worth deploying.

Leszek

Leszek has 25+ years in technology. He works on knowledge agents and retrieval that stays grounded.

Krzysztof

Krzysztof has 20+ years in delivery and operations. He owns use-case selection and secure deployment.

Tools for field work.

  • Vercel
  • OpenAI
  • Anthropic
  • Microsoft Copilot
  • Hugging Face
  • Docker
  • LangChain

Build a tool for one client workflow. Take the code, tests and runbook into your next deployment.

FAQ

Have another question? Ask the program team.

About the program

Who is this for?

Engineers who already ship code and want to do client-facing AI deployments in the Gulf.

Can I apply from outside the Gulf?

Yes. The projects focus on the UAE, Saudi Arabia, Qatar and Egypt. You can register your interest from another country.

What should I already know?

You should be comfortable writing code, calling APIs and debugging an application. Bring a project you can discuss without sharing confidential data.

Can I use my current engineering stack?

Yes. The reviews look at system behavior, the quality of your evidence and whether another engineer can operate your release. Document the stack you choose.

Where can I compare compensation?

The salary benchmark in the public Salary & Role Guide lists FDE Gulf estimates for Dubai, Doha, Abu Dhabi and Riyadh, with an independent UAE comparator. The guide also explains how to compare allowances and travel obligations. Read the salary benchmark →

Format and time

When does the first cohort start?

The first cohort starts January 4, 2027. Live workshop times will be shared before enrollment opens.

Which time zone will the schedule use?

The final schedule will show Dubai time (UTC+4) and Riyadh/Doha time (UTC+3). Dates and times will be published before paid enrollment.

What happens in a live workshop?

You bring that week’s artifact to a working session. Each lab includes a decision or failure to handle and a concrete acceptance check. The five workshops are listed in the agenda.

What should I bring to the first session?

Bring a workflow you can describe, one example input and a way to measure success. An anonymized client scenario or a project of your own both work.

Do I need access to client production systems?

No. Use an environment you control and data you have permission to use. A reproducible exercise with explicit limits is suitable for the review.

Skill Cards and certification

How do I earn the certificate?

Submit evidence for all nine Skill Cards and pass a practical capstone review. Attendance alone does not earn the credential.

Can I get a credential without joining the cohort?

Yes. Experienced engineers can take the free assessment with evidence from prior work. If all nine Skill Cards pass, you earn FDE Gulf Assessed. Get assessed for free →

What is the difference between the Certificate and “Assessed”?

The full Certificate includes live workshops, full Skill Card reviews and priority in the Talent Pool. Assessed is for people who already have the work and pass the free assessment.

Does the starter card count toward certification?

The starter card is a private self-assessment. The credential requires nine reviewed Skill Cards and a successful capstone review.

Can employers verify my credential?

Yes. Issued certificates have an individual ID and a public verification page that shows their current status.

Do I get job introductions?

Yes. Certified participants get priority introductions through the Talent Pool. See how hiring works →

What can I put in my interview portfolio?

Use your redacted brief, architecture decision, evaluation report, release drill and capstone. Obtain permission before sharing work that belongs to a client.

Pricing and enrollment

What does it cost?

Early bird: 5,499 AED until December 14, 2026. Regular price: 6,999 AED. Joining the waitlist is free, and so is the independent assessment.

How long do I have access to materials?

Paid cohort participants have 12 months of access to all materials from the cohort start date.

What if I’m not strong enough?

After purchase you get a short readiness check. If it’s clearly not a fit, you can get a refund within 7 days or move to a later cohort.

Can my company pay?

Yes. Use the invoice option. Request a company invoice →

Forge your first field card.

Pick one system you’ve built. Turn its strongest evidence, its weakest assumption and your next experiment into a card you can take to an interview.

FIELD CARD challenge.md
Read https://fdegulf.dev/challenge.md. Interview me about one deployment and help me create my first FDE field card. Use only details I choose to share. Keep the card local.

Paste into your coding assistant, or read the instructions and complete it yourself.

Become the FDE people trust with production AI.

Early bird 5,499 AED ends December 14.
25 seats in the first cohort.