T2 NOC Analyst

cubic; Hyderabad; On-site; INR 700,000 - 900,000; Full time

Benefits offered by this job

Shift allowance

Career progression

Job summary

Cubic Transportation Systems in Hyderabad is seeking a Tier 2 NOC Technician to monitor 35+ programs across local data centers and cloud tenants, perform incident remediation, and drive patching across Linux and Windows assets.

The role requires ITIL 4 practices, ISO/IEC 27001:2022 compliance, and PCI DSS v4.x alignment, with collaboration across regions to ensure service continuity.

Qualifications

• > Experience in NOC operations and incident remediation using runbooks.
• > Proficiency with ITIL 4 processes and escalation paths.
• > Familiarity with Linux/Windows environments and patch management.

Responsibilities

• Monitoring, event correlation, and incident remediation for multiple programs.
• Executing approved remediation runbooks and patching across environments.
• Coordinating with regional ops and cloud teams for timely resolutions.

Skills

Incident remediation

Troubleshooting

Stakeholder communication

Tools

Azure

AWS

Job description

Business Unit:

Cubic Transportation Systems

Company Details:

EXECUTIVE SUMMARY

Cubic Transportation Systems (CTS) is establishing a centralized, 24 hour by 7 day (24x7) global Network Operations Center (NOC) to monitor 35+ customer program implementations spanning regional field-service data centers and Microsoft Azure and Amazon Web Services (AWS) cloud tenants that support Payment Card Industry Data Security Standard (PCI DSS) v4.x scoped fare and payment processing. Tier 2 (T2) NOC Technicians sit between frontline Tier 1 (T1) monitoring and Tier 3 (T3) engineering, and perform two co-equal essential duties: validated-incident remediation using defined runbooks and playbooks (escalating to T3 only when no playbook exists or deeper technical guidance is required), and driving patching operations across each assigned program's environments.

Operations must comply with the International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) 27001:2022 standard, follow Information Technology Infrastructure Library (ITIL) 4 practices, support PCI DSS v4.x, and support National Institute of Standards and Technology (NIST) Cybersecurity Framework (CSF) 2.0 outcomes. This document describes the detailed roles and responsibilities of the T2 NOC Technician role and the standards basis for that operating model.

Job Details:

Scope and Operating Context

The NOC monitors 35+ global program implementations, each a distinct Cubic customer, managed day-to-day by regional field service operations in customer-site data centers and/or in Azure or AWS cloud tenants. Monitored elements include network, systems, services, and internal processes critical to operations, as well as an array of Operational Technology (OT) devices including fare gates, ticket vending machines, point-of-sale (POS) devices, and mobile applications. The NOC also ensures processes for backup, log management, and operational security remain fully operational.

Patching operations are a significant and growing share of T2 workload. Each program averages 5 or more environments, and each environment averages approximately 150 Linux and Windows assets, located in a physical customer-site data center and/or an Azure cloud tenant. Two T2 NOC engineers are dedicated to each program to support this effort, and it consumes the majority of their time. DevOps automation intended to make patch orchestration more efficient is in progress but not yet mature; until it matures, a significant amount of hands-on T2 time is required.

Compliance basis: ISO/IEC 27001:2022, PCI DSS v4.x, ITIL 4, and NIST CSF 2.0.

Tier Model and Escalation Path

Tier 1 (T1) staff perform 24x7 monitoring; once they have identified a validated issue, they elevate to Tier 2 (T2) staff for remediation. Operations issues route to NOC T2 staff; security issues route to Security Operations Center (SOC) T2 staff. If the issue has a known remediation path with a defined playbook, T2 staff resolve it directly. If there is no defined playbook, or deeper technical guidance is needed, T2 staff engage Tier 3 (T3) engineers.

Tier 1 (T1)

Function : 24x7 event triage, initial diagnosis, ticket creation, execution of approved runbooks, stakeholder communications.

Escalation Trigger: Escalates validated issues to Tier 2 (Ops to NOC, Security to SOC).

Tier 2 (T2)

Function : Deeper troubleshooting, incident remediation, patching operations, correlation across regions and programs, coordination with regional field service operations and cloud teams.

Escalation Trigger: Escalates to Tier 3 when no defined playbook exists or deeper technical guidance is required.

Tier 3 (T3)

Function : On-call product/platform engineering, complex database, storage, and network remediation, emergency design changes.

Engaged by Tier 2 on escalation; leads complex or novel remediation.

Escalation Trigger: NOC-to-SOC routing: operational anomalies that may be security-significant (spikes in authentication failures, unusual administrative actions, unexpected database audit patterns, web application firewall block surges, file integrity or tamper alerts) are escalated by the NOC to the SOC with enriched context, while the NOC continues operational containment under pre-approved playbooks.

Tier 2 NOC Technician: Roles and Responsibilities

Monitoring, Event Correlation, and Incident Remediation

• Perform deeper technical triage on incidents escalated from Tier 1, correlating events across regions, sites, and cloud tenants.
• Execute approved remediation runbooks and playbooks to restore service, consistent with ITIL 4 Incident Management practice.
• Engage Tier 3 engineers when no defined playbook exists or when the issue requires deeper technical guidance.
• Lead or support major incident coordination for assigned programs, including stakeholder communications and resolution validation.

Patching Operations (Co-Equal Essential Duty)

• Drive patch execution across the 5 or more environment