Exploring an agentic developer experience

A high-level work summary from my professional experience at IKEA / Ingka Group. This describes a proof of concept, not publicly released code; private implementation details are intentionally omitted.

The problem

Developer experience is not only about having the right tools. It is also about knowing where to begin, finding relevant context, and understanding what to do next. I was interested in where agentic assistance could help with that work without making the underlying decisions harder to follow.

My contribution

I co-led the Agentic Developer Portal proof of concept. It brought together my engineering background and my growing product responsibilities, including my role as Product Owner (Acting) from January 2025. My contribution sat at that intersection: connecting a technical possibility with a useful developer problem.

My approach

I approached the work as an exploration, rather than a promise that an agent should handle everything. The important questions were about purpose and boundaries: what help is useful, what context is needed, and where a person should remain in control.

For me, a proof of concept is a way to make those questions concrete. A convincing interaction is a starting point for learning, not evidence of production readiness or broad adoption.

What I learned

I came away with a clearer distinction between demonstrating capability and earning trust. The product question is not simply whether an agent can complete a task. It is whether someone can understand its contribution, check the result, and comfortably decide what happens next.