Release operations Engineer

HCL Technologies Limited; Singapore; On-site; SGD 70,000 - 110,000; Full time

Job summary

HCL Technologies Limited in Singapore is seeking a deployment-focused professional to be the first point of contact for web tier code releases. You will monitor the continuous push pipeline, triage breakages, and perform routine remediation.

Responsibilities include release schedule management, runbook maintenance, rollback readiness, and reporting. You will escalate infrastructure issues to L2/L3 with full context and help surface trends to improve stability.

Responsibilities

• Release monitoring: Continuously monitor pipeline health and acknowledge alerts within 15 minutes.
• Triage & classification: Investigate failures by logs, classify issues and compare with historical runs.
• Remediation: Execute standard runbook steps, retry failed steps and skip flaky tests.
• Release Schedule Management: Coordinate code freezes and maintenance windows, track upstream dependencies.
• Runbook Maintenance: Update runbooks as failure patterns evolve and document new steps.
• Rollback Readiness: Ensure rollback paths are clear before high-risk releases proceed.
• Reporting & Analysis: Produce handoff reports and on-call summaries; surface trends to L3.
• Escalation: Escalate infrastructure issues to L2 with full context and actions taken.

Job description

Role: First point of contact for web tier code releases. They monitor the continuous push pipeline, triage breakages, perform routine remediation, manage release scheduling, and elevate complex issues

Detailed requirement:

• Release Monitoring - Continuously monitor pipeline health via FlightDeck and Conveyor, track build progress and test signals, acknowledge alerts within 15 minutes, and keep pushctl updated.
• Triage & Classification - Investigate failures by reading logs and exceptions, classify as infrastructure/product/capacity/flaky, and compare against historical runs to identify patterns.
• Remediation - Execute standard remediation steps per runbook, including retrying failed steps and skipping documented flaky tests.
• Release Schedule Management - Stay aware of upstream dependencies (drain testing, HHVM builds, config pushes), coordinate around code freezes and maintenance windows, and flag release drift early.
• Runbook Maintenance - Keep runbooks current as failure patterns evolve, document new remediation steps, and flag gaps to L3.
• Rollback Readiness - Maintain awareness of rollback procedures and ensure rollback paths are clear before high-risk releases proceed.
• Reporting & Analysis - Produce structured shift handoff reports, prepare daily/weekly on-call summaries, and surface recurring trends to L3.
• Escalation - Escalate infrastructure-level issues to Tree Hugger (L2) with full context: timeline, logs reviewed, classification, and actions taken.