Senior Software Engineer – Roku

#We Are Paramount  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

You’ll build and ship the Paramount+ Roku application used by millions of viewers. The Roku platform has constraints other platforms don’t: tight memory budgets, a single-threaded render loop, device hardware that ranges from flagship to five years old. You’ll solve problems inside those constraints.

We write software that’s simple to read, cheap to maintain, and built to last. You’ll own features from design through deployment, work across agile teams, and help other engineers get better at this work.

• Design, build, and maintain core Roku framework components and application features for Paramount+
• Architect around Roku’s constraints: memory limits, render-thread/task-thread boundaries, device performance tiers, and certification requirements
• Use RSG 1.3 data transfer APIs, BrightScript Memory Monitor, and Perfetto tracing to find and fix performance problems before users hit them
• Build real-time personalization and engagement features — personalized recommendations, dynamic artwork, ad engagement — within Roku’s memory and performance budgets
• Write clear documentation for components, architecture decisions, and platform-specific patterns
• Measure and improve application performance and stability through instrumentation and observability
• Work across agile teams and coordinate with backend engineering and Dev Ops/SRE on service builds and deploys
• Review code, pair with teammates, and raise the quality bar across the team
• Maintain and improve CI/CD pipelines and testing infrastructure
• Design and run A/B tests, then act on what the data says
• Use AI development tools to move faster and share what works with the team

• 6+ years writing software
• 3+ years building Roku applications
• BS in Computer Science, a related field, or equivalent work experience
• You know OOP, data structures, and algorithms well enough to design systems, not just pass interviews
• BrightScript and Scene Graph SDK, including RSG 1.3
• You can explain Roku’s memory model, the render-thread/task-thread split, device tiers, and what certification requires
• RESTful API design and data serialization
• Roku frameworks and services: RAF, RMF, Roku Pay
• Unit and integration testing on Roku
• HTTP protocol and caching behavior
• Git and Git Hub
• 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) to write and ship code faster

• BrighterScript and Roku community tooling (ropm, bslint, roku-debug)
• Other OTT platforms:
  Fire TV, Android TV, Apple TV, Samsung TV, LG webOS
• Observability tools:
  Conviva, New Relic, Datadog, Sentry
• Microservices and backend-for-frontend patterns
• You’ve worked with personalization or recommendation APIs on resource-constrained devices
• E2E testing for connected-device applications
• Docker and CI/CD tooling (Jenkins or similar)
• GraphQL
• You share AI tools and workflows that save the team time
• You care about UX enough to push back on Product and Design when something isn’t right
• You say “I don’t know” when you don’t know
• You’ve worked across time zones without waiting for meetings to unblock you

• You open a 200-file BrightScript repo you’ve never seen and start making changes the same day
• Other engineers read your code and understand it without a walkthrough
• You notice a memory spike on a Roku Express before QA files a ticket. You fix it and write up what happened
• You track Roku OS releases and adopt new APIs when they solve a real problem, not because they’re new
• You write architecture…