Senior Security Engineer

queueinc is building security around a pharmacy robot and the connected systems it relies on. In this role, you own security engineering end to end for the machine, its software and operating-system image, the cloud service that controls it, and the update path that keeps it current.

You will translate system architecture into usable threat models, run design and independent security reviews, and back up customer-facing security statements with versioned evidence. The work spans incident response, cloud posture, and verification of security and privacy controls aligned to relevant regulated requirements.

What you will own

• Security engineering for the pharmacy robot and everything it communicates with, including the machine, its OS image, the software that runs on it, the cloud service that commands it, and the update path.
• Threat modeling as a written model of trust boundaries covering machine-to-cloud, operator-to-screen, the update path, remote support, and suppliers, kept current as designs change.
• Security review of designs submitted early in the process, with your review recorded.
• Device identity and key custody, including the threat model, priorities, and verification, working with the engineers who own the operating-system image.
• Independent security testing end to end, including scope, test environment, triage, remediation with the owning squads, and retest evidence.
• Finding and fixing weaknesses across code, dependencies, device images, and cloud, tracking findings to closure and reporting status to squads that own each area.
• Security involvement in incident response, covering detection, triage, containment, evidence, and what changes afterward, working alongside systems reliability engineers for operational response.
• Customer security reviews where answers are treated as commitments, verified against evidence such as versioned implementation, deployed configuration, and operational records, while separating what is built, designed, and planned.
• Cloud posture across identity and access, secrets, infrastructure change review, and what the cloud provider’s detection services report.
• Security and privacy controls verification, including controls that follow from HIPAA, gathering evidence from the system.
• Risk assessment and recommendations, including recording exceptions with their approver and ensuring an authorized business owner accepts what remains.

Key skills and background

• Ownership of security for a shipped product end to end, with the ability to describe a problem you found, fixed, and followed until it stayed fixed (not consulting-only or compliance-only).
• Building skills: you read and write code. The team uses Rust, TypeScript, and Python.
• Systems and network depth across TLS and certificates, identity and access, secrets management, and Linux hardening, with the ability to reason about trust boundaries from hardware to cloud.
• Offensive fluency with defensive judgment, including running or working closely with penetration tests, ranking issues by impact to the system and users, and defending appropriate deferrals.
• Engineer-used threat modeling, with a bias toward removing inputs rather than adding controls, and a willingness to review designs proactively.
• Exact writing that states what is true at the strength the evidence supports for engineers, executives, and customer assessors.

Technologies

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

First 90 days

• Day 30: trace trust boundaries personally, hold the threat model and independent testing record, and review the first set of designs.
• Day 60: hold priorities and verification for device identity and key custody with the OS image engineers, maintain the inventory of secrets and key rotation schedule, and ensure every customer-facing security statement is checked first.
• Day 90: write the scope for the next independent test and prepare the environment it will run against, ensure every design review is recorded, and provide assessor-ready control evidence produced from the system.

Nice-to-have

• Device security experience, including verified start-up, hardware-held keys, signed updates, and fleet identity.
• Security in healthcare or other regulated industries, plus customer security reviews from the supplier’s side.
• Cloud security engineering on AWS.
• Supply-chain security, including dependency policy, artifact signing, and provenance.
• Working knowledge of IEC 62443, UL 2900-1, or NISTIR 8259.

How the hiring process works

• Recruiter Screen: 30 minutes.
• Technical Interview: 90 minutes, including a take-home exercise of 2 to 3 hours (sent at least 24 hours before) to harden a small working system. The session reviews what you fixed first and why.
• Design Interview: 60 minutes, focused on trust boundaries and key custody.
• Leadership Interview: 60 minutes, focused on owning your work and collaborating across squads.
• Two interviewers score each technical stage independently.

Location and work setup

• Newark, CA (hybrid), with three days a week at the Bay Area headquarters. Device security work requires hardware access.

What you can expect

• Ownership of security engineering for the machine and everything it talks to.
• Hard problems spanning trust boundaries from hardware to cloud, device identity and key custody, and the update path.
• Small team with zero bureaucracy and high trust.

Role alignment and values

You report to the Head of Software Engineering with significant autonomy and influence. The same person sets the security requirements you will work to, and you collaborate daily with engineers building the on-machine software, the cloud service, and the operating-system image. Queueinc values Servant Leadership, Do the Hard Things, Own Your Work, and Default is Now, with Own Your Work taking priority by following problems until they stay fixed.