Lead Software Engineer - CTV
Burbank, CA, US, 91505 New York, NY, US, 10036
#WeAreParamount on a mission to unleash the power of content… you in?
We’ve got the brands, we’ve got the stars, we’ve got the power to achieve our mission to entertain the planet – now all we’re missing is… YOU! Becoming a part of Paramount means joining a team of passionate people who not only recognize the power of content but also enjoy a touch of fun and uniqueness. Together, we co-create moments that matter – both for our audiences and our employees – and aim to leave a positive mark on culture.
Location: On-site - New York / Los Angeles / San Francisco / Ft. Lauderdale
Responsibilities
-
Set technical direction for Paramount's Smart TV applications. Choose the patterns, own the architecture, make decisions the team can follow
-
Build and maintain application components using React and TypeScript. This is a hands-on role. You ship code
-
Lead a team of Smart TV engineers. Run code reviews, pair on hard problems, give feedback that raises the bar
-
Architect around CTV platform constraints: web runtime limitations, memory ceilings, rendering performance on low-end hardware, and platform certification requirements for Tizen, webOS, and other targets
-
Develop real-time personalization features for Smart TV applications. This includes creating personalized recommendations. dynamic artwork, and ad collaboration experiences built for CTV constraints
-
Collaborate with central video engineering teams to integrate and optimize video players across platforms
-
Work with external platform partners (Samsung, LG, and others) to develop, debug, and certify applications
-
Plan and prioritize technical work. Scope projects, surface risks before they block the team, keep releases on track
-
Write architecture docs, RFCs, and technical guides. Make decisions visible so the team doesn't have to guess
-
Improve CI/CD pipelines, testing infrastructure, and build tooling for multi-platform Smart TV deployments
-
Use AI development tools to advance faster. Show the team what works and help them adopt it
-
8+ years writing software
-
3+ years building Smart TV or CTV applications on web-based platforms (Tizen, webOS, or similar)
-
2+ years leading a team or serving as a technical lead
-
BS in Computer Science, a related field, or equivalent work experience
-
React and TypeScript at a level where you can design component architectures, not just use them
-
State management with Redux and RTK. You've made decisions about store shape, middleware, and selector performance that held up at scale
-
Client-side routing patterns (React Router or equivalent)
-
Front-end fundamentals: HTML, CSS, modern JavaScript. You can debug layout and rendering issues on a TV runtime without guessing
-
You've taken features from concept through delivery on CTV platforms, including certification and deployment
-
CI/CD environments with DevOps and SRE principles
-
RESTful API integration and data handling
-
Check how the profile performs. Make it better for devices that have limited resources. You know how to measure, not just improve
-
You write and speak about technical decisions in a way that helps people act on them
-
You use AI tools (Copilot, Claude, Cursor, or similar) and can point to specific ways they've changed how you work
-
Experience with multiple CTV platforms (Tizen, webOS, Vizio, Xbox, PlayStation, or others)
-
You've built or maintained cross-platform CTV codebases that share React code across Tizen, webOS, and other targets
-
Browser internals knowledge: rendering pipelines, compositing, layout thrashing, and how these behave on TV runtimes vs. desktop browsers
-
Video player integration experience (Shaka, hls.js, or native platform players)
-
You've rendered personalized or dynamically served content on memory-constrained CTV hardware
-
You've worked with real-time event pipelines or recommendation APIs on client applications
-
Observability tools: Conviva, New Relic, Datadog, Sentry, or similar
-
Experience working in Agile frameworks across distributed teams and time zones
-
Rapid proof-of-concept experience. You've built throwaway prototypes to answer hard questions fast
-
You've introduced AI tools to a team and helped them stick. Not a demo. Actual adoption
-
You care about UX enough to push back on Product and Design when something isn't right for the 10-foot experience
-
You say "I don't know" when you don't know
-
Your team ships on time because you scoped the work correctly, not because anyone worked weekends
-
Engineers on your team grow. They take on harder problems this quarter than last quarter. You can name what changed
-
You open a Smart TV app codebase you've never seen, connect a Tizen emulator, and start diagnosing a rendering issue the same afternoon
-
You know which React patterns cause jank on a 2020-era LG TV and which ones don't. You've written it down so the team knows too
-
When a certification submission fails, you read the rejection, fix the issue, and update the team's checklist so it doesn't happen again
-
You manage the relationship with platform partners. Samsung and LG engineers know your name and trust your team's submissions
-
You write architecture decisions down. Six months later, a new engineer reads one and understands why you chose what you chose
-
You push back when a plan has gaps. You suggest a better one. You do this without making people feel small
-
You treat the build pipeline, test coverage, and error monitoring like product features
-
You make the people around you better at their jobs. They'd say so if asked
Nearest Major Market: Los Angeles