Senior Backend Engineer
Kingston Stanley View all jobs
- United Arab Emirates
- Permanent
- Full-time
convenience • reliability
elegance • observability
assumptions ? ? What You?ll Do • Design and implement high-performance Go microservices • Build and operate distributed systems running on Kubernetes (GKE) • Design APIs that scale horizontally and degrade gracefully under load • Apply safe concurrency and parallelism patterns • Identify and eliminate bottlenecks using metrics, tracing, and profiling • Design data access patterns with explicit consistency and availability trade-offs • Build services that are observable, resilient, and production-ready • Operate within a GitOps-driven delivery model: o Git as the source of truth o PR-based changes, promotions, and rollbacks • Collaborate across platforms, frontend, mobile, QA, and compliance teams Technology Stack (Mandatory Experience) • Language: Go (production, high-performance systems) • Architecture: Microservices (mandatory) • Cloud: Google Cloud Platform (GCP) • Container Orchestration: Kubernetes (GKE) • Infrastructure as Code: Terraform • CI/CD & GitOps: GitHub Actions, PR-driven workflows • Observability: Datadog or equivalent (Prometheus, Grafana, Loki, distributed tracing) Mandatory Requirements (Non-Negotiable) Candidates must have hands-on experience with all of the following: • 5+ years backend engineering experience • Strong Go experience building production microservices • High-scale distributed systems (mandatory) • Microservice-driven architectures (mandatory) • Transactional, financial, or regulated systems • Event-driven or streaming architectures • Kubernetes (GKE) in production • GitOps workflows (Git as source of truth, PR-driven deployments) • Infrastructure as Code using Terraform Deep observability experience, including: • Metrics, logs, traces • SLOs, error budgets, alerting • Handling traffic spikes and asymmetric failure costs • Multi-region or multi-country deployments Strong understanding of: • Concurrency, race conditions, and resource control • API design and service boundaries • Performance vs scalability trade-offs • Failure handling (timeouts, retries, idempotency, back-pressure) • Experience operating services in production, including incidents and postmortems • Full service ownership – End to End This Role Is NOT For You If • You have only worked on monoliths or low-traffic systems • You optimise without observability or data • You treat CI/CD, infrastructure, or monitoring as “someone else?s job” • You have never handled real production incidents • You are uncomfortable owning systems after deployment What Success Looks Like • You design systems that scale predictably under real load • You proactively design for failure modes • You use observability and SLOs to guide engineering decisions • You reduce incident frequency and blast radius • You raise reliability and engineering maturity across teamsFOR MORE INFORMATIONCONTACT Omair Waziri