About Us
Agentic coding tools such as Claude Code, GitHub Copilot, Cursor and Codex are changing how our engineers work, and new capabilities arrive faster than we can currently absorb them.

You will join a small existing team that already owns this area, with established tooling, working relationships across engineering, and colleagues who know the landscape. You will not be starting from scratch or figuring it out alone. What we need is the capacity and depth to keep pace: teaching teams what has become possible, building it into our templates and golden paths, supporting teams directly when things do not work, and assessing which developments are worth adopting.

This work sits directly on the Accelerate lever of our “Winning Ways” strategy — enabling people to use AI effectively in their own area of work, and prioritizing the applications whose value has been proven in fast, focused pilots. For software engineering, that is this team's remit.

Responsibilities
This position suits an engineer with an active interest in how agentic coding changes software work,



rather than a general interest in AI.

When a new model or agent feature ships, you try it within days, against your own hard problems rather than a toy example — a legacy refactor whose shape you already know, a test suite that resists, a migration you have previously done by hand. Your views come from that, not from reading about it, and you can distinguish a real capability improvement from a well-produced demo. The second-order question interests you as much as the result: if this holds, what does it change about how we review code, structure repositories, write specifications and run CI?

You will probably recognize yourself in the following:
- You write and iterate on your own agent configuration — instruction files, custom commands, subagents, MCP servers — rather than accepting the defaults.
- You know how differently these tools behave on a large, old, inconsistent codebase than on a greenfield pr

📌 AI Engineer (Madrid)
🏢 Basf
📍 Madrid