Principal Engineer

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.

• 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.
• Stay in the Code: Prototype quickly, write production code on the most critical paths, and review designs and PRs across teams. Favor pragmatic, incremental rollouts that reuse what exists over rewrites.
• Technical Shaping and Economics: Lead technical discovery, feasibility, and sizing across your division's roadmaps. Weigh engineering investment against cost and business impact, and make the case for foundational work in business terms.
• Quality and Reliability: Define testing strategy, observability practices, and on-call health so teams can ship fast without breaking critical healthcare workflows.
• Raise the Bar: Grow Staff and Senior engineers into technical leaders. Shape hiring and leveling, including the architecture interview.