DevOps Engineer

Seniority level: Not Applicable | Employment type: Full-time | Industries: Financial Services

About The Role

We are hiring a DevOps Engineer for the IT Operations team in the Infrastructure department.

You own the day-to-day reliability of internal company infrastructure: GitLab, collaboration tooling (e.g. Slack), and Kubernetes-backed internal services. You design and ship automation, run the services, handle incidents, and migrate workloads onto Kubernetes.

Job Description

Operate and evolve GitLab, collaboration tooling, and Kubernetes-backed internal workloads: availability, upgrades, troubleshooting, backups, and change management.

Develop infrastructure code (IaC, CI/CD glue, tooling) so internal services are repeatable and less dependent on manual work.

Operate Kubernetes for internal workloads: deploy, scale, debug, participate in cluster upgrades.

Set up and maintain monitoring, alerting, and logging for services in your area; keep runbooks and operational docs current.

Serve on-call per the team schedule; respond to incidents from the runbook; eliminate causes, not only symptoms.

Migrate internal applications onto Kubernetes: document cutovers and rollbacks, reduce manual steps.

Keep shared delivery tooling dependable (e.g. GitLab) without owning org-wide CI/CD strategy.

Coordinate with Security on access, patching, and security controls; operate LDAP/SSO for internal tooling where IAM policy is accountable elsewhere.

Participate in code reviews; register technical debt; propose improvements to team tooling and automation.

Qualifications

Required

3+ years in DevOps / platform / internal infrastructure.

Kubernetes: deploy workloads, scale, troubleshoot, participate in cluster upgrades.

Experience operating internal or platform services: incidents, changes, work with internal customers.

Infrastructure as Code in production use: Ansible, Terraform, or comparable — you write and operate it, not only review it.

Linux (Ubuntu/Debian/CentOS family) and structured troubleshooting (logs, metrics).

Highly Preferred

Helm: create, change, and operate charts.

Prometheus and Grafana: metrics, alerts, dashboards.

Networking: DNS, TLS, ingress/LB — enough to debug service and cluster edge cases.

Python and Bash for automation.

Identity and access integrations: LDAP, SSO and related IdP/application integrations for internal tooling, aligned with Security.

Designing for availability (rollback, backup/restore).

Nice to have

GitLab administration (or equivalent developer platform) as a product you ran, not only consumed.

Security-aware operations: patching, secrets, least privilege — aligned with Security.