Senior Python Developer Needed: Aviation Data Pipeline, Binary File Compiler & USB Desktop App

Project Title Aviation Data Management Platform — Backend Data Pipeline and Customer Update Application Project Type Fixed-price with defined milestones. NDA required before full technical details are shared. Budget Range Budget to be determined based on developer proposals and scope confirmation. See Phase 0 below for optional paid discovery engagement prior to full contract. We are seeking fixed-price bids broken down by milestone. Timeline Phase 0 (optional discovery): 2–4 weeks. Full project: first milestone within 30 days of Phase 0 completion (or contract execution if format spec is provided at kickoff). Full delivery within 2–3 months of main contract execution, assuming format documentation is in hand. Timeline to be confirmed by developer in proposal. Company Overview We are a U.S.-based aviation hardware company that manufactures proprietary data storage cards and a compatible USB programmer for a specific class of panel-mounted avionics used in general aviation aircraft. Our hardware is manufactured to ISO 13485 (medical device) quality standards and is currently in production. We are seeking a senior developer to build the software platform that powers our data update service. This is a greenfield project with no legacy codebase. All work will be owned exclusively by our company under a work-for-hire agreement. What We Are Building Important Note on Binary Format Documentation The binary output format for our hardware is proprietary. We are evaluating two paths for providing format documentation to the selected developer: Path A — We provide the format specification. If our hardware manufacturer can supply complete binary format documentation, we will provide it to the developer under NDA at project kickoff. In this case, the developer proceeds directly to implementation. Path B — Developer performs format analysis (Phase 0). If manufacturer documentation is unavailable or incomplete, we will provide the developer with physical hardware samples (data card + USB programmer + sample binary files) for independent format analysis prior to the main contract. Phase 0 is a separate paid engagement ($1,500–$3,000 fixed fee, 2–4 weeks) that produces a format specification document. If Phase 0 confirms the format is fully documentable, the developer proceeds to the main contract. If Phase 0 concludes the format is not feasible to document within budget, both parties may walk away with no further obligation. Developers who have prior experience with this class of aviation hardware binary formats are strongly encouraged to note this in their proposal. Prior knowledge of the format may eliminate the need for Phase 0 entirely and will be weighted heavily in developer selection. We need two connected software components: Component 1 — Internal Data Processing Pipeline (Backend) Our company receives structured aeronautical navigation data on a 28-day cycle from a U.S. government source. This data is in a well-documented industry-standard text format (ARINC 424 / fixed-width records). We need a backend pipeline that: • Ingests the raw source data files on each 28-day cycle • Parses and validates the data against known format specifications • Compiles the parsed data into a proprietary binary output format specific to our hardware • Packages the compiled binary for distribution to our customer update application • Runs automatically on each cycle with logging and error alerting The binary output format is proprietary to our hardware. We will provide the developer with full format documentation, sample binary files for reference, and physical hardware for testing. The developer does not need to reverse-engineer anything — the format specification will be provided under NDA. Component 2 — Customer-Facing Update Application (Desktop) Our customers are general aviation pilots — non-technical users. They own our hardware (a data card and a USB programmer). They need a simple desktop application that: • Runs on Windows 10/11 and macOS 12+ • Detects our USB programmer when plugged in • Downloads the current cycle's compiled binary from our server (authenticated) • Writes the binary to the data card via the USB programmer • Displays clear progress and success/failure status • Sends a reminder notification 3 days before the next 28-day update is due • Requires no technical knowledge to operate — one-click update The USB programmer presents a standard USB HID profile. The write protocol is documented and will be provided under NDA. No driver development is required. Technical Requirements Backend Pipeline: • Language: Python 3.10+ preferred; Go acceptable • Deployment: Linux server (VPS or cloud); Docker preferred • Scheduler: Cron or equivalent for 28-day cycle automation • Output: Binary file packaged for authenticated download • Logging: Structured logs with error alerting (email or webhook) Customer Application: • Language: Python (PyQt6 or Tkinter) or Electron (Node.js) • Packaging: Windows .exe installer (NSIS or Inno Setup), macOS .dmg • USB communication: PyUSB or libusb • Update delivery: HTTPS download from our server with checksum verification • No cloud account required for the end user — authentication is handled by our platform Integration between components: • The backend pipeline produces a versioned binary file • The customer application checks our server for the current version on launch • If a newer version is available, it downloads and writes it automatically What We Will Provide to the Selected Developer Under NDA, the selected developer will receive: • Full binary output format specification with annotated sample files • USB programmer write protocol documentation • Physical hardware (data card + USB programmer) for development and testing • Access to the source data format specification (ARINC 424 documentation) • Sample source data files representing a full 28-day cycle • Access to our existing web platform for integration (REST API) What We Are Looking For in a Developer Required: • 5+ years of Python or systems programming experience • Demonstrated experience with binary data formats, file parsing, or protocol implementation • Experience building cross-platform desktop applications (Windows + Mac) • Experience with USB device communication (PyUSB, libusb, or equivalent) • Ability to work independently with minimal supervision • U.S.-based or willing to work U.S. business hours for communication Strongly preferred: • Experience with aviation data formats (ARINC 424, FAA NASR, or similar) • Experience with embedded systems or hardware-adjacent software • Experience with automated data pipelines and scheduled jobs • Prior work-for-hire projects with IP assignment agreements Not required: • Aviation pilot certificate or aviation industry background • Avionics hardware engineering experience Deliverables and Milestones Milestone Deliverable Payment 1 — Kickoff (Day 0) NDA signed, technical briefing completed, development environment confirmed TBD 2 — Pipeline Prototype (Day 30) Backend pipeline ingests source data and produces correct binary output on test hardware TBD 3 — Application Alpha (Day 60) Customer application detects programmer, downloads binary, writes to card on Windows TBD 4 — Cross-Platform + Polish (Day 90) macOS support, installer packaging, reminder notifications, error handling TBD 5 — Final Delivery (Day 120–150) Full documentation, source code transfer, 30-day bug fix period TBD Intellectual Property All work product, source code, documentation, and related materials produced under this contract are work-for-hire and become the exclusive property of our company upon payment of each milestone. Developer retains no rights to the work product. A standard IP assignment agreement will be required at contract execution. How to Bid Please submit a proposal that includes: 1. Your relevant experience with binary data formats and USB device communication (specific examples preferred) 2. Your proposed technical approach for the backend pipeline and customer application 3. Your estimated timeline and fixed-price bid broken down by milestone 4. Two or three references or portfolio examples of similar technical work 5. Your availability to start and your preferred communication method Please do not submit a generic proposal. We will only respond to proposals that demonstrate specific technical understanding of the work described. Proposals that ask for more information before bidding are welcome — we will share additional technical details under NDA. NDA Requirement A mutual NDA is required before full technical specifications are shared. We will provide the NDA within 24 hours of a proposal being accepted for review. Signing the NDA does not obligate either party to proceed with the project. This project involves proprietary aviation hardware and software. All technical details beyond what is described above are confidential and will be shared only under NDA. Path B — Developer performs format analysis (Phase 0). If manufacturer documentation is unavailable or incomplete, we will provide the developer with physical hardware samples (data card + USB programmer + sample binary files) for independent format analysis prior to the main contract. Phase 0 is a separate paid discovery engagement (fixed fee to be negotiated, estimated 2–4 weeks) that produces a format specification document. If Phase 0 confirms the format is fully documentable, the developer proceeds to the main contract. If Phase 0 concludes the format is not feasible to document within budget, both parties may walk away with no further obligation. Milestone day counts assume format documentation is available at contract kickoff. If Phase 0 is required, the clock starts after Phase 0 deliverable is accepted.