You're the second SRE. Sam joined in September and has been rebuilding our observability in Datadog and Cloudflare. You'll split the platform with him and help turn SRE into a real team.

SLOs that mean something. Define "reliable" per surface (API, websockets, jobs, renders), measure it, and hold us to it. We have the dashboards started. They need teeth.

Inference reliability. Provider failover, model fallbacks, queue priority for enterprise traffic, and degrading gracefully when a GPU vendor blips. The multi-provider router exists. Make it predictable under partial failure.

Kubernetes and infra. Probes, rollouts and rollbacks, graceful shutdown, autoscaling headroom, resource limits under bursty inference load. Everything is Pulumi. Keep it that way.

Queues and jobs. At-least-once is the reality. Idempotency, poison-pill containment and stalled-job recovery should be defaults, not patches.

Ship-safe pipeline. Canaries, feature-flag rollouts, lock-aware migrations. A bad deploy should be boring to roll back.

Incidents. Lead Sev1/Sev2 response, including status page and enterprise comms. Run blameless postmortems and make sure the same thing doesn't break twice.

Security and compliance infra. Work through our pentest findings (AWS account isolation, secrets management) and keep SOC 2 / ISO evidence from being a fire drill.

Cost. Reliability and COGS are the same lever here. Help us spend GPU money on purpose.

Learn the system and get onto on-call.

Own one pentest remediation end to end (likely secrets management).

Ship SLOs plus alerting for the top 3 customer-facing surfaces, with pages that are actually worth waking up for.

Site Reability Engineer (SRE)

Responsibilities

Qualification

Required

Preferred

Benefits

Company

Vizcom

More roles at Vizcom