*AI Engineer *— Build the AI Brain of a Clinical System. On a Real Platform. With Real Users. Check out the role overview below If you are confident you have got the right skills and experience, apply today. * Location: Salt Lake City, Utah (preferred) * Reports to: Founder * Works closely with: Product/technical leadership and the practitioner channel * Role Type: All-in, high-ownership builder role with real creative authority * Compensation: Competitive base + performance bonuses. Equity eligibility in Year 2 for exceptional performers. * Performance Standard: Exceptional or not retained *READ THIS FIRST* This is a rare combination, and we know it. We need someone who can do two things most engineers treat as opposites. You'll build a brand-new agentic AI clinical co-pilot from a near-blank page — the kind of greenfield AI work people dream about. And you'll do it on top of a real, live health platform with years of .NET behind it and practitioners depending on it every day. That second part is not a footnote. The future doesn't get built on a clean slate here — it gets built on a working system that already serves people, which you'll modernise as you go. If "legacy archaeology" makes you groan, this isn't your role. If it makes you think "give me the codebase, I'll find the business logic and bring it forward" — keep reading. You'll have direct founder access and the freedom to make real product and architecture decisions. We don't want a pair of hands. We want someone with the taste and judgment to make the Co-Pilot genuinely excellent — and the engineering depth to ship it fast. *If you're looking for*: - A pure greenfield job with no old code to touch - A clear playbook someone else wrote - A comfortable pace where you learn the domain before you deliver - A title without real authority This role is not for you. *WHY THIS MATTERS* For 100 years, medicine has treated the body as a chemical system. Drug discovery costs double every nine years while efficacy halves. Chronic disease keeps accelerating despite trillions in spending. The model is failing — spending more to produce less — and everyone inside it knows it. We treat the body as what it actually is: a bioelectric system. Every cell holds a voltage, communicates through electromagnetic signals, and stores energy in structured water. When those fields are coherent, biology self-organises and the body heals. We have two decades of R&D, 300+ peer-reviewed sources, proprietary diagnostic and therapeutic technology, and a global practitioner network already using it. What's missing is the intelligence layer — the AI that turns all of that into the right next move for a real patient. That's what this role builds. *WHAT YOU'LL BUILD — THE FIELD CLINIC CO-PILOT* Field is our health system: one intelligence reading the whole body — pulse, face, voice, tongue, blood labs, wearable data, and full history — and turning it into the right next action. There are two sides: the consumer app, and the practitioner system you'll own the engine for. The Field Clinic Co-Pilot is the AI that practitioners work alongside. It reads every signal a patient generates, drafts the next move — labs, protocols, refills, follow-ups — routes it to the practitioner for approval, delivers what they sign off on, and then measures whether it worked. The loop is the product: Measure. Decide. Deliver. Measure again. *A few things that define how it has to work, and that you'll be responsible for getting right:* - The human stays in the loop, always. The AI never orders a lab or sends a prescription on its own. It drafts; a licensed practitioner reviews, edits, or declines; only then does anything reach a patient. Most approvals should take under 60 seconds — that "fast and safe" balance is an engineering and design problem you'll own. - One engine, two faces. The consumer AI coach and the clinical co-pilot are the same brain on a shared backend — one doing intake, the other drafting clinical protocols. Build the approval and delivery workflow once; it serves both. - It's branded around the clinic. When a patient comes in through a practitioner, the experience carries that clinic's name, photo, and preferred therapies. The intelligence underneath stays consistent; the front the patient sees belongs to their clinician. - It closes the gap between visits. Patients fail in the silence between appointments. The Co-Pilot's job is to make sure something is watching the whole picture continuously, and surfacing what matters to the practitioner before it becomes a problem. You'll build this agentically: multi-modal inputs in, drafted clinical actions out, a tight approval workflow, real delivery rails, and a measurement loop that makes the next reading sharper than the last. *WHAT YOU'LL BE RESPONSIBLE FOR* 1. Build the Co-Pilot — agentic, fast, excellent Design and ship the agentic AI that ingests multi-modal patient data and drafts the next clinical move for practitioner approval. You'll make real calls on how the agents are structured, how context and memory are managed, how safety and confidence are surfaced, and what the practitioner's approval experience feels like. Prototype aggressively, test in reality, kill what doesn't work, scale what does. 2. Modernize the platform underneath it The existing practitioner platform runs on legacy .NET. You'll keep it healthy while pulling it forward — refactoring and migrating components to current frameworks, standing up new services on a modern stack, and doing it incrementally without breaking what practitioners rely on today. 3. Own the full stack Database through API to front end. You'll design schemas, write and optimise queries, build and integrate APIs, wire up third-party services, and deliver working interfaces. You don't have to be the world's best at every layer — but you need to move confidently across all of them and know when something's off. 4. Work AI-first We expect AI to do as much of the building as possible — code generation, testing, research, automation. You already use AI to accelerate your own work; here it's a core operating principle, not a perk. *THE STACK* Existing / legacy stack — you must be comfortable working in this: * .NET Framework 4.5 * C# with ASP.NET MVC 3 and above * Entity Framework and LINQ * HTML / CSS * JavaScript and jQuery * Microsoft SQL Server (MSSQL) * TFS for source control * IIS 8 Modern stack — where the platform is heading: * .NET Core / .NET 8+ * REST API design, build, and integration with third-party services * Microsoft Azure — App Services, SQL Database, Functions, Key Vault, Storage * A modern JavaScript framework — React, Angular, or Vue (tell us your preference and why) * Git, alongside or replacing TFS Authentication: * Duende IdentityServer (OAuth2 / OpenID Connect) — the platform's self-hosted auth service *Core competencies — must have*: * SQL Server: schema design, stored procedures, query optimisation, migrations * API connectivity and integration * Strong C# fundamentals across both old and new framework versions *Strongly desirable*: * Experience migrating legacy .NET Framework apps to .NET Core / .NET 8+ * CI/CD pipelines (Azure DevOps or GitHub Actions) * Automated testing (unit and integration) * Legacy archaeology — working with undocumented code, reverse-engineering business logic, and refactoring incrementally without taking production down * Real experience building with AI agents, LLM orchestration, and multi-modal or time-series data *WHO THIS ROLE IS FOR* * You're a strong C# / .NET engineer who isn't afraid of old code — you can read an undocumented system, find the business logic, and bring it forward * You've built real things with AI agents, not just prompted them — and you want to build a lot more * You move across the full stack with confidence, from SQL schema to API to front end * You have taste — you know what "excellent" feels like and you'll push for it * You want founder access, real creative authority, and outsized ownership * You ship fast, accept imperfect information, and prove ideas in reality instead of in decks * You're drawn to the idea that medicine itself is about to change, and you want to help build what comes next *WHO THIS ROLE IS NOT FOR* * You only want greenfield work and won't touch legacy code * You can prompt but you can't engineer * You need someone to tell you exactly what to build * You optimise for job longevity over impact * You need a large org, long timelines, and established process to feel safe *HOW WE WORK* * Build first. Test in reality. Refine what survives. Scale what proves itself. * AI does the work. Humans direct, decide, and quality-check. * Speed beats perfection. Depth beats speed when speed is fake. * Prototypes, not slideware. Evidence, not opinions. * Direct founder access. High autonomy. Very high expectations. * Small team, big ambition, no bureaucracy. *REWARDS & UPSIDE* * Competitive base salary + performance bonuses tied to real output * Equity eligibility in Year 2 for exceptional performers — tied to contribution, not tenure * Direct partnership with the founder and real authority over how the Co-Pilot gets built * Ownership of the AI engine at the centre of a clinical system practitioners use worldwide * Early exposure to category-defining IP spanning two decades of biophysics research and proprietary technology * The chance to build something that will matter for a long time *WHAT YOU NEED TO SHOW US* We care about what you've actually built — not your degree or your resume polish. * AI agents, LLM systems, or automations you've built — and what they did * .NET / C# systems you've shipped, especially anything where you modernised or rescued legacy code * Full-stack work where you owned database through front end * Evidence you move fast with imperfect information and produce results * Side projects and obsessive explorations — welcome, if the output is exceptional *INTERVIEW PROCESS* We'll give you real problem statements from our platform and the Co-Pilot. Come ready to talk about: - How you'd architect an agentic clinical co-pilot with a human-approval loop that's both fast and safe - How you'd approach modernising a live .NET Framework platform without breaking production - How you'd design the data and API layer connecting multi-modal inputs to drafted clinical actions - What you've already built with AI agents — and what you learned - What about physics-first medicine interests you, and how fast you'd go deep on the science We're evaluating how you think, how fast you move, and whether you're someone our team would want to build with. *FINAL FILTER* If reading this makes you feel energised by the build, excited by the freedom and the founder partnership, and certain you're the rare engineer who can do both the legacy work and the AI future — apply. xxoysbn If it makes you feel like you'd need to be convinced — this probably isn't your role, and that's okay. Benefits: * Health insurance * Paid time off Work Location: In person