Definitely! Although I notice Design System designers are undergoing a shift. More and more roles opening up are no longer focused on building UI kits with Tokens and documentation sites, because theres so many good templates for them for an org to start with (plus AI accelerates building these right now). The roles I'm seeing pop up now are much more focused on managing adoption, culture and future proofing systems with AI. Overall, less delivery work and more strategic discovery and design process management, which in my opinion is a good thing! We need to continue to prove that the human element of the design process continues to be empathy and strategic thinking, something AI will probably never truly excel at over humans. Because if humans keep trying to build component libraries, they're soon going to be cut-off in favor of AI.

I recently "rebranded" myself as UX Design Engineer, even though I've never properly written code before. Writing code is one part of the job, but understanding technical contraints and in general just how things work behind the visuals, is a key skill to have as a designer that wants to ship. In my current job I often encounter designers who complain about their designs not being shipped to production correctly or even at all and developers complaining about designers designing things that can't be created. I hope the lines will continue to blur between designers and developers. Vibe code tools are a major first step. I'm creating my own iOS app now (personal use), I'm using it to understand code bases and code rules, finding the boundaries of what's possible in design and code, and just bringing my ideas to life. I've never felt more empowered as a designer as right now, and I hope more designers and developers will use it to create a mutual foundation and skillset to work together more efficiently