Monitoring & Observability Engineer

Serve as the Singapore-based engineer that integrates local monitoring, telemetry, and observability assets into the Group ROC observability platform (ServiceNow ITOM, Cloud Observability, and Group-standard tooling). The role consolidates Singapore’s fragmented monitoring stack onto the Group standard, defines service telemetry, SLIs/SLOs, dashboards, and AIOps event rules for local critical services, and improves MTTD/MTTR for Singapore incidents. It acts as the local SME and liaison to the Group observability team, ensuring the Singapore estate is observed with correct service context and resilience visibility for local leadership, the ROC, and regulators.

PART 3: KEY ACCOUNTABILITIES & OUTCOMES

Main areas in which the role must achieve end-results to fulfil its purpose (maximum 8 key accountabilities).

Accountability

Supporting Activities

Outcomes / Deliverables

Major Challenges

Integrate Singapore monitoring and telemetry into the Group observability platform

• Onboard local infrastructure, network, application, and cloud telemetry into ServiceNow ITOM / Cloud Observability
• Apply Group-standard tooling, connectors, and data pipelines
• Singapore assets observed on the Group platform
• Correct service context and telemetry coverage
• Tool-fragmented landscape
• Inconsistent instrumentation

Consolidate and rationalize the fragmented Singapore monitoring stack

• Migrate infrastructure, network, application, and cloud monitoring onto the Group standard
• Retire or feed legacy tools as defined by the program
• Rationalized, standardized monitoring estate
• Reduced tool sprawl and licensing overlap
• Legacy-tool dependencies
• Change resistance from tool owners

Define service telemetry, SLAs/OLAs, and dashboards for local critical services

• Define SLIs, SLOs, SLAs/OLAs aligned to Group observability standards
• Build operational dashboards and resilience views
• Clear service-level telemetry for critical services
• Leadership-, ROC-, and regulator-facing dashboards
• Defining meaningful service-level objectives
• Data ownership across teams

Configure event correlation, suppression, and AIOps rules; tune alerting

• Configure correlation, de-duplication, and suppression for the Singapore estate
• Tune alerting to reduce noise and improve detection
• Lower alert noise and false positives
• Improved MTTD and MTTR for Singapore incidents
• Alert noise and over-alerting
• Maturing AIOps models

Embed instrumentation and observability-as-code in local delivery

• Partner with application, infrastructure, and cloud teams to embed instrumentation
• Promote telemetry standards and observability-as-code practices
• Consistent instrumentation across local delivery
• Repeatable observability-as-code adoption
• Competing delivery priorities
• Skills and culture uplift

Act as Singapore observability SME and liaison to the Group team

• Feed local requirements upstream to the Group observability team
• Translate Group platform capability into local outcomes
• Local requirements represented in the Group roadmap
• Effective local adoption of Group capability
• Aligning local needs with Group roadmap
• Remote coordination across time zones

PART 4: EDUCATION, EXPERIENCE, CERTIFICATIONS, SKILLS & COMPETENCIES

EDUCATION

• Degree in Computer Science, Information Technology, Engineering, or a related discipline from a reputable university
• Minimum 7 years of experience in monitoring / observability engineering across infrastructure, application, and cloud

EXPERIENCE

☐ < 3 yrs ☐ 3-5 yrs ☒ 6-10 yrs ☐ > 10 yrs

Monitoring & observability engineering (infrastructure, network, application, cloud)

☐ < 3 yrs ☐ 3-5 yrs ☒ 6-10 yrs ☐ > 10 yrs

ServiceNow ITOM Event Management / AIOps, event correlation and alert tuning

☐ < 3 yrs ☒ 3-5 yrs ☐ 6-10 yrs ☐ > 10 yrs

Observability-as-code, telemetry standards (OpenTelemetry), dashboarding and SLI/SLO design

CERTIFICATIONS / REGULATORY CERTIFICATIONS

• ServiceNow CIS — Event Management (preferred)
• Observability / monitoring tooling certification (e.g. Splunk, Solarwind, Dynatrace, Datadog, Grafana, Prometheus)
• ITIL v4 Foundation
• Cloud foundational certification (AWS / Azure)

JOB-SPECIFIC SKILLS & COMPETENCIES REQUIRED

• Strong observability engineering — metrics, logs, traces, and event management
• Event correlation, suppression, and AIOps configuration and tuning
• SLI / SLO / SLA design and operational dashboarding
• Instrumentation and observability-as-code (IaC, OpenTelemetry, pipelines)
• Stakeholder engagement across local teams and the Group observability function
• Awareness of MAS TRM and resilience-reporting expectations

PART 5: JUSTIFICATION FOR HEADCOUNT

The observability platform will be standardized and delivered by Group, but Singapore’s local monitoring landscape — tool-fragmented, infrastructure-centric, and inconsistently instrumented — cannot be migrated, rationalized, and operated without a dedicated local engineer.

Singapore’s critical services, vendor systems, and cloud workloads need to be on-boarded into the Group platform with correct service context, SLIs, and alerting; this is hands-on engineering work that cannot be executed remotely from Group.

Without this role, the Singapore estate will remain monitored through legacy silos, the ROC will lack visibility into Singapore services, and the bank will not realize the MTTD / MTTR and resilience uplift that justifies the program investment.