Cloud & DevOps Engineer

Each client arrives with a different cloud, a different set of rules and occasionally a security questionnaire the length of a novella. You'd set up the infrastructure and delivery pipeline, then hand it over in a state their team can run without us.

In practice: AWS or Cloudflare most of the time, infrastructure as code always, and a strong preference for dull, well-documented choices over anything clever enough to be interesting at 3am.

You work across several engagements, so good patterns get reused instead of rebuilt from memory.

Expect agents to draft your Terraform, your pipelines and your runbooks. The interesting part is the review: what gets applied to a client's account, and who understands it when it pages them at night.

• Stand up new engagements. From nothing to a deployable environment on day one, without a week of yak shaving.
• Write infrastructure people can read. Terraform, Pulumi or similar that a client engineer can change without phoning us.
• Make it observable. Logs, metrics, traces, and alerts that fire for real problems only.
• Cover the security basics. Secrets, access, backups, and the answers their security review will demand.
• Keep costs visible. Clients see the bill, so they should also see what drives it.
• Write the runbooks. Then run the handover session that turns them from a document into knowledge.

• Four Years in Platform or SRE Work: with production responsibility, not just pipeline maintenance.
• Terraform Depth: modules, state, drift, and a plan output a reviewer can read without a decoder ring.
• Kubernetes or Serverless, Chosen on Merit: you know when a cluster is the answer and when it's a hobby.
• CI/CD Platforms: GitHub Actions or GitLab CI, with caching, matrix builds and a deploy that can roll back.
• Observability Stack: Prometheus, Grafana, OpenTelemetry or Sentry, wired so an alert means someone should move.
• Secrets and Access: least privilege, rotation and SSO, arranged so nobody keeps a production key in a chat thread.
• Networking Fundamentals: DNS, TLS, CDNs, and the load balancer that's definitely not the problem this time.
• Cloud Depth: one major cloud known properly, plus the humility that follows an outage you caused.
• Infrastructure as Code, For Real: used on something that mattered, not a tutorial repository.
• Pipeline Builder: CI/CD you designed rather than inherited, including the release strategy around it.
• Container Realist: comfortable with them, and comfortable telling a client they don't need any.
• Cost and Risk Translator: you explain a trade-off to a non-technical stakeholder and they make a better decision.
• Fluent English, Written and Spoken: most of our work happens in a written thread or on a call, and both have to be clear. Arabic is a genuine advantage across the region.
• AI With A Safety Net: agents draft infrastructure, you keep the blast radius small and the reviews real.

• Allergic to snowflakes: if it isn't in code, it didn't happen.
• Unflappable: incidents make you methodical instead of loud.
• Generous with knowledge: handover is the goal, not job security.

• Cloudflare Workers or other edge platforms.
• Compliance work: SOC 2, ISO 27001 or a regional regulator.
• Database operations, including restoring a backup for real rather than in theory.

• Remote across MENA. Work from wherever you are in the region, with hours built around your team's overlap rather than someone's attendance spreadsheet.
• Work that ships. Products go live in weeks, not quarters. When someone asks what you have been building, you can open it on your phone and show them.
• Small teams, no ticket queue. Four to eight people carry a product from the first client call to handover. Nobody hands you a spec and disappears.
• Kit and tools you choose. A budget for your setup, and for the editor, licenses and services that make you fast. No three-week procurement saga.
• A learning budget with time attached. Money for the course or the conference, plus room in the week to use it. The second half is the part most places skip.
• Client contact from day one. You sit in the room where the decisions get made. Plenty of engineers wait a decade for that seat.
• Time off people take, and no timesheets. We measure engagements, not humans in fifteen-minute increments. Book the holiday, go, come back.