I'm sitting through day one of AI Engineer World's Fair San Francisco, and I'm struck by how effectively the schedule embraces the beautiful fuzziness of "AI." In the past, I might have questioned a conference that lumps together developers who "just use the tools" with those diving into the core science. But being here, it clicks: both are AI engineers, even if their day-to-day jobs look entirely different.
Look at the workshop lineup. On one end, you have sessions like Kent C. Dodds' Product Engineering for Software Developers, targeting practitioners building practical, agentic workflows. On the opposite end of the spectrum, you have Daniel Han from Unsloth leading a deep dive into Special topics in Kernels, RL, and Reward Hacking.
One is about high-level orchestration, UX, and shipping product; the other is about the raw, nuts-and-bolts infrastructure of inference and model optimization.
Does it make sense to commingle these two distinct roles under one banner?
Absolutely. AI is aggressively redefining the organic dividing lines of our tech communities. The old tribal boundaries — where we siloed ourselves strictly by language or stack — are giving way to a shared, collaborative push into the agentic era.
The definition of an "AI engineer" isn't static, and it shouldn't be. Right now, keeping the product builders and the infrastructure scientists in the exact same room is a feature, not a bug. It's an inclusive, diverse context that is keeping all of us on the bleeding edge.
Top comments (0)