Technical Lead/Solution Arc for Health Tech IoT Scaling
Publicada el 2026-07-27
Descripción de la oferta
We are a health technology company building a wireless, non-wearable fall detection sensor for elderly people. The sensor streams event and vitals data continuously to our cloud. When someone falls, the alert must reach a monitoring centre in seconds. Missed events end careers. If that framing makes you nervous, stop reading. If it makes you interested, continue. We are scaling from hundreds of devices to several thousand this year, with enterprise customers across the US, UK, Canada and Australia. We have a small in-house engineering team and multiple partner API integrations running in parallel. We need a senior technical voice reviewing what gets built and keeping delivery honest. WHAT YOU WILL DO - Review every pull request before merge. You are the merge gate. - Run a 15 minute daily standup with the engineering team. - Review timelines across all active projects. Challenge estimates, split oversized tasks, flag slippage early. - Set the standard for how work is organised. Ticket structure, definition of done, branching, review rules. Then enforce it. - Assess our current architecture and deliver a written report on what breaks first at 10x load. - Advise on event pipeline design, database scaling, queue durability, and failover. - Join technical calls with enterprise customers on scalability, uptime, and integration questions. WHAT WE NEED - 10+ years building backend systems in production, with real ownership after launch - Node.js in depth. This is your primary language, not something you picked up recently. - MongoDB at scale, including sharding, indexing, and query optimization - Hands-on IoT or real-time telemetry experience. Device fleets, continuous data streams, connection management at scale. Hard requirement. - Message queues (MQTT, RabbitMQ, Kafka, or equivalent), REST and webhook integrations - You have taken a system from small scale to thousands of concurrent connected devices and you remember exactly what broke - Healthcare or safety-critical systems experience is a strong advantage - You can tell a non-technical founder a timeline is wrong, and explain why in plain language - Reliable 8 to 10 hours per week, 24 hour turnaround on reviews, available for a fixed daily standup slot HOW THIS WORKS - 8 to 10 hours per week, fully remote, one fixed daily slot plus flexible time - Two week paid trial on real pull requests and one architecture question, then a 3 month engagement - Direct line to the founder, no layers - Hands-on technical role. Not people management, not pre-sales. TO APPLY, YOUR BID MUST INCLUDE ANSWERS TO ALL THREE. Bids without answers will be ignored. 1. Describe one IoT or real-time system you scaled and the first thing that broke. Be specific about the failure, the root cause, and the fix. Generic answers will be rejected. 2. Describe a time you told a stakeholder a delivery date was wrong. What was the evidence and what happened. 3. In one paragraph, at 10,000 concurrent devices each pushing an event every 2 seconds over MQTT to a Node.js backend writing to MongoDB, what breaks first and why. Do not send a template bid. Do not attach a generic CV without answers. Do not tell me your team of 20 can do this. This role is one person, part time.
Skills
Fuente original: freelancer