Parachute Health · posted · checked
Principal Engineer
PythonRubyTypeScript$265k – $300kRemote · United StatesStaff+
Who can apply
Remote · United States
- “- Must reside in the U.S.”
- “Applicants must be legally authorized to work in the United States at the time of application and for the duration of employment.”
Location: U.S. Remote
Parachute Health is transforming post-acute care as the leading digital ordering platform for medical equipment and supplies. We connect major health systems, health plans, and suppliers to help patients get the life-saving products they need at home. Since launching, we've connected 300,000+ clinicians and 3,000+ supplier locations across all 50 states and helped 15M+ patients. What started as a DME ePrescribing tool has become the order management platform of choice for home medical equipment.
Join our team and make a difference in patient care.
About the Role
We are seeking a Principal Engineer to be the technical leader of one of our engineering divisions. You will own the architecture and technical direction across multiple teams working on core parts of the Parachute platform — the workflows that connect clinicians, health systems, health plans, and HME providers so patients get the equipment they need at home.
This is a hands-on, division-wide role. You will partner with engineering managers, Product, and Design to set direction across teams, make the hard technical calls, and stay close enough to the code to prove them out. As Parachute pivots from feature delivery toward foundational, AI-driven infrastructure, you will serve as a definitive technical leader, trusted to untangle ambiguous problems and deliver high-impact solutions.
Responsibilities
Division Architecture: Define the architectural standards and target state for your division. Make sure the systems your teams own evolve coherently instead of drifting apart at the seams.
Large-Scale Refactoring: Drive the refactoring needed to give teams clear domain ownership and independence inside a large shared codebase, sequenced so delivery keeps moving.
Decisive Technical Leadership: Take ambiguous, cross-team problems and turn them into a clear direction, a plan, and shipped software. Make the call, own it, and see it through.
Work in the Open: Lead technical decisions through Architecture Decision Documents and open discussion. Engage directly on others' proposals, state objections plainly and early, and model the transparency you expect from others.
AI-Native Engineering: Set the standard for how your teams build with AI — agentic coding, review and test acceleration, repo-native tooling and MCP servers. Raise the PR bar and show what great looks like.