Forward Deployed Engineer Remote / Hybrid · →

Meramia Technologies; Dubai; Remote; AED 360,000 - 600,000; Full time

Job summary

Meramia Technologies in Dubai is seeking a senior software engineer to own deployments from architecture notes to production systems. You will collaborate with client teams, write production code in Python, TypeScript, and the stack they run, and ensure health checks and ownership on the client side.

You will embed with engineers, map workflows, and turn patterns into libraries or playbooks to avoid rewrites.

Qualifications

• Five or more years shipping full-stack applications and cloud services.
• Experience with LLM or foundation-model systems in production.
• Experience with microservices, APIs, containers and observability.
• Ability to turn a workflow into a software requirement and communicate with sponsors and engineers.
• Experience simplifying systems, naming deployment risks early, and trimming scope when needed.

Responsibilities

• Own a deployment from the architecture note to a production system with health checks and client ownership.
• Write and review production code across services the delivery needs — Python, TypeScript, Node, React.
• Embed with client engineers; map workflows; remove blockers before they become blockers.
• Turn patterns into libraries, playbooks, or internal SDKs for future estates.
• Bring eval numbers and operator notes back to training and productization teams.

Skills

Full-stack development

Cloud services

Python

TypeScript

Node

React

Observability

Clear communication

Tools

AWS

Azure

GCP

Kubernetes

Terraform

Job description

The seat is the one the rest of the site already describes: you sit inside the client team, on their platform, and you leave behind a system they can operate — not a slide.

• Own a deployment from the first architecture note to a production system with a health check and an owner on the client side.
• Write and review production code across the services the delivery actually needs — Python, TypeScript, the stack the client already runs.
• Embed with their engineers. Map the workflow. Remove the blocker before it becomes a status slide.
• Turn a pattern that worked into a library, a playbook, or an internal SDK so the next estate is not a rewrite.
• Bring eval numbers and operator notes back to the people who train and productise the models, so the next build is not a guess.

What you will do

• Own a deployment from the first architecture note to a production system with a health check and an owner on the client side.
• Write and review production code across the services the delivery actually needs — Python, TypeScript, the stack the client already runs.
• Embed with their engineers. Map the workflow. Remove the blocker before it becomes a status slide.
• Turn a pattern that worked into a library, a playbook, or an internal SDK so the next estate is not a rewrite.
• Bring eval numbers and operator notes back to the people who train and productise the models, so the next build is not a guess.

What you bring

• Five or more years shipping full-stack applications and cloud services — Python, TypeScript, Node, React, or the equivalent you will defend.
• LLM or foundation-model systems in production, and a clear view of how non-deterministic output changes the interface and the tests.
• Microservices, APIs, containers, and an observability path you have actually paged on.
• The ability to turn a workflow into a software requirement, and to say the same thing to a sponsor and to the engineer who will merge the PR.
• A record of simplifying a system, naming the deployment risk early, and cutting scope when the calendar and the quality bar cannot both move.

Useful, not required

• AWS, Azure or GCP; Kubernetes; Terraform — used on a live estate, not a tutorial.
• Eval harnesses, prompt pipelines, or retrieval systems on a workflow where a wrong answer costs money or trust.