Windows Electron + React/TypeScript App — Finish Build, Test Suite, CI/CD & Signed Release
Budget: $250 – $750 SGD
Project Description
Overview
I have a Windows desktop application that is approximately 90% built and I need an experienced engineer to take it across the finish line: close out the remaining feature work, build a proper automated test suite, set up a production CI/CD pipeline, integrate code signing, and ship the first signed public release.
This is a fixed-scope, fixed-deliverable project with a defined end date. It is not an open-ended retainer. If the engagement goes well there may be ongoing maintenance work afterwards, but that would be negotiated separately.
The product is a productivity tool for business users. Further detail on the product itself will be shared after an NDA is signed — please don't ask me to describe the product concept in the public chat.
Current State
Core application is built and functional in development
Frontend, backend, database schema and native audio layer are all implemented
What's missing is the last mile: edge-case handling, hardening, tests, packaging, release infrastructure and production deployment
Tech Stack
Desktop: Electron, React, TypeScript Native module: Rust sidecar (Windows audio APIs via windows-rs), IPC to Electron main process Backend: Node.js + TypeScript (NestJS) Database: PostgreSQL with pgvector, on AWS RDS Infra: AWS (us-east-1) Auth: WorkOS Real-time: Authenticated WebSockets Target platform: Windows 10/11 only (no macOS, no Linux)
Scope of Work
1. Finish remaining feature work (~10%)
Close out a defined punch list of outstanding items (list provided post-NDA)
Error handling, edge cases, loading and empty states
Reconnection/recovery logic on the WebSocket layer
2. Automated test suite
Unit tests for backend services and business logic
Integration tests covering the API and database layer
End-to-end tests for critical desktop user flows
Basic test coverage for the Rust sidecar and its IPC boundary
Target: sensible, meaningful coverage of critical paths — not a coverage-percentage box-tick
3. Build & release pipeline
electron-builder + NSIS installer configuration
electron-updater auto-update with stable and beta channels and delta updates
Code signing for both the Electron app and the Rust sidecar binary (EV certificate will be procured and provided by me — you configure the signing integration)
GitHub Actions CI/CD: build, test, sign, publish signed artifacts to the update feed
Reproducible builds, versioning and release tagging
4. Observability
Sentry integration on the Electron process and the Rust sidecar (including native minidumps)
Sensible error grouping and release tracking
5. Production deployment
Deploy backend to AWS
Environment/secrets management
Basic runbook documentation for deploys and rollbacks
Deliverables
Punch-list items completed and merged
Passing test suite running in CI on every PR
Working GitHub Actions pipeline producing signed installer artifacts
Auto-update verified working across two sequential versions on a clean Windows machine
Backend live in production on AWS
Sentry receiving errors from both processes
Short written handover document: architecture notes, deploy runbook, rollback procedure
Milestones
# Milestone Payment
1 Punch list complete, all features working in dev 25%
2 Test suite complete and green in CI 25%
3 Signed build pipeline + auto-update verified end-to-end 30%
4 Production deployment, observability live, handover doc delivered 20%
Required Experience
Essential:
You have shipped and signed a production Windows Electron app — not just built one locally
Hands-on experience with electron-builder and electron-updater (channels, delta updates)
GitHub Actions CI/CD for desktop application release pipelines
Strong TypeScript across both Node backend and React frontend
Working knowledge of Rust — enough to test, debug and maintain an existing sidecar
Comfortable with AWS deployment and PostgreSQL
Nice to have:
Windows audio API experience (WASAPI)
NestJS
pgvector
Native crash reporting / minidump handling
Terms
NDA required before any product detail or repository access is shared
Full IP assignment — all work product assigns to my company. A written contractor agreement will be signed before work starts.
You must confirm you have the right to take on this work — i.e. no employer agreement or existing obligation that would conflict with assigning IP on this project
Work performed on your own equipment and accounts
Credentials will be scoped and revocable; you will not receive production root access
To Apply
Generic or copy-paste bids will be ignored. Please answer the following in your proposal:
Link me to a Windows Electron app you have shipped and signed. What signing method did you use — hardware token, cloud HSM, or a signing service?
EV code signing certificates are generally bound to hardware tokens or HSMs. How would you integrate that into a GitHub Actions pipeline? Tell me what you'd actually use.
Have you worked with a Rust binary as a sidecar to an Electron main process? What IPC mechanism did you use, and how did you handle sidecar crashes?
What is your testing approach for an Electron app? Which frameworks would you use for E2E, and how do you handle the main-process/renderer split?
Roughly how many hours do you estimate for this scope, and what is your availability per week?
State your fixed price for the full scope and your hourly rate separately.
Overview
I have a Windows desktop application that is approximately 90% built and I need an experienced engineer to take it across the finish line: close out the remaining feature work, build a proper automated test suite, set up a production CI/CD pipeline, integrate code signing, and ship the first signed public release.
This is a fixed-scope, fixed-deliverable project with a defined end date. It is not an open-ended retainer. If the engagement goes well there may be ongoing maintenance work afterwards, but that would be negotiated separately.
The product is a productivity tool for business users. Further detail on the product itself will be shared after an NDA is signed — please don't ask me to describe the product concept in the public chat.
Current State
Core application is built and functional in development
Frontend, backend, database schema and native audio layer are all implemented
What's missing is the last mile: edge-case handling, hardening, tests, packaging, release infrastructure and production deployment
Tech Stack
Desktop: Electron, React, TypeScript Native module: Rust sidecar (Windows audio APIs via windows-rs), IPC to Electron main process Backend: Node.js + TypeScript (NestJS) Database: PostgreSQL with pgvector, on AWS RDS Infra: AWS (us-east-1) Auth: WorkOS Real-time: Authenticated WebSockets Target platform: Windows 10/11 only (no macOS, no Linux)
Scope of Work
1. Finish remaining feature work (~10%)
Close out a defined punch list of outstanding items (list provided post-NDA)
Error handling, edge cases, loading and empty states
Reconnection/recovery logic on the WebSocket layer
2. Automated test suite
Unit tests for backend services and business logic
Integration tests covering the API and database layer
End-to-end tests for critical desktop user flows
Basic test coverage for the Rust sidecar and its IPC boundary
Target: sensible, meaningful coverage of critical paths — not a coverage-percentage box-tick
3. Build & release pipeline
electron-builder + NSIS installer configuration
electron-updater auto-update with stable and beta channels and delta updates
Code signing for both the Electron app and the Rust sidecar binary (EV certificate will be procured and provided by me — you configure the signing integration)
GitHub Actions CI/CD: build, test, sign, publish signed artifacts to the update feed
Reproducible builds, versioning and release tagging
4. Observability
Sentry integration on the Electron process and the Rust sidecar (including native minidumps)
Sensible error grouping and release tracking
5. Production deployment
Deploy backend to AWS
Environment/secrets management
Basic runbook documentation for deploys and rollbacks
Deliverables
Punch-list items completed and merged
Passing test suite running in CI on every PR
Working GitHub Actions pipeline producing signed installer artifacts
Auto-update verified working across two sequential versions on a clean Windows machine
Backend live in production on AWS
Sentry receiving errors from both processes
Short written handover document: architecture notes, deploy runbook, rollback procedure
Milestones
# Milestone Payment
1 Punch list complete, all features working in dev 25%
2 Test suite complete and green in CI 25%
3 Signed build pipeline + auto-update verified end-to-end 30%
4 Production deployment, observability live, handover doc delivered 20%
Required Experience
Essential:
You have shipped and signed a production Windows Electron app — not just built one locally
Hands-on experience with electron-builder and electron-updater (channels, delta updates)
GitHub Actions CI/CD for desktop application release pipelines
Strong TypeScript across both Node backend and React frontend
Working knowledge of Rust — enough to test, debug and maintain an existing sidecar
Comfortable with AWS deployment and PostgreSQL
Nice to have:
Windows audio API experience (WASAPI)
NestJS
pgvector
Native crash reporting / minidump handling
Terms
NDA required before any product detail or repository access is shared
Full IP assignment — all work product assigns to my company. A written contractor agreement will be signed before work starts.
You must confirm you have the right to take on this work — i.e. no employer agreement or existing obligation that would conflict with assigning IP on this project
Work performed on your own equipment and accounts
Credentials will be scoped and revocable; you will not receive production root access
To Apply
Generic or copy-paste bids will be ignored. Please answer the following in your proposal:
Link me to a Windows Electron app you have shipped and signed. What signing method did you use — hardware token, cloud HSM, or a signing service?
EV code signing certificates are generally bound to hardware tokens or HSMs. How would you integrate that into a GitHub Actions pipeline? Tell me what you'd actually use.
Have you worked with a Rust binary as a sidecar to an Electron main process? What IPC mechanism did you use, and how did you handle sidecar crashes?
What is your testing approach for an Electron app? Which frameworks would you use for E2E, and how do you handle the main-process/renderer split?
Roughly how many hours do you estimate for this scope, and what is your availability per week?
State your fixed price for the full scope and your hourly rate separately.