Description
The security function is being built out, and the role reports to Abhik, co-founder and VP of Engineering.
You get a mix of early-stage and growth-stage work: you write product specs, make product and design calls, and work in a team with very few meetings. The product has over 100,000 weekly active users who rely on it.
Annual recurring revenue is in the tens of millions and grows above 100% year over year, with low churn and many years of runway. More details are shared after a first conversation.
The Security team is one team with several specialties, covering security across the whole business.
Every application is read, and you will usually hear back within 3-4 days, often sooner.
Access now includes what an employee's AI tool can do on their behalf, so identity and permissions are an engineering problem. The questions are what a person or their agent can reach, and how to rebuild events when something goes wrong. The people using the controls matter as much as the risks they address.
Your mission is to automate and scale internal security access management and to give the company the visibility and response capability needed to investigate incidents. You own security integrations, identity workflows, operational telemetry, internal automation, and incident management for the Security team.
You work with IT on access and logging, with Engineering on service and agent identities, with Infrastructure on cloud signals, and with GRC on control requirements and AI governance evidence. GRC handles routine vendor diligence, and you add technical review when data sensitivity, privileged access, integration scope, or service criticality call for it.
You own the security logic that connects these systems and are the team's sole owner of incident management, from intake to follow-through. Application Security owns product authorization and AI feature threat modeling and adds specialist analysis during incidents. Together you keep access decisions and investigations consistent across people, services, and agents.
Less suited to the role: if you mainly want to administer consoles, believe access should always be blocked or always monitored, want every log collected before deciding what to detect, want AI agents making consequential access decisions without traceability, or only want project work.
In your first 3 months you could map key access paths, service and agent identities, and missing investigation evidence with IT and Engineering. You could propose initial prohibited access combinations, assess Okta and Cloudflare against contextual access needs, run a SIEM proof of concept, set up incident intake, severity and escalation criteria, playbooks and follow-up ownership, and test an early Slack investigation workflow. Work grows in scope and ambiguity as you learn how the company operates.