Senior Security Engineer

Own security engineering end to end for a pharmacy robot and every system it connects with, from the machine and operating-system image to cloud commands and the update path. In this hybrid role in Newark, CA, you will work in a small team with zero bureaucracy and high trust, partnering daily with the engineers building the on-machine software, cloud service, and OS image. You report to the Head of Software Engineering, with significant autonomy and influence.

What you’ll do

• Own security engineering for the pharmacy robot and everything it talks to: the machine, its operating-system image, the software on it, the cloud service that commands it, and the path that updates it.
• Maintain the threat model as a written record of trust boundaries, including machine to cloud, operator to screen, update path, remote support, and suppliers. Keep it current as designs evolve.
• Review designs early by providing security input when designs are still fluid, with each review recorded.
• Own device identity and key custody, including threat-model priorities and verification. Coordinate with engineers who own the operating-system image build-side platform work.
• Run independent security testing end to end, including defining scope and test environment, triage, remediation with the owning squads, and retest evidence.
• Find and drive fixes across code, dependencies, device images, and cloud. Set the rules, track each finding to closure, and report current status back to the squads that own each area.
• Lead the security side of incident response: detection, triage, containment, evidence, and follow-up changes. Coordinate with owning squads and run with Systems Reliability Engineers for operational response.
• Support customer security reviews by verifying every statement against evidence from versioned implementation, deployed configuration, and operational records. Keep what is built, designed, and planned clearly separated in customer commitments.
• Own cloud posture, including identity and access, secrets, review of infrastructure changes, and what cloud detection services report.
• Verify security and privacy controls, including controls derived from HIPAA, and collect system evidence for each control.
• Assess and recommend without accepting risk by default: record exceptions with their approver and documented conditions, with a business owner accepting the remaining risk.

Requirements

• Ownership of shipped product security end to end, with experience finding a real issue, fixing it, and following it through until it stayed fixed. Consulting-only or compliance-only experience is not the same.
• You build: you read and write code. Rust, TypeScript, and Python are used, with deep skill in one and comfort reading the others. Security reviews come with a patch or guidance precise enough to act on.
• Systems and network depth: TLS and certificates, identity and access, secrets management, and Linux hardening. You can reason about trust boundaries from hardware to cloud.
• Offensive fluency with defensive judgment: experience running or working closely with penetration tests. You can rank issues by impact and defend deferring certain work when appropriate.
• Threat modeling that engineers use: you prefer removing an input over adding a control, and engineers seek your review.
• Exact writing: you state what is true at the strength the evidence supports for engineers, executives, and customer assessors.

First 90 days

• Day 30: Trace trust boundaries personally. Hold the threat model and record of independent testing. Review your first design.
• Day 60: Own priorities and verification for device identity and key custody with OS image owners. Hold the inventory of secrets and keys and their rotation schedule. Verify every customer-bound security statement.
• Day 90: Write scope for the next independent test and prepare the environment. Record every design review you receive. Provide assessor-ready control evidence as system output.

Technologies you’ll work with

• Rust, TypeScript, Python
• TLS, Linux, AWS
• HIPAA, IEC 62443, UL 2900-1, NISTIR 8259

Nice-to-have

• Device security experience (verified startup, hardware-held keys, signed updates, fleet identity)
• Healthcare or other regulated-industry security experience, including supplier-side customer security reviews
• Cloud security engineering on AWS
• Supply-chain security (dependency policy, artifact signing, provenance)
• Working knowledge of IEC 62443, UL 2900-1, or NISTIR 8259

How we hire

• Recruiter Screen (30 min)
• Technical Interview (90 min) with a take-home exercise of 2 to 3 hours, sent at least 24 hours before: a small working system to harden. Review what you fixed first and why.
• Design Interview (60 min) focused on trust boundaries and key custody.
• Leadership Interview (60 min) focused on owning your work and collaborating across squads.

Two interviewers score each technical stage independently.

Our values

• Servant Leadership
• Do the Hard Things
• Own Your Work
• Default is Now

Own Your Work comes first in this role: follow the problem until it stays fixed.