G

Goldman Sachs

Advises on mergers and trades stocks and bonds

Senior Site Reliability Engineer

Site Reliability EngineeringUpdated on Nov 12
Full-timeSingaporeNo salary listedIn-person

About the Job

Requirements

  • At least 5 years in site reliability engineering, production operations, or reliability-focused engineering supporting high-availability, customer-facing, or trading/front-office systems.
  • Proven experience as an Incident Commander with measurable improvements in escalation timeliness, communications quality, and mean time to recovery.
  • Strong foundations in Linux, networking (DNS, HTTP, TLS, and routing), distributed systems, and public cloud platforms (AWS, Azure, or GCP).
  • Hands-on experience with observability stacks such as Prometheus, Grafana, OpenTelemetry, and ELK; incident tooling such as PagerDuty and Opsgenie; and collaboration platforms such as Slack and Teams.
  • Proficiency with infrastructure as code and automation tools such as Terraform, CloudFormation, and Ansible, and at least one modern programming language such as Go or Python.
  • Experience implementing service-level objectives, service-level indicators, error budgets, capacity planning, progressive delivery (feature flags, canary, or blue/green deployments), and chaos or game days.
  • Ability to translate complex technical contexts into concise updates for executives and business stakeholders.
  • Ability to work across time zones and own cross-region handoffs and follow-through.

Responsibilities

  • Act as Incident Commander for high-severity events, ensuring timely escalation, resolver engagement, and transparent communications to technical and business stakeholders.
  • Maintain status updates, incident timelines, and customer and leadership communications; improve communications templates and runbooks for clarity and speed.
  • Drive blameless, learning-first post-incident reviews and produce actionable remediation items with owners and due dates.
  • Own cross-region handoff procedures so emerging issues are surfaced globally with explicit ownership, clear next steps, and desk-readiness checklists.
  • Ensure shift notes, incident context, and risk hot spots are consistently captured, discoverable, and actioned.
  • Partner with Application Business Operations to identify incident and issue trends, quantify impact, and prioritize engineering fixes that remove manual workarounds.
  • Provide visibility into Application Business Operations workload and escalate when engineering prioritization is needed to reduce toil.
  • Automate repetitive tasks, codify remediations, implement self-healing mechanisms, and responsibly evaluate and adopt artificial intelligence for triage, runbook execution, and anomaly detection.
  • Track toil reduction and time saved, and feed the results into prioritization and capacity planning.
  • Collaborate with developers to improve instrumentation, service-level indicators, dashboards, and actionable alerts aligned with firmwide standards and globally consistent tooling.
  • Reduce alert noise and increase signal-to-noise ratio through improved thresholds, aggregation, deduplication, and suppression; validate alert-to-action mapping with runbooks and ownership.
  • Expand tracing, logging, and metrics coverage to accelerate detection, triage, and root cause isolation.
  • Define and steward service-level objectives and indicators across services; implement and manage error budgets with policies influencing release velocity and risk acceptance.
  • Facilitate data-driven tradeoffs between feature delivery and reliability, and regularly review error-budget burn with product and engineering teams.
  • Drive capacity engineering standards and partner with teams on forecasting, scaling strategies, and reporting on leading indicators, saturation, and headroom.
  • Work with developers to automate capacity tests, limit management, and scaling actions; ensure predictable behavior under load and graceful degradation.
  • Oversee change quality across environments and reduce change-related incidents through pre-deployment checks, progressive delivery, and canaries.
  • Serve as Operational Readiness Review gatekeepers, validating observability, runbooks, on-call readiness, rollback plans, and dependencies before go-live.
  • Review and improve documentation freshness, clarity, and completeness; identify and automate repeatable runbook steps.
  • Train developers on SRE fundamentals, including service-level objectives and indicators, error budgets, incident roles, on-call hygiene, and production-readiness best practices.
  • Establish, track, and publish SRE key performance indicators and objectives and key results, including detection, acknowledgement, and resolution times; incident frequency and severity distribution; change failure rate; error-budget burn; alert quality; toil reduction; and capacity headroom.
  • Produce regular executive-ready reports and partner dashboards, highlighting trends, risks, and the impact of reliability investments.

Desired Qualifications

  • Experience in front-office or trading environments, or similarly latency- and availability-sensitive environments, and close partnership with business operations or site operations teams.
  • Experience with Kubernetes-based microservices, service meshes, multi-region architectures, and global standards harmonization.
  • Experience building AI-assisted operations such as alert enrichment, anomaly detection, or runbook copilots with measurable toil reduction.
  • Experience operating status pages and handling customer-facing incident communications.
  • Experience implementing ITIL-aligned processes adapted to SRE practices, Operational Readiness Review frameworks, and governance.

About the Company

Goldman Sachs

Advises on mergers and trades stocks and bonds

Goldman Sachs advises companies and governments on mergers, raises money for them by selling their stocks and bonds, and trades securities for big investors such as hedge funds and pension funds. It led Ford Motor's 1956 stock market debut, then the largest share sale in US history. Traders buy and sell stocks, bonds, currencies, and commodities for clients and lend them money, while bankers earn a fee on each deal they advise on or arrange. Its asset and wealth management arm invests for institutions and wealthy families and charges fees based on the money it oversees. The firm was founded in 1869, when it began brokering short-term IOUs for New York merchants, and it is based in New York City.

Company size
10,001+
Company stage
IPO
Headquarters
New York City, New York
Founded
1869

Recently Posted Jobs

Explore more opportunities at Goldman Sachs

See more jobs