PROJECT MANAGER — AI-FIRST, CROSS-FUNCTIONAL DELIVERY

Lumimeds

senior

Job description

<div class="content-intro">About LumiMeds LumiMeds is a fast-growing U.S.-based telehealth startup focused on weight management and long-term metabolic health. We are building the next generation of e-commerce and clinical infrastructure from the ground up. As an early-stage company, we move quickly, operate with limited layers, and expect high ownership from every team member. There is no bureaucracy here — decisions happen fast, priorities evolve, and builders thrive. We are a remote-first, globally distributed team that values clarity, accountability, and people who take initiative rather than wait for direction.</div>Platform & Product Engineering — LumiMeds Location: Remote — partial US hours overlap required (minimum 4–5 hours daily overlap with US Pacific/Eastern) Seniority: Manager — Player/Coach <h2>What We're Building</h2> LumiMeds is a high-growth telehealth platform building the operating system for modern virtual care — an AI-accelerated clinical engine, a high-converting e-commerce storefront, a consumer mobile app, and intake infrastructure that moves at the speed our patients expect. We don't scale engineering by adding headcount. We scale by multiplying leverage — through better systems, better tooling, and better use of AI. Our engineers already orchestrate Claude agent teams in production. Your job is to raise the ceiling on what that means. <h2>The Role</h2> We're looking for a Project Manager who is obsessed with outcomes, not process for its own sake. You will own cross-functional delivery across Engineering, Product, Clinical, and Operations — keeping initiatives moving, dependencies untangled, and the right people unblocked at the right time. This is not a role for someone who color-codes Jira and calls it a day. You will use AI tooling to eliminate grunt work from your own workflow, write specs that agents and engineers can execute autonomously, and bring systems thinking to everything you touch — from sprint rituals to cross-team escalations. <h2>What You'll Actually Do</h2> <ul> <li>Own project delivery end to end. Track initiative progress across engineering, clinical, product, and ops. Surface blockers early, coordinate dependencies, and keep stakeholders informed without over-communicating.</li> <li>Run sprint and delivery rituals. Facilitate planning, standups, retrospectives, and reviews — but only the ones that create real alignment. Cut anything that doesn't.</li> <li>Write specs that move. Produce project briefs, PRDs, and task breakdowns that are structured, precise, and executable — by engineers, AI coding agents, or junior team members — with minimal back-and-forth.</li> <li>Use AI to remove work. Automate recurring status updates, meeting notes, and reporting. Build lightweight automations that free the team from low-value admin.</li> <li>Manage risk proactively. Identify scope creep, resource conflicts, and timeline drift before they become incidents. Escalate with proposed solutions, not just problems.</li> <li>Hold the cross-functional seam. Product wants to ship. Engineering needs clarity. Clinical has compliance requirements. Ops is watching cost. You translate between all of them without losing fidelity.</li> <li>Improve delivery systems over time. Audit your own processes. Kill what doesn't work. Version-control the rituals that do.</li> <li>Measure everything. Every initiative has a baseline, a target, and a definition of done. If you can't tell whether something shipped successfully, the spec wasn't complete.</li> </ul> <h2>What You'll Own</h2> <table> <tbody> <tr> <td> Domain </td> <td> Scope </td> </tr> <tr> <td> Cross-Functional Delivery </td> <td> Engineering, Product, Clinical, Ops — initiative tracking, dependency management, unblocking </td> </tr> <tr> <td> Sprint Rituals </td> <td> Planning, standups, retrospectives, reviews — streamlined and outcome-focused </td> </tr> <tr> <td> Project Documentation </td> <td> Briefs, specs, status updates, risk registers — clear and always current </td> </tr> <tr> <td> AI-Augmented Workflows </td> <td> Automations that replace recurring manual PM tasks </td> </tr> <tr> <td> Stakeholder Communication </td> <td> Async-first updates, escalations, and alignment across all functions </td> </tr> <tr> <td> Delivery Metrics </td> <td> Velocity, predictability, on-time delivery, blocker resolution time </td> </tr> </tbody> </table> <h2>Required Skills & Experience</h2> Non-negotiables: <ul> <li>5+ years in project management, program management, or a delivery-focused ops role at a software company or startup</li> <li>Demonstrated ability to run cross-functional delivery across Engineering, Product, and Ops with minimal oversight</li> <li>Hands-on AI tooling use — you have automated your own work, built a workflow, or written prompts that replaced a recurring task</li> <li>Strong written English — all communication is async, in writing, in English</li> <li>Ability to write specs and project briefs that AI agents and engineers can execute with minimal back-and-forth</li> <li>Fluent in project tracking tools: Linear, Jira, Asana, Notion, or equivalent</li> <li>Availability to work U.S. business hours consistently</li> <li>High agency — you identify problems, propose solutions, and execute without waiting to be managed</li> </ul> Nice to Have: <ul> <li>Experience in telehealth, healthcare, SaaS, or a regulated industry</li> <li>Familiarity with HIPAA-adjacent workflow constraints</li> <li>Experience working alongside AI coding agents (Claude Code, Cursor, or similar)</li> <li>Background in technical project management — you can read a PR, understand a schema, and hold your own in an engineering design conversation</li> <li>Experience building or owning internal tooling specs alongside engineering teams</li> <li>A project, system, or automation you can point to and explain in detail — what it solved, how you built it, what it unlocked</li> </ul> <h2>Why LumiMeds</h2> AI as infrastructure, not a feature. We've already rewired how we build around AI. You won't be evangelizing something new — you'll be operating at the frontier with a team that's already bought in. Real technical complexity. Clinical state machines, real-time patient-provider flows, high-stakes billing, HIPAA. The problems are hard because the domain is hard. Small team, enormous leverage. You won't manage through layers. Your decisions show up in production the same week. Direct impact. The systems you build affect patient outcomes. That's not a cliché here — it's the constraint that makes the work matter.<div class="content-conclusion">How to Apply If this role sounds like a fit, we’d love to hear from you. Please submit your application in English and ensure your resume reflects relevant experience for the role. This position is open to candidates based in approved locations, depending on the role and business needs. Qualified applicants will be contacted for next steps. LumiMeds is an equal opportunity employer. We hire based on skills, experience, and alignment with our values. Please note: This role requires professional-level English communication and availability to work U.S. business hours.</div>