Systems built for machines to read
My sharpest work is making design systems machine-readable, so AI tools build from them consistently instead of guessing.
Senior product designer who designs and builds, from the first idea to the code that goes live. Paste a job description and I'll tell you where I fit.
I'm a senior product designer who doesn't stay in one lane. The consistent thing isn't a single specialism, it's curiosity: I follow a problem into whatever skill it needs, which over time has meant design, then design systems, then writing code and building AI tooling.
Day to day I'm at Brighte, working at the seam of design, engineering and AI. I ship my own front-end pull requests and shape the briefs rather than wait for them, because I understand the problem and the technical reality well enough to.
My sharpest work is making design systems machine-readable, so AI tools build from them consistently instead of guessing.
I took a "redesign the form" brief, reframed it as the data layer for an agentic system, and owned it end to end. 208 reviewed, 89% completion.
I work close enough to engineering to ship my own UI changes as reviewed pull requests, so the engineers stay on the harder problems.
I'm clear about where my depth ends. Being honest about the line is part of what makes the rest credible.
Rebuilt vendor accreditation around an agentic AI workflow. 208 applications reviewed, 89% form completion, 30+ automated checks per submission.
Read the case studyEverything here is answerable in Tyren's own words. Ask the brain directly, or paste a job description for an honest fit read.
Ask anything, or paste a job description for an honest fit read. Pasted JDs aren't stored.