Design and implement platform capabilities: container orchestration, service mesh, observability, and developer tooling
Operate production platforms with 99.9%+ uptime SLAs for government and enterprise clients
Build self-service tooling and internal developer platforms that accelerate delivery
Participate in on-call rotation and lead incident response for platform issues
Mentor junior engineers and contribute to platform engineering best practices
Collaborate with security and compliance teams to meet regulatory requirements
5+ years operating production infrastructure at scale (10K+ containers, multi-cluster)
Deep Kubernetes experience: not just kubectl apply, but understanding of controllers, operators, and cluster internals
Proficiency in at least one language: Go (preferred), Python, or advanced Bash scripting
Experience with observability tools: Prometheus, Grafana, Jaeger, or equivalent
Strong understanding of networking (CNI, service mesh, ingress), security (RBAC, PSP, network policies), and distributed systems
Experience with CI/CD pipelines (GitLab CI, GitHub Actions, ArgoCD, Flux)
Ability to troubleshoot complex production issues under pressure
Experience in regulated industries: finance, government, healthcare (SAMA, NESA, PCI-DSS compliance)
Contributions to open-source infrastructure projects (Kubernetes, Prometheus, etc.)
Experience with service mesh: Istio, Linkerd, or Consul
Terraform/Pulumi expertise for infrastructure as code
Experience with multi-cloud or hybrid cloud architectures
Arabic language proficiency (written and spoken)
Certifications: CKA, CKAD, CKS, or cloud provider certifications
Technical interview (90 min): System design and troubleshooting scenarios. Design a platform for a real use case.
Practical exercise (2-3 hours): Debug a broken Kubernetes cluster with multiple issues. Fix them and explain your approach.
Architecture discussion (60 min): Present a platform you've built. Discuss trade-offs, failures, and lessons learned.
Cultural fit (45 min): Discuss past incidents, on-call experiences, and how you handle production pressure.
Final round: Meet the team and discuss day-to-day collaboration
"I've worked at startups and big tech. Neurasal is different. The systems we build actually matter. When we're on-call, it's because a government service or financial platform depends on us. That responsibility is what makes this work meaningful."
Submit your context and let's discuss production trade-offs.