AI-Proof Engineering Jobs — Netherlands

Build the internal developer platforms, internal tooling, and infrastructure abstractions that everyone else uses. When you own the platform, you own the leverage. AI can't replace the person who built the environment it runs in.

AI writes YAML — you build the system that runs it

SREs own the reliability contract between engineering and the business. On-call, incident response, SLA enforcement, and error budgets require judgment calls with real financial consequences. AI assists but can't take the 3am call.

AI-assisted alerting — human owns the outcome

Shift security left into the pipeline, own the threat model, do penetration testing, and design zero-trust architectures. Security engineers sign off on architecture — that's legal accountability AI can't carry.

Humans sign security reviews — not AI models

Own the tools that other developers use: internal CLIs, scaffolding generators, IDE plugins, code quality dashboards, and CI/CD templates. You determine how everyone else ships code — high leverage, high ownership.

Build the AI tools — don't be used by them

Build the data pipelines, feature stores, model training infrastructure, and deployment systems that power AI — rather than being replaced by it. Data engineering owns the data contract — essential regardless of what models run on top.

Pipelines outlive models — own the plumbing

Work at the layer below application code: distributed systems, consensus protocols, storage engines, networking kernels. These require formal reasoning about correctness, performance, and failure modes that AI can't reliably produce.

Correctness proofs > autocomplete