Technical Lead - Robotics Healthcare

Job title

Founding Robotics Systems Architect (Healthcare)

Location

Remote (US / EU / GCC time zones preferred) with travel to GCC as needed for pilots

Employment type

Contract / Advisory (Pre-funding) Full-time after funding (target)

Job description (paste this)

About LuxAI

LuxAI is a stationary clinical concierge system designed to stabilize front-desk operations in premium clinics and hospitals. It performs administrative reception workflows with deterministic, policy-driven behavior (check-in, eligibility/payment readiness, and waiting guidance) while explicitly excluding clinical decision-making.

We are currently pre-funding. We have the robot visuals and a locked, stage-based patient journey system (five flows). We are now assembling technical leadership to convert this into a buildable, pilot-ready system.

Role summary

We are hiring a senior, systems-level technical leader who can architect the end-to-end LuxAI platform across:

1. Robot hardware architecture (compute, peripherals, payment module integration posture, handset privacy design, serviceability)
2. Device software architecture (UI runtime, voice/handset modes, document scanning flows, local device control, offline-safe behavior)
3. Cloud platform architecture (workflow engine, device management, security, logging/monitoring, integration layer)

This is not a single-component role. The goal is a coherent system architecture that is pilotable, observable, secure, and scalable.

What you will lead (first 3045 days, pre-funding)

• Produce a Technical Execution Brief (buildable spec) that converts our locked patient flows into an implementable architecture
• Define the system boundaries and non-negotiables (privacy posture, deterministic behavior, safe failure modes, no clinical reasoning)
• Recommend the compute stack (industrial PC vs SBC; where edge logic ends and cloud begins; offline/latency strategy)
• Define the device software structure (modules, services, state machine/workflow runtime, monitoring, update strategy)
• Define the cloud platform structure (APIs, workflow orchestration, queue/waiting link service, identity/eligibility hooks)
• Craft an integration posture for pilots: minimum required integrations, best-effort connectors, and clean deferral when systems are slow/unreliable
• Produce a V1 pilot scope plan (appointments-first) with milestones, team roles, and risk gates

Deliverables should be practical: architecture diagrams, interface contracts, a build plan, and a hiring map.

What we are

not

asking you to do

• We are not asking you to build everything solo.
• We are not asking for speculative AI diagnosis or clinical decision systems.
• We are not asking for a flashy prototype that breaks in real clinics.

We are asking you to design a system that survives reality.

Ideal background (must-have)

• Senior technical leadership experience shipping production systems that combine device + cloud (robotics, kiosks, medical devices, or regulated/healthcare-adjacent systems)
• Strong systems thinking across hardware + device software + backend/cloud
• Experience designing for reliability, observability, and safe failure modes
• Comfort working with privacy/security constraints (PHI/PII awareness; least-privilege patterns; auditability)

Strong plus

• Healthcare workflows exposure (PMS/EMR integration patterns, eligibility/payment flows, clinic operations reality)
• Fleet/device management experience (updates, monitoring, incident response, remote diagnostics)
• Experience with payment hardware integration posture (without overpromising scope)

Engagement structure (truthful and flexible)

• Pre-funding: advisory/contract engagement to produce architecture + execution plan
• Post-funding: transition into full technical leadership to build and lead the team
• Compensation structure is flexible depending on start timing:
• If you engage pre-funding: equity-heavy advisory structure can be discussed
• If you engage post-funding only: full-time compensation post-funding with potential equity component

Screening (how we evaluate fit)

A strong candidate can clearly explain:

• how they would architect the edge vs cloud split
• how the robot behaves when internet is weak or systems are unavailable
• how updates, monitoring, and failure recovery work
• how to structure pilot-first integrations without brittle dependencies
• how to convert workflows into deterministic system logic

Next step

If you apply, we will shortlist candidates for a 3045 minute architecture conversation.

We will share the patient journey system and the current deck during the processy.