DEVOPS_SRE_ENGINEER

DevOps/SRE Engineer

Contract Type

Full time

Level

Senior

Work Model

Hybrid

Ensure reliability, performance, and observability of production systems. Build automation that prevents incidents before they happen for government and enterprise clients in the GCC.

ROLE_OVERVIEW

Role Overview

You'll define SLOs, build automated runbooks, conduct chaos experiments, and lead incident response for mission-critical systems.

Own the reliability and performance of production systems serving millions of users. You'll build automation, define SLOs, and lead incident response for government and enterprise platforms.

OWNERSHIP

What You Will Own

✓
Define and track SLOs/SLIs for production services. Establish error budgets and reliability targets.
✓
Build automated runbooks and self-healing systems that reduce manual intervention and MTTR
✓
Conduct chaos engineering experiments to validate system resilience under failure conditions
✓
Lead incident response, coordinate cross-team efforts, and facilitate blameless postmortems
✓
Optimize system performance, cost, and resource utilization across cloud and on-prem infrastructure
✓
Build and maintain CI/CD pipelines that enable safe, rapid deployments

REQUIREMENTS

What You Bring

✓
3+ years in DevOps, SRE, or platform engineering roles with production responsibility
✓
Strong scripting skills: Python, Bash, or Go for automation and tooling
✓
Experience with CI/CD pipelines: GitLab CI, GitHub Actions, Jenkins, or ArgoCD
✓
Proficiency with monitoring and alerting: Prometheus, Grafana, PagerDuty, or equivalent
✓
Understanding of cloud platforms: AWS, Azure, or GCP (compute, networking, storage)
✓
Experience with containerization: Docker, Kubernetes, or similar
✓
Ability to troubleshoot complex distributed systems under pressure

EVALUATION_PROCESS

Interview Process

+
Experience with infrastructure as code: Terraform, Pulumi, or CloudFormation
+
Knowledge of chaos engineering tools: Chaos Monkey, Litmus, or Gremlin
+
Experience with cost optimization and FinOps practices
+
Understanding of security best practices: secrets management, RBAC, network policies
+
Experience in regulated industries: finance, government, healthcare
+
Certifications: CKA, AWS Solutions Architect, Azure Administrator, or similar
+
Arabic language proficiency (written and spoken)

NICE_TO_HAVE

Bonus Points

1
Technical interview (90 min): Troubleshooting production incidents. Walk through your approach to diagnosing and resolving complex issues.
2
Practical exercise (2-3 hours): Write automation to solve a real reliability problem. Implement monitoring, alerting, or self-healing.
3
System design (60 min): Design a system for reliability and observability. Discuss trade-offs and failure modes.
4
Cultural fit (45 min): Discuss your approach to on-call, incidents, and blameless postmortems. How do you handle production pressure?
5
Final round: Meet the team and discuss day-to-day collaboration

WHY_NEURASAL

Why This Role?

This isn't about keeping the lights on. You'll build reliability into systems from the ground up, define what 'reliable' means, and have the autonomy to make it happen.

Real SRE Practices

We practice what Google preaches: SLOs, error budgets, toil reduction, and blameless postmortems. This isn't just ops with a new title.

Meaningful Impact

Work on systems that governments and enterprises depend on. Your reliability work directly impacts public services and business operations.

Automation First

We invest in automation and self-healing systems. Reduce toil, improve MTTR, and spend time on engineering instead of firefighting.

Learning Culture

Incidents are learning opportunities. We conduct thorough postmortems, share learnings, and make systemic improvements. No blame, just better systems.

Competitive Package

Market-rate salary (AED 18K-28K/month based on experience), performance bonuses, health insurance, and visa sponsorship.

Fair On-Call

Balanced on-call rotations (1 week every 4-6 weeks), on-call compensation, and focus on reducing after-hours pages through automation.

"I came from a big tech company where SRE meant firefighting. At Neurasal, we actually practice SRE principles: SLOs, error budgets, blameless postmortems. We build systems that don't need constant babysitting."

SRE Engineer

Neurasal, 18 months

Ready to apply?

Submit your context and let's discuss production trade-offs.