Agent Security Engineer
Belmont Lavan Ltd Netherlands
- Location
- Netherlands
- Closing date
- Not provided
- Published on
- 6 November 2026
- Contract
- Full-time
- Field
- Information Technology
- Area
- Outside Africa — visa sponsorship (according to the posting)
How to apply
Free account: “Apply” prepares your CV and letter for this offer; you then send your application yourself. You can also apply directly from the original listing.
Description
Belmont Lavan is hiring an Agent Security Engineer to secure autonomous AI agents before and after they reach production. Agents now call tools, hold credentials and act on live systems, so they need the controls we already expect for people and services: identity, least-privilege access, monitoring and testing.
You will sit between AI engineering and security. You will design the guardrails, attack the systems yourself, and build the governance controls that let the business deploy agents with confidence.
Requirements
- 5+ years in security engineering (AppSec, cloud security, IAM or offensive security), with at least 1 year securing LLM or agent-based systems
- Hands-on knowledge of LLM attack techniques: prompt injection, jailbreaks, data exfiltration via tools, RAG poisoning
- Experience designing identity and access controls: OAuth 2.0 / OIDC, token exchange, workload identity, secrets management
- Working knowledge of agent frameworks and protocols such as LangGraph, OpenAI Agents SDK, CrewAI or Model Context Protocol (MCP)
- Strong coding skills in Python, plus one of Go, TypeScript or Rust
- Cloud security on AWS, Azure or GCP, including logging, detection and policy-as-code (e.g. OPA / Cedar)
- Ability to explain AI risk clearly to engineers, risk teams and executives
Find more English Speaking Jobs in Netherlands on Arbeitnow
How to apply
Sign in to save this job, then track your application.
Where the job is located
location given by the source: Amsterdam, Netherlands
Map background © OpenStreetMap contributors, loaded from their servers. City coordinates: GeoNames. Privacy
Listing origin
seen on the original site on 12 November 2026 at 21:32 (Paris time)
We regularly check that the offer is still published there.
Information not provided by the source
duration, work arrangement, salary, reference