Security Engineer
Security Engineer
Posted 2 days ago
SENIORITY
Lead
About the role
- We hold customer specifications, expert identities and unreleased evaluation data. You'll build the controls that protect them: access, secrets, environment isolation, monitoring, and the processes customers audit before they work with us.
- What you'll own
- Identity, access and secrets management across the company.
- The isolation model for sandboxes and customer data, designed and reviewed.
- Detection and response for the events that matter, with the rest tuned out.
- Vendor and customer security reviews, with our evidence kept current.
- Security checks embedded in engineering workflows without slowing them down.
- What you bring
- Three or more years in security engineering with hands-on cloud and application work.
- You write code to solve security problems rather than only configuring tools.
- Compliance frameworks customers ask about, such as SOC 2.Clear communication with engineers and with customers' security teams.
- Helpful, not required
- Securing multi-tenant compute or ML systems.
- An offensive security background.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
