Lead DevOps Engineer

What You’ll Do 

• Own end-to-end GitLab CI/CD pipeline design and operations—build, test, security scans, artifacting, environment promotion, and release automation—aligned to APL’s SDLC standards and environments (ATX/HOX for automation, DTQA, IVV, CERT, PROD). 

• Implement and evolve “safe deployment” practices (e.g., fully automated pipelines, blue/green or sharded deployments) to reduce risk and enable frequent, reliable releases. 

• Partner with Tech Ops/Networking to configure and secure runner connectivity (tags, protected runners, firewall rules) for deployments to AIX subnets and target hosts, ensuring compliant SSH key management and protected variables. 

• Build and maintain deployment automation and configuration management for AIX-hosted Dyalog APL services and related Linux/Windows components, with clear runbooks and rollback strategies. 

• Integrate quality gates into pipelines, including static analysis, unit/integration/E2E tests, and semantic release notes, in alignment with APL’s automation direction. 

• Improve observability and operational readiness (logging, metrics, tracing) and align with our modernization emphasis on enterprise observability as part of platform advancement. 

• Champion standards from APL Fundamentals (configuration in GitLab, continuous verification, environment strategy) and Architecture Principles (automation-first, CI/CD per module, testing in pipelines). 

• Troubleshoot and remediate pipeline, runner, and environment issues; drive root-cause analysis; and proactively harden delivery systems over time. 

• Mentor engineers and partner teams to adopt best practices in pipeline design, test automation, and release management across APL’s codebases and environments. 

What You Bring 

• 5+ years in DevOps or Platform Engineering with production-grade CI/CD for multi-repo environments (GitLab preferred), including runner orchestration, tags, protected branches/variables, and pipeline security controls. 

• Strong Linux/Unix administration; AIX experience or appetite to learn is a plus given APL’s runtime landscape. 

• Proficiency automating build/deploy operations with Bash/Python or PowerShell and infrastructure scripting (e.g., SSH, packaging, artifact management). 

• Practical experience integrating security and quality gates in pipelines (e.g., static analysis, linting, unit/integration testing, E2E), and releasing with semantic versioning and changelogs. 

• Familiarity with end-to-end test frameworks such as Playwright and integration frameworks such as Reqnroll and their execution within CI/CD. 

• Knowledge of environment promotion patterns (DTQA → IVV → CERT → PROD), release orchestration, and rollbacks in enterprise settings. 

• Excellent collaboration with Tech Ops/Networking and product engineering teams; strong documentation and runbook discipline. 

Nice to Have 

• Exposure to Dyalog APL and/or legacy modernization patterns (refactoring for testability, reliability, and performance). 

• Experience with blue/green or sharded deployment strategies at scale in regulated or mission-critical domains. 

• Observability tooling and practices for logs/metrics/traces. 

• Familiarity with wealth management and managed accounts workflows (models, rebalancing, post-trade ops). 

How We Work in APL (What to Expect) 

• CI/CD and quality are strategic levers: pipelines include linting, security scanning, multi-level testing, semantic releases, and automated environment promotion. 

• Configuration and client configurations are managed in GitLab, and teams aim for fully automated and “safe” deployments (blue/green or sharded). 

• Networking and runner strategy matter: we collaborate with Tech Ops to ensure GitLab runners can securely reach AIX subnets and target hosts with the right firewall and key configurations. 

• We are scaling “full-stack CI/CD” in APL Fundamentals, building shared capabilities for DevOps, performance, and resilience across APL teams.