Remote
Senior Security Engineer
About this role
Senior Security Engineer Reports To: Sr. Director of IT & Security Locations hiring from: Alabama, Arizona, Arkansas, California, Colorado, Delaware, Florida, Georgia, Idaho, Illinois, Indiana, Kansas, Louisiana, Maine, Maryland, Massachusetts, Michigan, Minnesota, Missouri, Nevada, New Hampshire, New Jersey, New York, North Carolina, Ohio, Oregon, Pennsylvania, Rhode Island, South Carolina, Tennessee, Texas, Utah, Vermont, Virginia, and Wisconsin.
Employment Type: Full-time Role Overview: As Oshi Health's first dedicated Senior Security Engineer, you will own the technical security of our fully remote, SaaSand cloud-native healthcare platform, protecting the sensitive health data of real people working to take back control from chronic GI conditions. This is a hands-on, builder-focused role, not a policy desk: you will set security architecture standards, harden identity and secrets management, and build security into our engineering and AI workflows from the start.
It is a uniquely forward-looking opportunity to shape how a growing healthcare platform stays safe as it adopts agentic AI development, with your fingerprints on the foundation. What You'll Do — Key Responsibilities Own application and product security, including threat modeling, secure design review, and secure code review, with a focus on the access-control and secrets-exposure flaws that matter most for a member-facing healthcare app and its APIs.
Design and own the security architecture for Oshi's shift to an agentic software development lifecycle, including phase-gate criteria, out-of-band controls so AI-written code is never its own security gate, and tested clawback procedures for when risk spikes. Build and run non-human identity and secrets management at scale, covering service accounts, scoped tokens, OAuth grants, and machine credentials across our SaaS and AWS estate.
Secure our AWS environment end to end, including IAM, network segmentation, logging, encryption, and workload protection across S3, EKS, and Terraform. Enforce and tune our security tooling so it does real work, including GitHub Advanced Security (CodeQL, secret scanning, push protection), branch protection, and CODEOWNERS-enforced review on sensitive paths. Review AI and third-party vendor integrations before they touch PHI, evaluating data flows, retention, and data loss-prevention needs with healthy skepticism toward vendor security claims.