Meramia already sits with ministries, regulators and other estates that will not let a system onto the network until the boundary is written down. This seat embeds with those teams — civil, defence-adjacent, federal or emirate — and ships the same class of production AI the commercial FDE ships, inside that fence.
You will not invent a clearance you do not hold. You will be eligible for the vetting the client requires, and you will treat air gaps, sovereign regions and audit trails as engineering, not as theatre.
What you will do
- Lead a public-sector deployment from the architecture note to an observable system in the cloud the agency already trusts.
- Build the full stack the operator needs — Python, JavaScript, a modern web front — so model output becomes a decision they can act on.
- Integrate on government and sovereign estates: Azure Government, AWS GovCloud, a Kubernetes runtime the security office has already blessed, or the regional equivalent.
- Advise their engineering leads on model safety, retrieval, and how a system is scored before it is trusted.
- Turn the friction of a government rollout into a playbook or a platform request, so the next agency is not a cold start.
What you bring
- Five or more years shipping production code — Python, TypeScript or Go — across services and a modern front end.
- Eligibility for the client's security vetting. Many public estates in the region will not put you on the network without it.
- LLM or foundation-model systems, and a cloud stack (AWS, Azure, Kubernetes, Terraform) you have deployed into, not only described.
- Calm trade-offs when the operational clock is the constraint and the brief is still moving.
- The same explanation, in two registers: a technical officer and an agency lead, without a slide doing the work.
Useful, not required
- Air-gapped estates, a FedRAMP or equivalent control set, or a defence / intelligence operational setting you can discuss without inventing a programme name.
- Zero-trust, multi-tenant government clouds, or a data architecture built for classification boundaries.
What to send
- A CV and the two profile links the form asks for.
- One system you shipped into a governed or classified estate — the boundary, the eval, and what you refused to connect.
The first quarter
The first month is the vetting the client requires, a map of the public-sector estates we can already touch, and agreement on the first deliverable. The second is a secure, observable prototype in their cloud, with a baseline eval. The third is that prototype integrated as a production path with the security and operational checks written down.