Senior DevOps Engineer

Senior DevOps Engineer

Job Title Senior DevOps Engineer Job Description The Role Following extensive global expansion over several years and a drive to standardise common systems and platforms globally, PL Re is undertaking a major back-office transformation programme and has established a Divisional Data Team to develop and manage an enterprise-wide data solution, reporting services and to embed best practice data governance. We are looking to appoint a DevOps Senior to contribute towards the DevOps function within the Divisional Data Team (DDT). DevOps is the highest-risk pillar of the data engineering operating model, owning CI/CD, database change management, environment control, release management and platform access. The role holder will be the single point of accountability for how change moves safely from an engineer’s branch into production. The role reports to the AVP, Data Engineering, who is responsible for prioritizing, planning and driving forward the data engineering and transformation activities required. The role holder will build close working relationships with data engineering, testing, reporting, architecture and IT infrastructure teams across our operating geographies, and will be responsible for ensuring releases are controlled, auditable and repeatable.

Core Responsibilities

Azure DevOps platform ownership

• Own the Azure DevOps organisation and project configuration for the Divisional Data Team, including projects, teams, security groups, service connections, variable groups and secure files.
• Administer permissions and access models across repositories, pipelines, artefacts and libraries, ensuring segregation of duties between engineers, reviewers and approvers.
• Manage build agents (including self-hosted agent pools), agent capacity, scaling and patching.
• Use Azure Boards to plan, track and report DevOps work, and integrate work items with commits, pull requests and releases for traceability.
• Manage Azure Artifacts feeds, package versioning and retention policies.

Git branching strategy and standards

• Define, document and enforce the branching strategy across all repositories (for example trunk-based or GitFlow-style dev/SIT/UAT/production branches), including naming conventions and promotion paths.
• Set and maintain branch policies: required reviewers, minimum approvals, linked work items, build validation, comment resolution and merge strategy (squash, rebase or merge commit).
• Own the pull request process — review quality standards, approval routing, and clear rules on who may approve changes to which repository.
• Define the release branching, tagging and versioning model, and the process for hotfixes and emergency fixes.
• Own merge conflict resolution guidance, rebase and cherry-pick standards, and rollback procedures.

Git repository management

• Create, structure and maintain repositories; define repository standards, folder structures, README and documentation requirements.
• Manage repository security, path-based policies, protected branches, forks and cross-repository dependencies.
• Implement and maintain pre-commit and pre-merge quality gates, including linting, formatting and automated tests.
• Manage repository hygiene: history management, large file handling, retention, archiving and repository migration where required.
• Ensure no secrets or credentials are committed to source control, supported by scanning and remediation processes.

Deployment and CI/CD

• Design, build and maintain CI/CD pipelines (YAML-based) for Snowflake SQL, dbt models, Streamlit applications, stored procedures and supporting scripts.
• Own database change management (DCM), including the transition to and operation of a state-based deployment approach across development, SIT, UAT and production.
• Maintain consistent, reproducible environments and infrastructure-as-code, including configuration management across environments.
• Implement automated testing, deployment gates, approvals and post-deployment validation within pipelines.