Lead, Platform & Security Engineer at Shuttlers

Job Overview

Location
Lagos, Lagos
Job Type
Full Time
Date Posted
29 minutes ago

Additional Details

Job ID
162360
Job Views
24

Job Description






The role




  • You will head our new Platform Squad, reporting to the Head of Engineering. The squad is being separated out of today's Operations & Platform squad so that platform, reliability and security get dedicated ownership.

  • Your customers are our product squads. Your job is to give them a fast, safe, self-serve path to production and keep that path reliable and secure.

  • This is a player-coach role. You will set direction for platform and security while staying hands-on in code, infrastructure and incidents, working closely with our Senior SRE. With a small team, we value pragmatic choices: proven tools, simple designs, and custom builds only where they clearly pay off. We expect you to use AI tools heavily to move fast, with human review on anything touching production or security.



What you will do



Platform and developer enablement




  • Own the paved road. Build golden-path templates, standard Helm charts and self-serve environments so product squads ship without waiting on the platform team.

  • Shape our developer portal. Lead the design of a portal that becomes the front door to the platform, including AI-assisted self-service such as service scaffolding, environment requests and guided runbooks, all operating within clear guardrails.

  • Scale the runtime. Evolve our EKS, Istio and Envoy Gateway setup for growing real-time tracking and transaction volume.

  • Keep cost in check. Track infrastructure cost per trip and keep it efficient through right-sizing, autoscaling and sensible use of spot capacity.

  • Keep delivery fast and safe. Own the GitHub CI and ArgoCD pipeline from commit to production.



Reliability




  • Set SLOs that matter. Define per-service SLOs for core booking, payment and trip flows, with error budgets that guide release and roadmap decisions, and a path toward 99.99% on the most critical services.

  • Design for failure. Make sure core flows degrade gracefully when third parties fail (payment providers, maps, SMS) and when parts of our own platform are unavailable.

  • Raise observability quality. Mature our OpenTelemetry and SigNoz setup so alerts are tied to SLOs, signal is high and issues surface before customers notice. Extend coverage across the full stack, from EKS clusters, RDS and Valkey through the service mesh and edge to the third-party providers our core flows depend on.

  • Run incidents well. Own the incident response process, command major incidents, lead blameless post-incident reviews and make sure follow-up actions land.

  • Codify operational knowledge. Turn tribal knowledge into runbooks, including rollback and recovery procedures.



Security




  • Own the security posture. Take ownership of infrastructure and application security across AWS, Kubernetes and our edge.

  • Treat identity as the perimeter. Enforce least-privilege access and phishing-resistant MFA for production systems, and audit who can access rider location and payment data, including internal staff.

  • Build security into the SDLC. Represent security on the Engineering Architecture Review Committee and own security controls in CI, secrets management and dependency scanning.

  • Manage vulnerabilities and testing. Run vulnerability management and coordinate external penetration tests.

  • Detect threats early. Run threat detection and security monitoring using GuardDuty, Security Hub and WAF, with alerts routed into the incident process.

  • Own compliance for engineering. Maintain ISO 27001 controls for infrastructure and engineering, and ensure location and payment data are handled in line with the Nigeria Data Protection Act 2023.

  • Plan for growth. Build a phased security roadmap, including when and how to hire dedicated security specialists.



Leadership




  • Lead the Platform Squad. Set priorities, run the squad's backlog and represent platform and security in engineering leadership.

  • Stay hands-on. Write code, review infrastructure and Helm changes, and configure systems directly.

  • Grow the team. Partner with and develop our Senior SRE, and shape the hiring roadmap for platform and security.

  • Translate risk. Explain infrastructure and security trade-offs to leadership in clear business terms.

  • Our stack

  • We run on AWS with Kubernetes and GitOps at the core.

  • Area

  • What we run

  • Cloud

  • AWS, including EKS and RDS

  • Runtime and delivery

  • Kubernetes on EKS, ArgoCD (GitOps), GitHub CI, GHCR

  • Networking and edge

  • Istio service mesh, Envoy Gateway, AWS CloudFront and WAF, Cloudflare

  • Observability

  • OpenTelemetry, SigNoz

  • Data and caching

  • RDS, Valkey

  • Security and secrets

  • Infisical, GitHub CodeQL and Dependabot



Requirements



Must have




  • 7+ years in SRE, platform or cloud engineering, with at least 2 years leading a team or owning architecture.

  • Deep, hands-on experience running Kubernetes in production on AWS (EKS), including networking, autoscaling and ingress.

  • Proven experience designing or operating a multi-cluster Kubernetes platform, built to keep working when clusters or third-party dependencies fail.

  • Strong AWS knowledge across networking, IAM and native security services such as GuardDuty, Security Hub and WAF, including least-privilege access to sensitive data.

  • Demonstrable experience shaping and executing a multi-cloud strategy: deciding which workloads run on which provider, managing portability and lock-in, and operating production systems across more than one cloud.

  • Experience provisioning infrastructure across multiple regions for high availability, including failover and data replication, while keeping the added cost of redundancy under control.

  • A track record of measurable cloud cost reduction, with evidence such as lower monthly spend or unit cost achieved through right-sizing, autoscaling, spot or reserved capacity, and cost visibility for engineering teams.

  • Experience with GitOps and CI/CD, ideally ArgoCD and GitHub-based pipelines.

  • Strong working knowledge of infrastructure as code.

  • A track record of automating infrastructure provisioning, operational tasks and recurring toil.

  • Experience building developer experience tooling, such as internal developer portals, with evidence of significantly improving how developers work (for example, faster onboarding, shorter lead time or fewer support requests).

  • Experience building observability on OpenTelemetry and alerting on SLOs and error budgets.

  • Experience monitoring infrastructure end to end across clusters, databases, networking and the edge, with consistent metrics, logs and traces across regions and cloud providers.

  • Security breadth: secure SDLC, vulnerability management, working with external penetration testers, and ISO 27001 or a similar framework.

  • A pragmatic builder's record: delivering reliable platforms with a small team, preferring proven tools and simple designs over custom ones.

  • Clear communication of technical risk to non-technical leadership.



Nice to have




  • Experience with SigNoz or other ClickHouse-backed observability.

  • Experience with Istio or Envoy in production.

  • Experience building AI-assisted developer tooling.

  • Familiarity with the Nigeria Data Protection Act or GDPR.

  • Background in mobility, logistics, fintech or other real-time systems.



Your first 90 days




  • By day 30: you know the platform end to end and own incident response and the Platform Squad backlog. Infrastructure dashboards and alerts cover EKS clusters, databases and the edge, and SLO instrumentation is collecting baseline data for core rider and operations flows. You have shipped the first paved-road improvement and produced a triaged security baseline, including who can access rider location and payment data.

  • By day 60: SLOs are published for core rider and operations flows, with error-budget alerting tied to them. You have presented a phased security roadmap to leadership, runbooks cover rollback and recovery for core flows, and you have shared a platform roadmap that tracks cost per trip, alongside a working developer portal prototype that can scaffold a new service.

  • By day 90: at least one product squad uses the portal to create services and request environments, with measured gains in lead time or fewer platform support requests. Error budgets inform release decisions, phase one of the security roadmap is underway with an external pen test scheduled, and you have delivered a measurable improvement in cost or availability.



Similar Jobs

Full Time
Full Time
Full Time

Cookies

This website uses cookies to ensure you get the best experience on our website. Cookie Policy

Accept