▪Automate identity lifecycle and access changes, including joiner, mover, and leaver workflows, access reviews, expiring grants, and integrations with internal systems.
▪Help define prohibited combinations of role, system, action, and data, then implement access controls and monitoring proportionate to the risk.
▪Evaluate and extend contextual access controls that assess each request using current identity, device posture, and relevant behavioral signals. Compare how Okta and Cloudflare can support those decisions across internal systems.
▪Centralize useful telemetry from identity, SaaS, infrastructure, repositories, and data systems. Define and maintain detections and escalation rules with our outsourced SOC, improving them through incident learnings.
▪Evaluate SIEM options through a practical proof of concept, including Datadog Cloud SIEM, Microsoft Sentinel, and Splunk, then recommend an approach based on coverage, investigation quality, effort, and cost.
▪Build agent attribution: connect the initiating human, acting agent, credentials and permissions, trigger, and resulting actions so activity can be reconstructed.
▪Deliver useful alerts and permitted response actions through Slack, with access checks, confirmation where needed, and an audit trail. Use AI to help with enrichment and triage while retaining accountability for consequential decisions.
▪Own incident management from preparation and intake through severity assessment, containment and recovery coordination, stakeholder updates, post-incident review, and tracking follow-up actions to closure. Build the evidence capture, playbooks, and automation that make investigations faster and more reliable.
To ground it with examples, you could:
▪Build an access workflow that grants an appropriate capability for a limited period and automatically removes it, with the reason and owner attached.
▪Follow an agent’s repository or infrastructure action back to the human who initiated it and show the permissions it used.
▪Connect identity and SaaS events to an alert that gives an investigator enough context to act, then test whether the detection works without flooding the team with routine activity.
WHY YOU SHOULD AND SHOULDN’T APPLY
You should apply if:
▪You’ve built integrations, internal tools, or automation for identity, security operations, or enterprise systems, and you can write maintainable code.
▪You understand authentication, authorization, least privilege, and how access and delegation work across cloud and SaaS systems.
▪You’ve worked with logs, detections, and incident investigations, coordinated a security incident through resolution, and know what evidence a responder needs to reconstruct an event.
▪You care about the experience of employees using security controls, and you can use data to stage changes and find workflows that need a better path.
▪You’ve applied AI or workflow automation to operational work and can explain the limits, permissions, and review points of what you built.
▪You collaborate well with IT, Infrastructure, engineers, and nontechnical teams, and can own a problem across those boundaries.
You might not enjoy the role if:
▪You want to spend most of your time administering consoles. We want you to build integrations and automate recurring work.
▪You believe access should always be blocked or always be monitored. You’ll need to make the tradeoff explicit and implement the appropriate treatment.
▪You want to collect every log before deciding what to detect. We’ll start with risks and the evidence needed to investigate them.
▪You want AI agents to make consequential access or response decisions without traceability. Delegation has to preserve accountability.
▪You only want project work. Incident management, investigations, response, tuning, and maintenance are part of the job.
LEVEL AND EXPERIENCE
This posting is aimed at Senior engineers, and we’re also open to Staff-level candidates. We care about the systems you’ve built, the judgment you bring, and your ability to own a problem through implementation and operation.
At Senior level, we expect you to independently deliver substantial security work and help other engineers use what you build. At Staff level, we expect experience setting technical direction across teams, finding recurring problems, and building approaches that others can extend.
YOUR FIRST THREE MONTHS AT ASHBY
Your early changes will give you a tour of our codebase, infrastructure, and best practices, increasing in scope and ambiguity as you learn how we work.
Early on, you could:
▪Map key access paths, service and agent identities, and missing investigation evidence with IT and Engineering.
▪Propose the initial prohibited access combinations and assess Okta and Cloudflare against contextual-access requirements.
▪Run a SIEM proof of concept using representative identity, SaaS, cloud, and repository signals, comparing coverage and operational cost.
▪Establish incident intake, severity and escalation criteria, response playbooks, and follow-up ownership; test an initial Slack investigation workflow and agent-attribution path, and define when vendor diligence needs a technical security review.
ROLE-SPECIFIC TECHNOLOGY AND TOOLS
For this role, identity protocols, APIs, event data, and production automation matter more than one vendor certification. Okta, Cloudflare, GitHub, Google Workspace, and cloud logs are relevant to the environment. We’ll evaluate SIEM choices as part of the work. You should be comfortable building integrations and security workflows in a language such as TypeScript, Python, or Go.
BENEFITS
▪Competitive salary and equity.
▪10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby; do it when you feel financially comfortable.
▪Unlimited PTO, and we will encourage you to take it.
▪A minimum of 12 weeks of fully paid parental leave, covered by Ashby. The actual number may increase to satisfy local requirements.
▪Generous equipment, software, and office furniture budget. Get what you need to be happy and productive!
▪$100/month education budget with more expensive items (like conferences) covered with manager approval.
▪$250/month tool budget plus access to Claude, Cursor, and Codex with generous token budgets.
▪If you’re in the US, we offer top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby. In other countries, we provide high-quality supplemental health insurance for you and your dependents, also fully covered by us.
CLOSING
Ashby’s success hinges on hiring great people and creating an environment where we can be happy, feel challenged, and do our best work. We’re being deliberate about building that environment from the ground up. I hope that excites you enough to apply.
Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.
Ashby is committed to a fair and transparent hiring process. We confirm that this advertisement is for an active, existing vacancy within our organization. Please be advised that we may use artificial intelligence-driven tools to assist our recruitment team in screening, assessing, and selecting candidates for this position.