I turn complex workflows into products and systems teams can ship and keep running. I’ve done it inside Apple, Disney, and startups, and in products I build independently.
Open to senior and staff-level roles with ambitious product teams.
Scroll
Shipped with
Selected work
Logos say where. These say what.
Three pieces of shipped work, each a different kind of evidence: what I am building now, scale inside a large organization, and one you can open and run right now. Every case study opens with the problem, the role, and what actually shipped.
I had the pleasure of working closely with Timurtek on several projects at Disney. He brings a rare combination of design sensibility and engineering precision — the kind of collaborator who closes the loop between concept and shipped product without losing the intent of either. His work elevated every team he touched.
Sarah DossProduct Designer @ The Walt Disney Company“
Timurtek is a skilled, and detail oriented UI/UX Engineer who I’ve had the pleasure to work with over 3 years at Disney. His ability to produce pixel perfect user interfaces is rare, especially when combined with Timurtek’s friendly, and positive attitude. As a strong team member, and an expert in UI and UX, Timurtek has helped produce complex component libraries, and features to serve critical business needs.
The design system and the gates around it, the Report Center 2.0 interface, the marketing site from commit zero, a knowledge base with its own retrieval-backed chat agent, and the org brain that turns every meeting into a searchable record.
In progress
The Data Hub interfaces, design first: the production plan gates that work on the designs before a screen gets built.
What I can show today
The marketing site and the knowledge base are public at mixshift.ai. The case study covers the rest, limited to what the repositories show. MixShift’s numbers land when they say so.
Twelve months on GitHub
6,716contributions
244 active days · 66-day longest streak
Client work and my own products, counted together. Most of it is in private repositories, which GitHub shows as daily counts with no names attached. Zengin is open source: read the case study, or the code on GitHub.
Design and engineering as one function, inside the team.
One team at a time, the same way whether it is a role or an engagement.
01
When
Where I fit.
A product team with more workflow than hands. There's an AI roadmap, or the pressure to have one, and nobody whose job it is to turn it into systems that run in production. I take the layer between the model, the interface, and the people who have to use both.
02
Start
How it starts.
With the one workflow that costs the team the most hours. I model what fixing it is worth before anything larger gets built, and if AI isn't the answer for it, I say so.
03
Work
What working together looks like.
Your Slack, your standups, your codebase, your on-call rotation if it matters. I ship inside the stack with the engineers: the pipelines, the eval infrastructure, and the operator-grade interfaces that turn model output into something the team opens every day.
04
Own
What the team owns at the end.
Code, prompts, infrastructure, runbooks, and the habit of running them. I build so the system outlives my hands on it, whether I stay on the team or hand it off.
The path here
For a decade I was the designer who could ship and the engineer who could design, at Apple, at Disney, and at a run of startups. The work was design systems: the layer that decides whether a hundred product teams ship coherent software or a hundred slightly different ones.
AI systems fail the same way design systems do: they work in the demo and fall over in operation, because nobody owned the layer between the model and the people who have to use it. That layer is what I now build. The longer version →
Independent products, owned end to end: finding the problem, designing, shipping, operating. The same model I bring to an engagement, with nobody to hand off to but myself.
Decision-intelligence platform for traveling skilled trades workers. Real pay data, contractor safety records, housing intel, and area ratings, built for the 500K+ tradespeople who travel for contracts.The studio venture at full surface area. Marketplace economics, federal-data ETL, content automation, paid SaaS billing, full SEO posture. All shipped solo with Claude as a daily collaborator. The operating model on display.
Field notes from an AI-native operator. I design, develop, market, and shape product direction with Claude as a daily collaborator. One letter, no hype.
How a one-person stack actually decides what to build
Operator-grade patterns across the full product surface
Honest field notes: what shipped, what broke, what I'd do differently
Field notes from a rebuild: what I learned redesigning my own site with Claude in the loop.
~9 min read · No more than once a week
Unsub any time · No tracking · No share-this-with-your-team CTAs
Next step
Two ways in.
Hiring for a senior or staff role where product thinking meets production systems, or a team that needs this for a season? Thirty minutes, no sales flow.
Not there yet? Read how I got here, or start with the case study that best matches what you’re trying to build.
