Full Job Description
We're hiring a senior Connected TV engineer to own production streaming apps used by millions of viewers on smart TVs and streaming devices, for a global media company. The apps are built in React + TypeScript and ship to Samsung Tizen, LG webOS, Vizio and Amazon Vega OS (next-gen Fire TV), across multiple brands. This is a hands-on architecture role. You'll shape how a multi-brand, multi-platform codebase is structured, built and shipped, in a monorepo with shared packages, and make it easy for both people and AI agents to work in. This team builds with AI agents every day. Most code is written through Claude Code and Cursor, under engineering discipline: agents plan, write and test, and you set direction, review and decide what ships. You should be comfortable with that workflow from day one, and able to make it better.
What you'll do
• Own the codebase architecture. Structure a monorepo (Turborepo or similar) of brand- and platform-specific apps on top of shared packages for logic, data, player and UI, with enforced import boundaries. Lead large refactors and repo changes without losing git history or breaking production.
• Design the data layer. Keep the UI independent of backend data models through an internal schema and adapters, so moving from REST to GraphQL touches only the adapters. Work with both Redux and React providers/hooks.
• Keep old TVs working. Many target devices run browser engines that are many years old. You'll own the shared Vite/Babel/TypeScript build config, legacy bundle output (ES5, polyfills), and automated checks that catch problems before they reach a TV.
• Own the TV experience. Work on D-pad focus and navigation, video playback (HLS/DASH, DRM, ad insertion, analytics) and startup performance, and verify on real hardware, not just a desktop browser.
• Scale CI/CD. Build and test only what a change affects, with build caching, templated infrastructure (Terraform, nginx, GitHub Actions) and per-app releases.
• Lead agentic development on the team. Maintain the agent context in the repo (CLAUDE.md / AGENTS.md, Cursor rules, skills, custom commands, hooks, MCP integrations with Jira/Confluence/GitHub), so agents work well in a large monorepo. Review AI-written changes as strictly as human-written ones, and help other engineers use these tools well.
• Work with native-platform engineers (Roku, Apple, Android), product, QA and backend teams in two-week sprints.
What you'll bring
• 5+ years of professional front-end engineering, including 2+ years shipping Connected TV / OTT apps on at least one of Tizen, webOS, Vizio, Fire TV / Vega OS, or similar.
• Strong TypeScript and React (class components and hooks), plus Redux and the Context/provider pattern.
• Deep understanding of legacy browser constraints: transpilation targets, polyfills, bundle size, and debugging on a device with limited dev tools.
• Hands-on build tooling experience: Vite (or webpack/Rollup), Babel, ESLint, Jest.
• Monorepo experience (Turborepo, Nx, or npm/pnpm workspaces), including package boundaries, shared configs and caching. Bonus if you've restructured or merged repos without losing history.
• Experience with HTML5 video: HLS/DASH, DRM (Widevine/PlayReady), client-side or server-side ad insertion, playback analytics.
• Strong Git skills, and comfort with Conventional Commits, squash-merge PRs and trunk-based development.
• Real, daily agentic coding experience with Claude Code, Cursor, or similar agents, beyond autocomplete. You know how to:
- give an agent the right context (project instruction files, rules, focused prompts) and keep it current
- plan before coding, break work into small verifiable steps, and keep diffs reviewable
- make tests, type checks, lint and builds the agent's guardrails, and require proof before accepting "done"
- spot plausible-but-wrong output, scope creep and invented APIs, and stay the accountable author of what you merge
- run parallel or long-running agent tasks (subagents, worktrees) without losing control of the codebase
- keep secrets and confidential data out of prompts and third-party tools
• Clear written communication. Much of the work is writing tickets, specs and decisions that people and agents can act on.
Nice to have
• React Native (0.7x) or WebView-hosted apps, especially Amazon Vega OS / Kepler
• GraphQL clients and codegen; federated graphs (Apollo Federation, WunderGraph Cosmo)
• Terraform, Docker, nginx and GitHub Actions
• Headless or legacy browser testing (Playwright, Puppeteer, Chrome DevTools Protocol)
• Feature flags and gradual rollouts
• Writing your own agent skills, MCP servers or hooks
Our process
1. Application and screening questions
2. HR call
3. Hiring Manager interview
4. Technical interview
5. Offer