Senior Full-Stack / Electron Engineer to Take Existing Product to Beta — September Deadline

Job Description We are looking for a senior hands-on software engineer or small senior engineering team to take over an existing working software product and bring it to a production-ready beta. This is not a greenfield project. The system already has substantial functionality, company-owned GitHub repositories, API documentation, environment/configuration documentation, and a working hardware implementation. The immediate objective is to complete the remaining engineering work, transition the device runtime to a Windows-based Intel mini-PC environment, build the minimum administration UI/UX required for beta operation, and have a stable beta release ready for deployment in October 2026. Timeline is critical. We need someone who can begin immediately and dedicate enough senior engineering capacity to target a beta release candidate by September 30, 2026. Current Technology The existing system includes technologies such as: Node.js / Express React Redux / Material UI WebSockets Sequelize / MySQL Chromium Electron / transparent desktop overlays Linux-based device runtime REST APIs cloud backend local device software The current working implementation uses Raspberry Pi hardware. The next production-beta hardware target is an Intel N100-class Windows mini-PC. What Remains The selected developer/team will be responsible for taking ownership of the existing codebase and completing the remaining beta-critical work, including: reproducing and understanding the existing system from the repositories and documentation; completing reliable local/offline device operation; completing device-side playback/scheduling behavior; improving long-duration reliability and recovery; transitioning the device-side runtime to Windows mini-PC hardware; preserving compatibility with the existing backend rather than creating a separate architecture; building a simple beta administration UI/UX so normal operations do not require developer tools; integration testing and debugging; documenting deployment, configuration, architecture, and operational procedures; producing a reproducible beta release that can be maintained by another qualified developer. This is an existing product that needs technical ownership and execution, not merely individual feature development. Required Experience We are looking for someone with strong professional experience in most of the following: Electron desktop applications transparent / always-on-top windows Node.js and Express React REST APIs and WebSockets Windows application/runtime development Linux Chromium integration offline/local caching and synchronization media or video playback hardware acceleration / GPU / compositor troubleshooting long-running desktop or edge applications application startup, monitoring and recovery packaging and deployment debugging and taking ownership of an existing codebase Experience with digital signage, kiosk systems, media players, video overlays, edge devices, streaming-video environments, or similar systems is highly desirable. A traditional web developer without desktop/runtime, Chromium, media, or operating-system experience is unlikely to be a good fit. Critical Architecture Requirement We do not want the product tied permanently to one developer, one operating system, or one hardware device. The engineer must understand how to keep core application logic, backend communication, device state, and business logic maintainable and portable while isolating platform-specific Windows/Linux implementation where appropriate. All development must remain in company-controlled repositories, with sufficient documentation for another qualified engineer to reproduce, deploy, and maintain the system. Expected Schedule We expect approximately: Week 1 — Technical takeover Review repositories and documentation, reproduce the existing system, identify risks, and confirm the completion plan. Weeks 2–4 — Core beta functionality Complete remaining device-side/offline functionality and begin Windows mini-PC implementation. Weeks 3–5 — Windows + UI/UX Complete the Windows runtime and minimum beta administration interface. September — Integration and stability Long-duration testing, debugging, deployment procedures, and beta release preparation. Target beta release candidate: September 30, 2026. Target real-world beta deployment: October 2026. Applicants who cannot realistically commit the necessary availability during August and September should not apply. When Applying Please answer all of these questions. Generic proposals will not be considered. Have you personally inherited an existing production or prototype codebase and taken it through deployment? Briefly describe the project and your role. What hands-on experience do you have with Electron and transparent/always-on-top desktop windows? What experience do you have with Windows desktop/runtime development and Chromium? Have you built an application that must continue operating locally when internet connectivity is lost and synchronize when connectivity returns? Describe it. What experience do you have troubleshooting video playback, hardware acceleration, GPU/compositor behavior, memory/resource leaks, or long-running application stability? How would you approach moving an existing Linux device application to Windows while avoiding unnecessary changes to an existing backend architecture? Are you personally going to review and write the code? If a team will perform the work, identify the senior engineer who will own the architecture and implementation. How many hours per week can the senior engineer dedicate during August and September 2026? Can you start immediately and realistically target a September 30 beta release candidate? Please provide examples of the most technically similar projects you have completed. Shortlisted candidates will receive additional technical documentation and architecture details before final selection.