Companies hire for patterns. If you've spent your career polishing front-end experiences, that's the work you'll keep getting hired to do. However, content designers who think in systems—taxonomy, schema, measurement frameworks, language governance—often have skills that map directly to infrastructure-level problems companies might overlook if their portfolio focuses only on past front-end work. The gap between the work you're doing in your day to day and the work you want to be doing won't close on its own. You have to manufacture the pattern yourself.
This session walks through how I did exactly that. I identified a structural gap in the traditional voice computing stack, wrote a systems architecture proposal for a missing layer, defined its scope and limitations, designed a measurement framework, scoped failure modes as a design principle, and then used Claude Code to build a working prototype. The project is mine, not my employer's—and that's the point. It's a proof-of-work document that shows exactly how I think, what I prioritize, and why, within a domain I want to be hired into. I'm sharing the full process so you can apply it to your own dreams.
After this session, you'll be able to:
