Louis, Head of Security, is building out the security function for the company, and this role is part of that build.
You will work in a single security team with several specializations that covers the whole business. Louis reports to Abhik, Co-Founder and VP of Engineering.
The company is at a stage where you help write product specs and make product and design calls, in a team that meets rarely. It serves over 100,000 weekly active users who depend on its software.
The company has tens of millions in ARR, growth above 100% year over year, very low churn, and many years of runway. More detail is shared after a first conversation.
The team is also exploring software for Talent Acquisition.
Every application is read. You will hear back within 3-4 days, often sooner.
Access is no longer only what people can reach themselves. It also includes what they can hand to an AI tool. Identity and permissions therefore become an engineering problem: you need to know what a person or their agent can reach, and rebuild what happened when something goes wrong.
The goal is to automate and scale internal security access management while keeping enough visibility and response capacity to investigate incidents. You will also care how security controls feel to the people who use them.
Your first three months are a ramp-up on the codebase, infrastructure, and team practices. Scope and ambiguity grow as you learn.
Early work could include mapping key access paths, service and agent identities, and missing investigation evidence with IT and Engineering; proposing the first prohibited access combinations; running a SIEM proof of concept on identity, SaaS, cloud, and repository signals; and setting up incident intake, severity and escalation criteria, playbooks, and a first Slack investigation workflow.
This role may not suit you if you mainly want to administer consoles, want to block or monitor access by default without weighing the tradeoff, want to collect all logs before choosing what to detect, want AI agents to make consequential access or response decisions without a trail, or only want project work rather than ongoing incident, tuning, and maintenance work.
Responsibilities
Automate identity lifecycle and access changes, including joiner, mover, and leaver flows, access reviews, expiring grants, and links to internal systems.
Define prohibited combinations of role, system, action, and data, then build access controls and monitoring sized to the risk.
Extend contextual access controls that check each request against current identity, device posture, and behavioral signals, and compare how Okta and Cloudflare could support those decisions.
Bring telemetry from identity, SaaS, infrastructure, repositories, and data systems into one place. Write and maintain detections and escalation rules with the outsourced SOC, and refine them from incident lessons.
Run a practical proof of concept across Datadog Cloud SIEM, Microsoft Sentinel, and Splunk, then recommend one based on coverage, investigation quality, effort, and cost.
Build agent attribution that links the initiating person, the acting agent, its credentials and permissions, the trigger, and the resulting actions, so activity can be reconstructed.
Send useful alerts and allowed response actions through Slack, with access checks, confirmation where needed, and an audit trail. Use AI for enrichment and triage, while a person stays accountable for consequential decisions.
Own incident management for the Security team, from preparation and intake through severity, containment, recovery, stakeholder updates, post-incident review, and closing follow-up actions. Build the evidence capture, playbooks, and automation that speed up investigations.
Own the security logic and automation linking these systems, and coordinate with IT on access and logging, Engineering on service and agent identities, Infrastructure on cloud signals, and GRC on controls and AI governance evidence.
Provide deeper technical review of vendors when data sensitivity, privileged access, integration scope, or service criticality call for it. GRC handles routine vendor diligence.
Work with Application Security, which owns product authorization and AI-feature threat modeling and supports incidents with specialist analysis.
Requirements
You have built integrations, internal tools, or automation for identity, security operations, or enterprise systems, and you write code that others can maintain.
You understand authentication, authorization, least privilege, and how access and delegation work across cloud and SaaS.
You have worked with logs, detections, and investigations, and have run a security incident to resolution. You know what evidence a responder needs to rebuild an event.
You care about how employees experience security controls, and you use data to stage changes and find workflows that need a better path.
You have applied AI or workflow automation to operational work and can explain its limits, permissions, and review points.
You work well with IT, Infrastructure, engineers, and nontechnical teams, and you can own a problem across those boundaries.
You can build integrations and security workflows in a language such as TypeScript, Python, or Go.
Senior level is the main target, with Staff candidates also considered. Senior means independently delivering substantial security work and helping other engineers use it. Staff means setting technical direction across teams, finding recurring problems, and building approaches others can extend.
Identity protocols, APIs, event data, and production automation matter more than any one vendor certification. Okta, Cloudflare, GitHub, Google Workspace, and cloud logs are relevant to the environment.
Conditions
Senior-level role, with Staff-level candidates also considered.
The company confirms this is an active, existing vacancy and may use AI-driven tools to help screen, assess, and select candidates.
Benefits
Competitive salary and equity.
Stock options with a 10-year exercise window. You can exercise when you are financially comfortable, with no pressure to buy if you leave.
Unlimited PTO, and the company encourages you to use it.
At least 12 weeks of fully paid parental leave, covered by the company, which may increase to meet local rules.
A generous budget for equipment, software, and office furniture.
$100/month education budget, with larger items such as conferences covered with manager approval.
$250/month tool budget, plus access to Claude, Cursor, and Codex with generous token budgets.
In the US, top-tier health insurance for you and your dependents, with 100% of premiums covered. In other countries, high-quality supplemental health insurance for you and your dependents, also fully covered.
Where you’d work
Fully remote
You can work from
Europe
United Kingdom
About the company
Hidden companyCompany hidden
Industry: SaaS
Good
Your chances
Still hiring, not crowded yet, and you'd be among the first.
17 checks run
7 good signs
0 red flags
Still hiring?
11 checks
Actively hiring
StaleHiring
In its favour4
Still on the company's own careers site, checked 1 h agoModerate evidence
Found in the last 48 hours, before the big job boardsModerate evidence
Specific about the basics: pay, place, level, stack and contract all statedSlight evidence
1 moreFewer
States its salarySlight evidence
How crowded?
6 checks
Low
QuietCrowded
In its favour3
In its Early Window: not on the big job boards yetStrong evidence
Senior level: far fewer people qualifySlight evidence
Asks for Datadog, which fewer than 1% of open roles doSlight evidence
?
Fits Me
How well does this role fit you?
Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.