Anrok Security Engineer at Anrok with 6+ years of experience in security engineering across application, cloud security, and detection and response. Build and secure AI systems including agents and LLM workflows.
Responsibilities
Most security teams grow by adding people: another analyst for alerts, another engineer for design reviews, another person for triage. We’re taking a different approach at Anrok.
As our first security engineer, you’ll build a strong product and cloud security program, covering secure development, a hardened cloud, detection and response, and incident leadership. AI agents handle the repeatable work so you can focus on the judgment calls. What you build in your first year will shape how far a small team can go as Anrok grows.
Anrok sits in the path of our customers’ revenue and holds sensitive financial, tax and identity data. For them, security is a crucial part of the product they’re buying.
What AI-native means here
Repeat work goes to agents. If you've done a task twice, the third time should be a workflow.
Agents propose, people decide. Anything that changes production, closes a finding or reaches a customer needs a human approver and leaves an audit trail.
Agents get the same scrutiny as engineers. Each one has its own identity, least-privilege access, logged actions and evals before we rely on it.
We measure leverage. The question is how much coverage one engineer gives a growing company, not how many tickets get closed.
What you'll build
Product and application security
A secure development process engineers trust: scanning in CI, AI-assisted review on pull requests that touch payments, credentials or auth, and threat models for our highest-risk designs.
Findings triage that mostly runs itself, plus our pentest and vulnerability disclosure programs, with each fix agreed with the owning team.
Qualification
6+ years in security engineeringStrong coding abilityGood judgment on riskSecuring LLM featuresDetection engineering as codeExperience in fintech
Required
6+ years in security engineering, with hands-on experience across application security, cloud security, and detection and response.
You’ve built with AI for real security work: agents, LLM workflows, MCP servers or retrieval over your own data. You know how these systems fail (made-up findings, prompt injection, permissions that are too broad) and you design for it. Show us something you’ve shipped.
Experience locking down access to sensitive data across production and internal tools, including scoped identities for people, services and agents.
You’ve owned technical controls for SOC 2 or ISO 27001, and you prefer evidence that comes from automation, not screenshots.
Strong coding ability. You read production code fluently and can review a pull request for security, not just run a scanner on it.
Hands-on security in a major public cloud, and fluency with infrastructure as code and CI/CD (e.g., Terraform, GitHub Actions).
You’ve led security incidents and can run a calm, well-documented response.
Good judgment on risk. You focus on the controls that matter most, explain trade-offs clearly to engineers and executives, and make the secure path the easy one for engineering teams.
Preferred
Experience as the first or an early security engineer at a fast-growing startup.
Securing LLM features, AI agents or MCP integrations in production, including evals or red-team testing.
Rolling out guardrails for company-wide AI use, such as tool and connector policies, shadow-AI discovery or data loss prevention.
Owning technical controls for SOC 2 or ISO 27001, with evidence that comes from automation, not screenshots.
Detection engineering as code.
Experience in fintech, payments or B2B SaaS with sensitive financial data.
Running pentest and vulnerability disclosure or bug bounty programs.
Certifications are welcome but not required. We care more about what you’ve built.