Operations Engineer

Project Role : Operations Engineer

Project Role Description : Support the operations and/or manage delivery for production systems and services based on operational requirements and service agreement.

Must have skills : Oracle Database Administration (DBA)

Good to have skills : NA

Minimum 7.5 Year(s) Of Experience Is Required

Educational Qualification : 15 years full time education

Summary:

• The Scrum Master — Core Infrastructure serves as the agile delivery lead and servant-leader across the Compute & OS, Storage & Backup, Database & Middleware, and Cloud Platform engineering towers. The role is responsible for facilitating agile ceremonies, removing delivery impediments, co-ordinating cross-tower dependencies, and embedding a culture of continuous improvement across infrastructure engineering teams in a regulated financial services environment.
• Core infrastructure delivery has distinct characteristics that separate it from software development — change control windows, vendor hardware lead times, patching freeze periods, DR testing cycles, and regulatory maintenance obligations all shape sprint cadence and capacity. This role demands works within them effectively, and continuously drives the team toward greater delivery predictability and operational efficiency.
  
  

Roles & Responsibilities:

Agile Delivery & Sprint Management

– Facilitate sprint planning, daily stand-ups, sprint reviews, and retrospectives across all four infrastructure towers — ensuring ceremonies are purposeful, time-boxed, and produce actionable outcomes

– Own and maintain the infrastructure delivery backlog in collaboration with platform owners and technical leads — ensuring stories are well-defined, technically scoped, and sprint-ready with clear acceptance criteria

– Track and report sprint velocity, delivery metrics, and team capacity — producing transparent, accurate reporting for engineering management and programme governance forums – Manage cross-tower dependencies — Compute, Storage, Database, and Cloud workstreams frequently intersect on major programmes (server builds, DR tests, cloud migrations) the Scrum Master ensures these are visible, sequenced, and resolved before they impact sprint outcomes

– Drive backlog refinement sessions — translating infrastructure work items (server builds, patching cycles, storage migrations, DR rehearsals) into sprint-deliverable stories with measurable done criteria

– Facilitate continuous improvement through structured retrospectives — capturing actions, tracking follow-through, and promoting a culture of accountability across all towers

Impediment Removal & Stakeholder Management

– Proactively identify, escalate, and remove delivery blockers — spanning procurement, vendor lead times, change approval delays, resource constraints, and cross-team dependencies

– Serve as the primary delivery status contact for all four towers — communicating sprint progress, risks, and dependencies clearly to programme managers, infrastructure leadership, and senior stakeholders

– Co-ordinate with ITSM change management, CAB, and release management teams to align sprint deliverables with approved change windows, maintenance schedules, and freeze periods

– Manage vendor, OEM, and TAC engagement timelines where they create sprint dependencies — escalating when resolution SLAs are at risk and tracking through to closure

– Shield sprint commitments from unplanned scope injection — managing stakeholder expectations proactively when operational incidents, emergency changes, or business-critical requests compete with planned work

– Support major incident and problem management co-ordination as a delivery resource when infrastructure events impact sprint workstreams or require engineering team engagement

Infrastructure-Specific Delivery Practices

– Maintain awareness of infrastructure delivery constraints — hardware lead times, firmware and OS patching schedules, DR testing windows, licence renewals, and end-of-life milestones — and factor these into sprint planning and capacity management

– Co-ordinate multi-tower programme delivery — cloud migrations, data centre refreshes, DR rehearsals, and platform upgrades — ensuring sequencing is logical, dependencies are tracked, and no tower is blocked waiting on another

– Support audit, regulatory, and compliance delivery activities — ensuring infrastructure change evidence, configuration documentation, and operational records are produced, traceable, and audit-ready within sprint timelines

– Track and report on infrastructure-specific KPIs — patching compliance rates, change success rates, DR test outcomes, platform availability, and incident-driven sprint disruption — as inputs to programme governance and continuous improvement– Maintain accurate sprint boards, delivery dashboards, and programme-level reporting across Jira, ServiceNow, or equivalent ITSM tooling — integrated with change management workflows

– Drive operational efficiency and automation adoption across infrastructure teams — identifying toil reduction opportunities, supporting IaC and runbook automation initiatives, and tracking delivery benefit realisation

People, Capability & Continuous Improvement

– Champion the adoption of agile delivery standards, tooling, and best practices across all four infrastructure towers – Support onboarding of new team members into delivery norms, tooling, and sprint processes

– Identify and promote opportunities to improve cross-tower collaboration, reduce silos, and build shared delivery culture across Compute, Storage, Database, and Cloud teams

Professional & Technical Skills:

Must-Have Skills– Proven Scrum Master experience delivering infrastructure engineering programmes — server builds, storage migrations, database upgrades, DR rehearsals, or cloud platform delivery — not solely software development– Deep understanding of infrastructure delivery constraints — change freeze windows, CAB processes, vendor lead times, patching cycles, and their impact on sprint planning and velocity– Backlog management — Jira, ServiceNow, or Azure DevOps ability to translate infrastructure work into well-formed stories with technical acceptance criteria and realistic effort estimates

– Cross-tower dependency management — ability to map, track, and resolve sequencing dependencies across Compute, Storage, Database, and Cloud workstreams on concurrent programmes

– Stakeholder communication — clear, concise sprint reporting and risk escalation to infrastructure engineering leads, programme managers, and senior FSI leadership

– Working knowledge of core infrastructure domains — sufficient understanding of server, storage, database, and cloud platform operations to facilitate technical conversations, challenge estimates, and identify hidden dependencies

– ITSM integration — experience aligning agile delivery with ITIL-based change management, release management, and CAB governance in enterprise environments

– Metrics and reporting — velocity tracking, sprint burn-down, change success rates, patching compliance, and escalation-ready risk dashboards

– FSI delivery environment — comfortable operating in a heavily governed, audit-conscious environment with change control obligations, regulatory maintenance windows, and multiple stakeholder layers

– Continuous improvement — structured retrospective facilitation with measurable follow-through, particularly on sprint disruption caused by operational incidents and emergency changes

Preferred / Advantageous

– Experience supporting data centre refresh, cloud migration, or platform consolidation programmes across multiple infrastructure towers simultaneously

– Familiarity with IaC and automation delivery (Terraform, Ansible) — understanding how automation workstreams differ from operational change in sprint planning

– Prince2 Practitioner or equivalent project delivery certification — useful for hybrid agile/waterfall infrastructure programme delivery

Additional Information:

— with transparent reporting, minimal unplanned carry-over, and clear impediment resolution records

– Agile maturity grows across the infrastructure function — engineers write better stories, ceremonies produce real outcomes, and retrospective actions are followed through consistently rather than repeated sprint-on-sprint