Role: Site Reliability Engineering
JD:
What You Will Do**
As an SRE on the team, you will own the reliability and operational excellence of the platform end-to-end. You will define and track Service Level Objectives (SLOs) and Service Level Indicators (SLIs), and work closely with engineering and product teams to reduce toil and improve system resilience. You will design and implement observability solutions — covering logging, metrics, and distributed tracing — to give the team deep visibility into platform health.
You will lead incident response efforts, conduct thorough post-mortems, and drive systemic improvements to prevent recurrence. Beyond firefighting, you will contribute to the platform's infrastructure-as-code posture, automating provisioning, configuration, and deployment pipelines on cloud and on-premises environments. You will also participate in capacity planning exercises and performance tuning to ensure the platform scales with growing government demand.
Collaboration is central to this role. You will work alongside development teams to embed reliability thinking early in the software development lifecycle, reviewing architectures and advocating for operability best practices.
**What We Are Looking For**
You should have solid hands-on experience with Kubernetes and container orchestration, along with familiarity with CI/CD tooling such as GitLab, Jira, Confluence, Fortify, or similar tools in the DevSecOps space. Strong proficiency in at least one scripting or programming language — Python, Go, or Bash — is expected, as is experience with infrastructure-as-code tools like Terraform or Ansible.
You should be comfortable working with cloud platforms (AWS, Azure, or GCP) and have experience setting up and managing observability stacks such as the ELK stack, Prometheus, Grafana, or equivalent. A good understanding of networking, security hardening, and compliance requirements in a government or regulated environment will be a strong advantage.
Beyond technical skills, we value engineers who communicate clearly, take ownership, and approach problems with a systems-thinking mindset. Experience working in an agile team and a genuine interest in public sector technology are a plus.
**Good to Have**
Experience with GitOps workflows, service mesh technologies (e.g. Istio), or secrets management tools (e.g. HashiCorp Vault) would be advantageous. Prior exposure to government ICT standards or IM8 policies is welcomed but not required. AI-native mindset and software engineering skills are highly valued.
