A vibe coding conference in Amsterdam.

Vibe coding is describing the behaviour you want in plain language and working with an AI system that writes and runs the implementation. You read what came back, judge it, and adjust in words rather than syntax.

At VibeConf that is treated as a working method, not a genre. The interesting part is never the generation itself; it is what a person decides before they ask, and how they tell whether the result is right. Sessions are held to that standard: what was built, what it cost, what broke, and what the speaker would now do differently.

The syntax barrier moved. The judgement did not.

Not only developers. The room is deliberately mixed, because the people who understand a problem in detail are now often the people building the first version of the answer.

• →Product, design and engineering. People shipping real things, comparing where AI genuinely shortens the path and where it quietly adds work.
• →Marketing, sales, HR and operations. People building the internal tool, workflow or prototype their team needed, without waiting for a backlog slot.
• →Founders and hands-on leaders. People who still build, and who have to decide what their organisation adopts next.

If you have never written code, the companion guide to coding with AI for non-developers is the best preparation for the day.

The common reading of this shift is that every role is collapsing into one generalist. In practice the opposite happens. A marketer with AI is still a marketer — with a wider range. A designer does not become an engineer; they get to test the interaction instead of describing it. Depth of expertise is what makes the output any good.

That is what we mean by the product builder era: building is now a behaviour available across functions, rather than a department you file a request with. The longer argument, with the practical method behind it, is in our guide to building products with AI.

Talks grounded in real work

Damian Skotzke asks where AI stops being a tool and starts acting like a collaborator, from his own product-design and design-engineering projects. Jim van der Waal argues that permission shapes what teams build more than tooling does, drawing on the rituals his product teams set up to learn together.

Workshops you leave with something from

Elena Avramenko builds the first working screens of a mobile app live, with no code written by hand. Dima Abramov runs a session on turning one recurring routine into a small agent you will actually use again.

People who have done it, in one room

Single track, no parallel sessions, roughly a hundred people. The programme and the full speaker line-up — including Debora Gallo and Marijn Markus — are on the main conference page. What happens between sessions is the reason the room is kept small.

Tuesday 6 October 2026, at Pathé Tuschinski, Reguliersbreestraat 26-34, 1017 CN Amsterdam — a 1921 Art Deco cinema a few minutes’ walk from Rembrandtplein, and one of the more unreasonable rooms in the city to watch someone build something in.

VibeConf grew out of Vibe Coding Amsterdam, the community behind it, which runs hands-on evenings, workshops and buildathons across Europe throughout the year. The archive there is the most honest preview of the conference.