[Talent Pool] Forward Support Engineer
Description
Summary
Keep business-critical consumer services always-on, and make each incident the last of its kind. This is a reliability engineering role deployed to the business — not a ticket queue. FSEs own service levels for the flows that carry revenue and customer trust: self-care apps, sales and distribution, martech journeys, and customer service.
What you will do
- Own SLIs, SLOs and error budgets for a set of business-critical journeys, agreed with the business owner in business terms.
- Act as incident commander during Sev-1/Sev-2: coordinate, communicate, restore — then drive blameless RCA to a permanent fix.
- Engineer resiliency in: graceful degradation, circuit breakers, retry and idempotency, fallback journeys, multi-zone posture.
- Build automated detection and remediation, including agentic runbooks that act before a human is paged.
- Run GameDays and chaos exercises; prove disaster recovery rather than assuming it.
- Gate releases on operational readiness, and plan capacity for campaign, payday and festive peaks.
- Hold vendors and partners to their SLAs with your own telemetry as the evidence.
Grade expectations
FSE1
Staff Support Engineer
SCOPE & DECISION RIGHTS : One service or journey. Can roll back, throttle or fail over within the runbook without waiting for approval.
ACCOUNTABLE FOR : Alert quality and noise, runbook accuracy, timely RCA with a fix that ships.
FSE2
Senior Staff Support Engineer
SCOPE & DECISION RIGHTS : A journey family. Incident commander for Sev-1. Can hold a release on error-budget grounds.
ACCOUNTABLE FOR : Availability and latency SLOs for the family. Repeat-incident elimination. On-call health of the rota.
FSE3
AVP, Service Resiliency
SCOPE & DECISION RIGHTS : The resiliency estate across consumer technology. Sets service tiering, error-budget policy, DR standards and the vendor SLA regime.
ACCOUNTABLE FOR : Enterprise service-level commitment to the business. Revenue and CSAT protected during peak. Resiliency spend and its return.
Reliability must-haves
- SRE practice at scale: SLOs, error budgets, toil reduction, blameless postmortems.
- Codes to automate — Python or Go — and reads the application code they support.
- Deep observability tooling and distributed-trace debugging across many services.
- Kubernetes, cloud networking, load and chaos testing, DR rehearsal.
- Calm, clear communication under pressure — to engineers and to executives at the same time.
Telecom domain must-haves
- Knows telco failure modes end-to-end: charging timeouts, provisioning stuck orders, gateway saturation, notification storms.
- Has run operations for a high-traffic consumer app or a national sales channel.
- Works fluently across the app-to-network boundary with NOC and network teams.
- Payment, wallet and OTT partner integration failure handling.
- Understands the commercial cost of a minute of downtime in prepaid.
Skills
Sign in to read and join the discussion.