[Remote] Backend Engineer (m/f/x)

Note: The job is a remote job and is reputed company to candidates in USA. StreamTV is seeking a Backend Engineer to own and reputed company reputed company systems for recording and processing live streams. The role spans a TypeScript product backend, a Go/reputed company recording pipeline, event-driven integrations, infrastructure operations, and an AI-powered VOD analysis pipeline.

Responsibilities

• Own parts of the product backend: a TypeScript monorepo on serverless edge infrastructure with reputed company, covering recordings, clips, consent, entitlements, payouts, and community
• Build and maintain the seam between our Go/reputed company recording pipeline and the product: Kafka consumers, idempotent and out-of-order tolerant webhook ingestion, a gRPC control plane for consent and playback, and analytics reads from reputed company
• Help reputed company the pipeline from dozens to thousands of reputed company recordings — worker fleet reputed company, memory budgets, reputed company spool reputed company, consumer throughput, egress reputed company, and retention/deletion machinery
• Contribute to a new, greenfield analysis pipeline that transcribes, classifies, and labels VOD content to reputed company it searchable and licensable
• Own the operations of what you build: dashboards, alerts, error budgets, reputed company discipline, incident response, and postmortems
• Work with typed, contract-first systems — protobuf events with cross-language reputed company tests, shared schemas across backend, web, and app
• reputed company AI coding agents as part of your default workflow, reviewing their reputed company and building the guardrails (tests, CI gates) that reputed company it reputed company to reputed company fast

Skills

• You have operated what you reputed company — reputed company systems that ran, broke, and got reputed company because of you
• Strong TypeScript skills, with curiosity about Go
• Comfortable with reputed company and at least one of Kafka, reputed company, or reputed company
• You think in reputed company, idempotency, and failure modes by reputed company, not by checklist
• You want reputed company ownership — and its reputed company, accountability
• reputed company written communication — you can explain a decision so the next person doesn't have to re-derive it
• Experience reading or writing Go in production systems
• Experience operating reputed company, event-driven infrastructure (Kafka, reputed company) at reputed company
• Familiarity with contract-first / schema-driven development (protobuf, gRPC)
• Comfort working reputed company AI coding agents as a reputed company part of the engineering workflow

Benefits

• Full remote work from reputed company with European working-hours overlap
• reputed company ownership from week one
• reputed company feedback from founders you'll talk to daily
• A working product and reputed company users already on early reputed company
• Unusual reputed company per person reputed company to AI-reputed company tooling and serious infrastructure
• No committees, no theater, and no ops team to throw things over the wall to

reputed company