Senior Roku & Fire TV Native CTV Engineer (BrightScript/SceneGraph)

Job Title: Senior Roku & Fire TV Native CTV Engineer (BrightScript/SceneGraph) Project Budget: $10,000 Hard-Cap (Phased Delivery) Post-Launch Support Term: Includes 90 days of dedicated post-launch bug-fix and stability support starting immediately after all milestones and store deployments are completed—all fully covered within the total fixed $10,000 project budget. Project Overview: We are looking for an experienced Senior CTV & Roku / Fire TV Native Engineer to build native streaming TV apps for Podvision TV, an emerging podcast entertainment network. The build features a Netflix-style VOD experience, a 50-channel real-time Live Guide/EPG, and multi-platform expansion (Apple TV and Google TV) alongside mobile and web development. CRITICAL WARNING TO APPLICANTS Do not apply if you are a general web or mobile developer with zero personally published CTV native living-room apps. This project requires hands-on production experience building and shipping apps to the Roku Channel Store and Amazon Fire TV. Budget Agreement Requirement: By applying, you explicitly confirm your agreement to work within the $10,000 hard-cap phased total budget outlined in this project scope. Proposals requesting higher rates or ignoring the fixed budget will not be considered. CRITICAL REQUIREMENT: 100% CODE OWNERSHIP & HYBRID EFFICIENCY We require full, proprietary source code ownership delivered directly into our private GitHub repository. We will NOT accept locked-down proprietary SaaS white-label wrappers, monthly platform rental prisons, or black-box app builders. Design & Asset Workflow: MANDATORY GITHUB REPOSITORY & CI/CD WORKFLOW: The developer must work directly inside the Client’s provided private GitHub repository from Day 1 for the entire duration of the project. No local-only development, external repositories, or end-of-milestone "code dumps" are permitted. Developers are expected to push code updates to the official repository on a daily basis, and code must pass automated GitHub Actions CI/CD deployment pipelines for linting, testing, and staging deployments on Vercel without breaking builds. The developer will receive graphic assets from the client and is responsible for translating provided web/mobile design assets into platform-compliant 10-foot TV navigation layouts using standard native UI components (including high-contrast D-pad focus states). You can immediately begin building the core structural shell, API connections, and playback logic. Scope & Adaptive Framework Policy: This agreement defines a lean, hybrid development build across all specified platforms. Both parties acknowledge that multi-platform software engineering inherently requires minor iterative adjustments, configuration refinements, and technical tweaks during development. Routine adjustments required to fulfill the core intent of these deliverables are considered part of the agreed-upon project scope and will not be subject to additional change-order fees. Note on Technology: We are using a lean, hybrid Headless Video API model. Developers are expected to leverage standard platform SDKs, native player frameworks, open-source UI component templates, and direct API integrations—such as Next.js, Supabase Server Backend Database, Bunny.net CDN Edge Storage, Google Ad Manager, and VideoElephant—rather than wasting time and budget custom-coding standard elements from zero. You are building clean, custom-wired clients that consume our centralized headless API. Project Scope & Milestone Architecture: $10,000 Phased Total Budget Cap — Spanning a 16-week execution timeline across three core phases: Phase 1: Core Web & Primary Living Room CTV Milestone 1: Backend Architecture, Bunny.net CDN, Supabase Server Backend Database & API Ingest Integration, VideoElephant Syndication Engine, Web Portal (Hosted on Vercel), Core Ad/CC Engine, Social SSO, Guest Access & Device-Pairing Auth Timeline: Weeks 1 to 4 | Payment Upon Approval: 15% ($1,500) Development Workflow & Version Control: Developers must work exclusively out of the Client-owned GitHub repository from Day 1, pushing daily code commits and incremental feature updates to ensure complete transparency, auditability, and daily progress tracking. Milestone Warranty, Bug Fixes, CTV Compatibility & Data Population: Zero-Defect Acceptance Period: The developer is responsible for resolving any bugs, layout breaks, API mismatches, or ingestion failures identified during testing at no additional cost. CTV API Compatibility & Downstream Readiness: Although dedicated CTV apps (Roku, Fire TV, Apple TV, Google TV) are built in subsequent milestones, all JSON API endpoints, metadata schemas, and HLS streaming manifests delivered in Milestone 1 must be fully verified and compatible with living-room streaming requirements. The developer warrants that the backend architecture built in Milestone 1 will require zero structural API modifications or database redesigns to feed future CTV apps, specifically including standard deep-linking content IDs, media type classifications, and playhead bookmark synchronization required by Roku and Fire TV frameworks. End-to-End Seed Execution: Milestone delivery is contingent upon the successful, verified end-to-end ingestion, automated categorization, and playback of initial seed content (including .mp4 and .srt sidecars) across the web portal. IP & Asset Ownership: All source code, repository commits, database schemas, and configuration credentials remain 100% the exclusive property of the Client from Day 1. Deliverables, Acceptance Criteria & Testing Protocols: Core Web Portal & Infrastructure - (The Master Pipeline Foundation): Podvision web portal styled, responsive, and tested across modern browsers; deployed to a secure private Staging/Beta URL on Vercel for client review and testing prior to official domain mapping to Podvision.tv. Headless API-First Architecture & Native Data-Contract Prep - The web portal must act as the primary, centralized Source of Truth and data pipeline for the entire ecosystem. Every single feature—including VOD content categorization, EPG schedules, creator metadata, ad-tag routing, and user state management—must be powered by clean, documented JSON APIs originating from Supabase and Bunny.net. Scalability & Performance Infrastructure - Implementation of adaptive bitrate (ABR) streaming configurations via Bunny Stream; strict database connection pooling and mandatory column/foreign-key indexing in Supabase for sub-50ms query speeds; aggressive Vercel Edge Caching and Incremental Static Regeneration (ISR) to offload repeated API read traffic; WebSocket/real-time feed throttling and debouncing; API rate-limiting and bot mitigation; and proactive setup of spend caps, alerts, and performance observability (Sentry/Vercel Analytics) on Vercel and Supabase. Proactive Infrastructure Monitoring & Alerts - Setup of real-time monitoring and automated alerts on Supabase and Vercel. Developer must configure email/system notifications to trigger if database CPU utilization exceeds 75%, active connections approach plan thresholds, or error rates spike, ensuring proactive scaling before high-volume traffic hits Marketing Data Pipeline & Content Monetization Hooks - Implementation of foundational hooks for ad traffic integration and partner tracking. Developer must install and configure the Next.js script component for the Meta Pixel alongside server-side event tracking hooks (page views, content plays). Additionally, the developer must structure the Supabase database schema with creator/partner content attribution fields and basic view-counting event logs, ensuring the platform is fully equipped for social campaign deployment and content-partner monetization tracking without breaking performance or speed scores. Crucial Architecture Requirement (50-Channel Live EPG & UI Scaling) - To guarantee smooth implementation during downstream mobile (iOS, Android) and living-room CTV phases (Roku, Fire TV, Apple TV, Google TV), all API response payloads delivered in Milestone 1 must natively support lightweight data structures, predictable pagination keys, and explicit time-grid formatting. This includes supporting a fully functional 50-channel live EPG grid with virtualized rendering rows and 3-row stacked horizontal discovery carousels without bloated payloads or UI lag. Supabase Server Backend Database & API Ingest - must be instantiated directly within Client-owned accounts from Day 1. Bunny.net token security must be verified against hotlinking; seed content loaded with captions and TV Content Ratings metadata; live chat & moderation fully tested. Authentication, Guest Access & Device-Pairing Architecture: Guest-First Instant Access: Architectural support allowing users to watch free AVOD content immediately and interact with the live EPG guide without a forced login wall, backed by temporary anonymous session handling in Supabase. Unified Web Social SSO: Custom database/password sign-in alongside friction-free 1-click Social Sign-On (Google, Facebook, and Apple OAuth mapped to a single unified user profile table). TV App QR Code & Device Pairing Logic: Backend token-handshake infrastructure fully wired for future mobile-to-TV and browser-to-TV QR code login handshakes. Centralized user session tables in Supabase tracking real-time playhead resume sync, watchlist states, and automatic background OAuth token renewal. Podvision TV Cross-Platform Data Flow & Frictionless Ingestion Pipeline Model (Bunny Stream Powered): Zero-Drop Architecture & Automated Asset Parsing: Backend must instantly process all incoming content—whether pulled automatically via background MRSS/JSON video feed parsers or manually uploaded as finished production-ready master export files (.mp4 or high-res .mov). Ingestion pipeline must automatically parse embedded metadata, category tags, and accompanying poster/thumbnail artwork without requiring manual intervention. Content State Verification: All incoming files are completely finished, final export files requiring zero post-production or editing on our end. End-to-End Architectural Data Flow: Bunny Stream acts as the central engine/hub to ingest finished master files, route them through adaptive transcoding and secure edge storage, and update the central database. All-platform viewers continuously read structured API feeds pointing to Bunny's optimized output. Automated Cron Workers & Ingestion Resilience: Implements automated server-side background cron workers/functions via Supabase to poll creator RSS/MRSS feeds automatically every 15 minutes. VideoElephant Syndication Ingestion Engine: Implementation of a dedicated, robust background ingestion and mapping module specifically built for the VideoElephant B2B syndication API to parse metadata schemas and route pre-packaged content directly into the system, inclusive of initial error states and standard API schema mapping. Automatic VOD Tagging & Manual Live EPG Separation Architecture: Automatic VOD Cataloging: Every ingested asset (whether via automated MRSS feed, VideoElephant syndication, or manual upload) must automatically parse its metadata tags (Parent Category and Subcategory) and instantly populate the corresponding Netflix-style 3-row stacked VOD carousels across the web and future CTV frontends. Strict Linear vs. On-Demand Separation: Ingestion into the master VOD library must not automatically push or dump content into the live linear channels, preventing accidental scheduling clutter. Admin Control Room EPG Scheduler: A fully functional administrative scheduling interface enabling platform operators to intuitively curate, drag-and-drop, or queue specific VOD assets into time-blocked slots across the 50-channel live EPG grid, while leaving non-scheduled assets safely within the on-demand library. Fallback automated UI placeholders must display cleanly if custom channel branding assets are absent. Creator Submission Portal & Multi-Tenant Dashboard: Front-end Creator Submission Portal page featuring an Automated Audio/Video RSS-to-JSON Ingestion Parser allowing podcasters to paste standard podcast RSS feed links. Multi-tenant Creator/Partner Dashboard architecture with strict Role-Based Access Control (RBAC) and a One-Click Social Share & Embed Generator. Verified Revenue Attribution & Financial Reconciliation Pipeline: Integration of a persistent Content ID indexing protocol. Every video asset carries a unique, immutable Content ID that propagates through player VAST/VMAP metadata tags and serves as the exclusive key for nightly Ad-Server API data reconciliation (e.g., Google Ad Manager), calculating impressions, eCPM, gross revenue, and exact net 50/50 revenue-split totals in U.S. dollars ($). Automated Partner Statements & Compliance: Self-service [ Download Statement ] export feature (PDF/CSV) for historical earnings and payout summaries. Day-1 Partner Compliance & Payout Architecture: Partner registration workflow natively collecting verified legal identity and tax documentation (W-9/Tax ID data) alongside bank payout destinations via integrated Stripe Connect Express/Embedded schemas, ensuring compliance for all financial ledgers and future 1099 reporting. Ad Monetization, Closed Captioning, & Player Mechanics: Full web-based HTML5 video player monetization and caption pipeline integrated and functional on Podvision.tv, including standard VAST/VMAP ad tag integration frameworks with strict 3-second timeouts, ad-blocker failovers, and house-ad/promo video failover logic. Standard .srt/.webvtt sidecar closed-captioning multi-language player toggles, native video player chapters, and graceful error-handling states featuring automated reconnection loops and a [ Refresh Stream ] recovery button. Interactive Features & UI Layouts: Implementation of dynamic network architecture including top-hero live video auto-play, sticky corner Picture-in-Picture (PiP) mini-player docking, native casting integrations, and an Interactive Companion Mode framework. Admin & Syndicator Management Dashboards: Zero-Code Operational Dashboards: Functional, non-technical Admin Dashboard (utilizing a custom-wired Supabase interface or low-code tool like Retool) empowering operators to independently manage VOD categories, map third-party syndication feeds, upload brand assets, and update EPG metadata via intuitive graphical interfaces without code modification. Universal Syndicator Management Dashboard allowing administrators to add, remove, and map multiple third-party content feeds independently. Security, Compliance, & Resilience: Backend API rate-limiting and bot-mitigation rules (via Cloudflare or AWS WAF). Multi-region Bunny.net edge-rule redundancy/failover profiles for high-traffic live streaming. Privacy Policy & Compliance Architecture, UGC Moderation & Reporting tools. Phase 2: Mobile Expansion & Network Analytics Milestone 2: Primary Living Room CTV (Roku & Amazon Fire TV Native Builds with Native Ad/CC Integration & QR Code Pairing) Timeline: Weeks 5 to 8 (4 Weeks) | Payment Upon Approval: 25% ($2,500) Deliverables & Testing: Podvision core CTV layout built natively using official platform SDKs for Roku (BrightScript / SceneGraph with native RAF SDK) and Amazon Fire TV (Fire OS / Android architecture), featuring high-contrast D-pad focus states and skeleton image loaders. 10-foot TV consumption experience optimized so all remote button actions execute within 250 milliseconds. Native TV login screen featuring instant QR Code TV Activation pairing. Both Roku and Fire TV apps natively consume the Milestone 1 web portal feed to accurately render the Live Guide (EPG), Netflix-style dynamic category carousels, 3-row subcategory hub templates, and podcaster tiles in real time. Native CTV player logic integrates the Milestone 1 Ad Server and Subtitle pipeline with 3-second timeouts, ad-blocker failovers, and multi-language subtitle support. Asynchronous ad-loading patterns ensuring ad-fetching and ad-pod transitions occur in the background without locking UI navigation. Full UI state preservation, accordion memory, back-navigation behavior, automated background token re-authentication protocols, and native crash reporting SDK integrations. Integration of a custom motion-graphic startup intro video (HBO-style logo reveal) for app launch. Milestone 3: Native iOS & Android Mobile Apps & Partner Analytics Dashboard Deployment Timeline: Weeks 9 to 11 (3 Weeks) | Payment Upon Approval: 20% ($2,000) Deliverables & Testing: Native Mobile Apps (iOS & Android) built natively using official platform SDKs, featuring high-contrast touch navigation, 1-click Social Sign-On, Picture-in-Picture (PiP) support, guest browsing support, and full consumption of the established core API feed. Full functionality testing executed for split-screen layouts, lower-third banners, subtitles, push notifications, TV activation code pairing, cross-device state handshakes, Continue Watching sync, and ABR streaming. Automated re-validation protocols for user freemium/subscription entitlement flags against App Store and Google Play billing servers. Deployment of the Admin/Partner performance dashboard to display real-time impression and revenue reporting. Phase 3: Secondary CTV Expansion, Private Beta & Store Publishing Milestone 4: Secondary Living Room Expansion (Apple TV & Google TV) Timeline: Weeks 12 to 14 (3 Weeks) | Payment Upon Approval: 20% ($2,000) Deliverables & Testing: Native application development and deployment across two distinct living room operating systems: Apple TV (tvOS): Built natively using Swift/SwiftUI, complying strictly with Apple TV HIG specifications and Siri Remote touch navigation. Google TV / Android TV: Built natively using the Android Leanback SDK and standard Android TV UI patterns. Complete Feature & Content Parity: Every single feature built into the website, Roku, Fire TV, and mobile apps must be fully functional here. Ad modules execute fully asynchronously with mandatory 3-second timeouts and house-ad/promo fallback protocols. Milestone 5: Private Beta Testing, Store Publishing & Complete Code Handoff Timeline: Weeks 15 to 16 (2 Weeks) | Payment Upon Approval: 20% ($2,000) (Bringing total to 100%) Deliverables & Testing: End-to-End Beta Testing: Execution of a structured private beta phase across all platforms (TestFlight, Roku Private Channel, Amazon Appstore Internal Testing, Google Play Internal Testing). App Store Publishing, Rejection Resolution & Compliance: Complete end-to-end management and successful submission of apps across all 6 target app stores, including build uploads, metadata entry, and resolving rejection notices. Disaster-Proof Handoff, Plain-English CMS Training & Documentation: Transfer of 100% proprietary ownership of all source code, design files, and administrative control to the Client via GitHub, verified automated CI/CD pipelines, and delivery of a plain-English Network Operations & CMS Handoff Guide plus a live/recorded video walkthrough session. Final Network-Wide Verification: Final QA sign-off confirming seamless, real-time synchronization across the website, mobile apps, and all four CTV living room platforms. Contract Terms, Maintenance & Safeguards Milestone Compensation Rule: Funds for each milestone remain held in Upwork Escrow and will ONLY be released upon successful code verification, live deployment testing, and full adherence to milestone deliverables. 90-Day Project Term & Post-Launch Support: The initial development, deployment, and configuration is scoped for a 90-day timeline, accompanied by a mandatory 90-day post-launch support and bug-fix period following final milestone approval at zero additional cost. Code Ownership & Intellectual Property: All source code, assets, repository access, API keys, configurations, and intellectual property created under this contract are 100% the exclusive property of the Client. Q & A Screening Questions (Required Before Proposal Submission) Question 1: In your very first sentence, please provide direct App Store / Roku Channel Store URLs or package names for at least two native living-room CTV apps you have personally built and published. Proposals without verifiable Roku or Fire TV links will be instantly archived. Question 2: Briefly describe your exact hands-on experience with Roku BrightScript/SceneGraph memory management and handling D-pad focus states for 50-channel EPG grids. Question 3: How do you implement asynchronous VAST/VMAP ad tags in native video players with a strict 3-second timeout, house-ad failover logic, and drop-off analytics telemetry to prevent UI freezing across web, mobile, and CTV? Question 4: What is your strategy for optimizing Supabase database queries and edge caching via Bunny.net CDN to ensure instantaneous load times for large video catalogs and EPG grid data across high-concurrency user sessions? Question 5: How do you manage app store compliance and fast-track approvals for streaming apps on Roku, Apple TV, and Fire TV, specifically regarding guest access, privacy policies, and playback error handling? To Apply: Please include links to recent native CTV apps you have built, along with a brief description of your specific role in the project.