Software Engineer

Senior Software Engineer - CTVYou'll build and ship Paramount's Smart TV applications across Samsung Tizen, LG webOS, and other CTV platforms. These apps run on web-based runtimes with tight memory budgets, limited CPU, and hardware that varies by model year and price point. You'll write React and TypeScript that performs within those constraints. You'll own features from concept through certification. You'll work with central video engineering, external platform partners, and Product/Design to deliver what millions of viewers see on the biggest screen in the house.ResponsibilitiesDesign, build, and maintain application components for Paramount's Smart TV apps using React and TypeScriptOptimize application performance on resource-constrained CTV devices. Profile rendering, measure memory, fix what's slowCollaborate with central video engineering teams to integrate and optimize video players across platformsWork with external platform partners (Samsung, LG, and others) to develop, debug, and certify applicationsManage application state with Redux and RTK. Keep the store clean and selectors fast as the app growsWrite clean, tested code and participate in code reviews. Hold your teammates to the same standardCoordinate with Product, Design, and Backend Engineering to turn requirements into working featuresWork across multiple agile teams and contribute to all phases of the development cycleImprove CI/CD pipelines and testing infrastructure for multi-platform Smart TV deploymentsDocument components, platform-specific patterns, and technical decisionsUse AI development tools to move faster and share what works with the teamRequired Qualifications5+ years writing software2+ years building Smart TV or CTV applications on web-based platforms (Tizen, webOS, or similar)BS in Computer Science, a related field, or equivalent work experienceReact and TypeScript. You build components, not just consume themState management with Redux and RTK. You understand store shape, middleware, and when selectors cause unnecessary re-rendersClient-side routing patterns (React Router or equivalent)Front-end fundamentals: HTML, CSS, modern JavaScript. You can debug layout and rendering issues on a TV runtimeYou've taken features from concept through delivery on CTV platforms, including certificationCI/CD environments with DevOps and SRE principlesRESTful API integration and data handlingYou communicate technical decisions in writing and in conversation. People act on what you say because it's clearYou use AI tools (Copilot, Claude, Cursor, or similar) to write and ship code fasterDesired QualificationsExperience with multiple CTV platforms (Tizen, webOS, Vizio, Xbox, PlayStation, or others)Performance optimization on TV devices: profiling, memory measurement, rendering analysis. You know how to find the bottleneck, not just guessBrowser internals knowledge: rendering pipelines, compositing, layout thrashing, and how these behave on TV runtimes vs. desktop browsersVideo player integration experience (Shaka, hls.js, or native platform players)Observability tools: Conviva, New Relic, Datadog, Sentry, or similarExperience working in Agile frameworks across distributed teams and time zonesRapid proof-of-concept experience. You've built throwaway prototypes to answer hard questions fastEnthusiasm for sharing AI tools and workflows that save the team timeYou care about UX on the 10-foot screen and you'll push back when something isn't rightYou say "I don't know" when you don't knowWhat Good Looks LikeYou open a Smart TV codebase you've never seen, connect a Tizen emulator, and start diagnosing a rendering issue the same afternoonOther engineers read your code and understand it without a walkthroughYou spot a memory leak on a 2020-era LG TV before QA files a ticket. You fix it and write up what happenedWhen a certification submission fails, you read the rejection, fix the issue, and flag what the team should check next timeYou own your features end to end. From scoping through deployment, you don't wait for someone to tell you what's nextYou know which React patterns cause jank on low-end CTV hardware. You avoid them and explain why to teammates who askYou push back when a plan has gaps. You suggest a better approachYou treat the build pipeline, test coverage, and error monitoring like product featuresYou help your teammates get better. Through code reviews, pairing, or writing things down so the next person doesn't hit the same wall