Sr. Staff Security Engineer

ABOUT OPENLOOP

OpenLoop was co-founded by CEO, Dr. Jon Lensing, and COO, Christian Williams, with the vision to bring care anywhere. Our telehealth support solutions are thoughtfully designed to streamline and simplify go-to-market care delivery for companies offering meaningful virtual support to patients across an expansive array of specialties, in all 50 states.

ABOUT THE ROLE

OpenLoop's mission is to bring care anywhere by powering telehealth solutions at scale. The Security Architecture & Engineering team defines how security is designed into every system that supports virtual care delivery across all 50 states. As Sr Staff Security Engineer, you will be the most senior technical authority on security architecture at OpenLoop, with approval authority over architecture decisions and responsibility for leading architecture reviews, driving threat modeling, and defining the standards and reference designs that engineering builds against.

WHAT YOU'LL DO

• Own and continuously evolve OpenLoop's security architecture across cloud infrastructure, applications, and corporate systems - defining standards, patterns, and reference architectures that teams build to.
• Lead threat modeling across product, engineering, and infrastructure initiatives, with particular attention to PHI data flows, patient-facing interfaces, and virtual care delivery systems - and coach engineers to threat model their own work.
• Conduct architecture reviews for new and existing systems, evaluating designs against security principles and regulatory requirements and producing actionable recommendations.
• Design and continuously improve the architecture review process itself so that it scales with engineering velocity - including self-service patterns, risk-tiered review paths, and clear criteria for when full review is required.
• Partner with the CTO and enterprise architecture function, embedding security review within existing technical governance rather than running a parallel process.
• Define and champion application security standards, including secure design principles, API security, authentication and authorization patterns (OAuth/OIDC, SAML), and data protection controls - including healthcare interoperability standards such as HL7 and FHIR.
• Establish and maintain a zero trust architecture strategy across identity, network, endpoint, and data layers.
• Architect and govern key management, secrets management, and certificate lifecycle practices across cloud-native environments.
• Own the security architecture for third-party integrations, defining how external systems connect to OpenLoop's environment and ensuring supply chain risk is controlled at the design stage.
• Serve as the primary security partner for product and engineering leaders, embedded in design and planning cycles to shape secure-by-default systems.
• Maintain security architecture documentation, including architecture decision records (ADRs), reference designs, and control frameworks.
• Take security and compliance requirements from GRC, Privacy, and audit partners and translate them into concrete architectural controls - with particular depth in the HIPAA Security Rule's technical safeguards as they apply to PHI architecture.
• Partner with the CISO and security leadership on the long-term architecture roadmap, producing clear metrics and executive-ready reporting on architecture risk posture.
• Mentor and elevate the broader security team, raising architectural thinking and design quality across all security domains.
• Research emerging threats and attack techniques - including threat actors actively targeting healthcare - to keep OpenLoop ahead of the threat landscape.
• Other duties as assigned.

WHO YOU ARE

• An architect who has owned the function, not contributed to it - you've built standards other teams actually adopted.
• Someone who scales themselves rather than becoming the queue everyone waits in. You'd rather teach ten engineers to threat model than review ten threat models.
• Comfortable being the most senior security voice in the room, and equally comfortable being overruled and managing the residual risk.
• Cross-domain by instinct: you think about identity, network, application, and data together rather than in isolation.
• Someone who understands that an elegant architecture nobody can operate is a failed architecture - and that a review process teams route around is a failed process.
• An enabler, not a gatekeeper. You've seen security teams become the department of "no" and you have opinions about why that happens.
• Self-directed, able to bring structure to ambiguous problems without waiting for it to be handed to you.
• Motivated by the fact that the systems you design protect health information for patients getting care they might not otherwise access.

REQUIRED QUALIFICATIONS

• Bachelor's degree in Computer Science, Information Security, or a related field, or equivalen