Founding Engineer

Tech Nova Time  builds digital replica employees for healthcare: agents that watch a human do a job for weeks, learn the underlying logic, then run that job themselves inside the same software the human used. Founding team automated 10M+ labor hours for the DoD. Now applied to healthcare admin.

We're hiring a Founding Engineer to take ownership of Mimic Capture, our core product surface for turning a recorded human process into a usable spec.

Here's what's true:
Capture already turns real recorded work into specs our agents run on, and it's live with real customers. What we don't have is someone who owns it end to end: architecture, implementation, production operation, and roadmap.

• You're building the ownership structure around Capture from scratch.
• Customer evidence goes in one end, shipped product comes out the other, continuously. You're not writing one-off customer code.
• Every deployment should make the product better for the next customer, not just solve the one in front of you.

• Capture, end to end. Architecture, implementation, and the roadmap for where it goes next.
• Production operation. You're accountable for uptime and output quality on the paths customers depend on.
• The feedback loop. Field evidence from Forward Deployed Engineers and customers turns into what you build next.

Onboarding is inconsistent. Time to first value and completion rate vary account to account. You own fixing that.

Field learning doesn't reliably make it back into the product. What Forward Deployed Engineers learn on-site needs a real path into Capture's roadmap, not an ad hoc one.

• A new customer reaches first value in under 10 minutes
• 80%+ of customers who start a Capture finish it
• Customer-rated output accuracy of 4.3/5 or higher
• Validated priority changes hit production in 7 days or less
• 99.9%+ uptime on critical production paths

A shipper, not a side-project builder. You've shipped and owned production software. This is unlikely to be a good fit if your strongest work has been personal projects or academic research.

Genuinely deep in ML/agentic systems. You understand the systems, not just how to call an API against a model. This is unlikely to be a good fit if your ML experience starts and ends with prompting.

Fast without breaking what matters. You move quickly, but you know which parts of the system can't take shortcuts. This is unlikely to be a good fit if you either move too slow to ship or ship things that break in production.

Wants real ownership. You want architecture-level decisions, not a ticket queue. This is unlikely to be a good fit if you'd rather be told what to build than decide it.

• A ticket queue. You decide the architecture and the roadmap.
• A role writing one-off customer code. Every deployment improves the core product.
• A caretaker seat. Capture doesn't fully exist as an owned system yet. You're building it.

• Cash: $180,000–$275,000 based on qualifications