SVP of Platform Operations

SVP of Platform Resilience & Intelligent Operations

Before the pager fires, an AI agent has already correlated the anomaly against three years of post-mortems, isolated the suspect deployment, and staged a rollback inside pre-approved guardrails. The engineer who joins the bridge isn't firefighting — they're reviewing the agent's work and deciding what to teach it next. That loop is the job. You'll own it.

We need a senior operational leader to take end-to-end accountability for platform resilience and intelligent automation across a large-scale enterprise SaaS product — one that underpins customer communities and social engagement for some of the world's most recognized brands. Reliability here isn't an internal SLA exercise; it's the revenue line.

How You'll Spend Your Time

• Run reliability like a P&L. Availability, recovery speed, and customer confidence are your weekly scorecard. You set targets, identify regressions in days rather than quarters, and close gaps with a bias toward automation over staffing.
• Engineer the autonomous operations layer. You architect, extend, and quality-gate the agent ecosystem — covering pre-triage, alert tuning, change-validation checkpoints, self-healing workflows, and automated post-incident reporting. Each agent ships with explicit scope, measured accuracy, failure-mode documentation, and a human override path.
• Lead from the terminal. A meaningful portion of every week is spent writing agent logic, reviewing incident data, and authoring root-cause analyses. During high-impact outages you take the bridge personally; the rest of the time your agents and your engineers handle execution.
• Be the executive customers trust. When a top-tier enterprise account needs a face behind operations, that's you. Equally, you're the architect ensuring those conversations become rarer over time by driving systemic improvements after every event.
• Curate an elite, compact team. You manage a small, senior, fully remote group distributed across time zones — no junior tiers, no ticket queues. Every engineer designs agents, owns runbooks, and carries full incident accountability. Hiring is deliberate and high-bar.
• Shape the playbook in real time. Decide where autonomous coverage expands next, where human judgment must remain, and what the agent surface looks like at the 6- and 12-month horizon. Publish what works and what doesn't — internally and, ideally, externally.
  
  

Requirements

• Founder-grade accountability. You internalize production health the way an owner internalizes cash flow. Customer outages cost you sleep — by choice, not by policy.
• 10+ years running SaaS or cloud-platform operations at non-trivial scale, with 3+ years as SVP, VP, or Head of Engineering over a senior-only organization.
• AI-native operator today, not tomorrow. You have already shipped or led autonomous incident-response, intelligent remediation, or agent-orchestrated operations systems in live production. Daily use of agentic coding tools (Claude Code, Cursor, or comparable) is expected.
• Battle-tested AWS depth. Multi-AZ, multi-account production estates with real war stories — not sandbox experiments.
• Technical hands still on the wheel. You have written or deployed production code within the past twelve months. You can evaluate an agent's decision tree, debug a failing runbook, and hold your own in an architecture review.
• Polished executive communicator. You brief the CEO and present to enterprise CxOs with equal confidence. Fluent or advanced English is required.
• Schedule & location. Overlap with US-morning hours (~13:00–17:00 UTC). OFAC-clear country of residence.
  
  

Nice to Have

• Visible thought leadership — talks, long-form posts, or open-source projects on autonomous operations, agentic SRE, or the "harness over headcount" philosophy.
• Experience in multi-tenant B2B SaaS — community platforms, social-engagement tools, observability, or customer-experience infrastructure.
• Operational fluency with Grafana, Prometheus, Loki, Datadog, PagerDuty, OpsGenie, or equivalent monitoring and incident-management stacks.
• A personal obsession pursued with unusual depth — a side project, niche research thread, or creative endeavor that reveals how you think when the problem is entirely self-chosen.
  
  

What You'll Gain

You'll build one of the earliest AI-native resilience functions operating at genuine enterprise scale — real contracts, real SLAs, real brand-name customers. There are no token caps, no tooling approval chains, and no pressure to grow headcount as a proxy for progress. The team that nails this model in the next year becomes the case study the rest of the industry references. You'll be the one writing it.

Environment

• Fully remote & async-first — work from anywhere with US-morning overlap.
• Enterprise stakes, startup tempo — weekly outcome loops, rapid decision-making, an evolving playbook.
• Senior-only roster — no L1/L2 layers; every contributor operates at the highest level.
• Uncapped AI investment — better models, more compute, new tooling — if it improves the agent surface, it gets funded.