Product design
Dashboards, tables, ERP screens. Dense data that has to stay readable at 3am on a support call, and the states, empty cases and failures that decide whether an operator trusts the screen.
- Dashboards
- Data tables
- Flows
- Prototypes
Anton Dvorianinov, Product Designer
0Portfolio 2026 · Burgas, BG / EET
Product Designer · AI Design Engineer · Remote, EET
Six years in product design: SaaS platforms, dashboards, ERP, mobile apps and websites. I work on the screens where the money is actually made: the ones that decide how fast a customer starts paying, what a mistake costs, and how many support tickets never get written.
AI design engineering
The last stretch of that work went on closing the gap between the file and the thing people actually use. I write the spec, run the agents, read every diff, and own what lands in production. Design Engineer course, UX Hero, 2026.
Figma stays where the thinking happens: components, variables, prototypes, and a Dev Mode file an engineer can read without me in the room.
Variables export to tokens.json in the W3C format, Style Dictionary turns them into CSS, and Storybook documents the components where they actually run.
Claude Code takes the spec into HTML, CSS, Tailwind, React and TypeScript. A branch per change, a pull request to read it in, a deploy on merge.
Experience · CV
Research, product analytics, information architecture, prototyping, design systems, and the production code the design ships in. The tools for finding a problem matter as much as the ones for solving it.
Selected work
Case studies and side explorations across SaaS platforms, dashboards and design systems. There is more inside than UI.
What I do · 03
Not a menu of services. These are the parts of product design I have actually shipped, repeatedly: on a B2B platform people use for their job every day, and on client products and websites.
Dashboards, tables, ERP screens. Dense data that has to stay readable at 3am on a support call, and the states, empty cases and failures that decide whether an operator trusts the screen.
Typography, colour, spacing and components pulled into one library, documented, and kept honest across releases so a screen built three years apart still matches.
Interviews, usability testing and heuristic review, enough to know which of the five arguments in the room is the one the user actually cares about.
How I work · 04 steps
The same four steps whether it is a single screen or a five-year platform. Most of the value is in the first and the last one.
01 / 04
Who uses this, what breaks their day, and what the business needs out of it. Interviews, existing tickets, watching people work.
02 / 04
Information architecture and flows before pixels. Cheap to change here, expensive later. Agreement on scope in writing.
03 / 04
Wireframes to high fidelity, built from the system rather than around it. Every state drawn: loading, empty, partial, failed.
04 / 04
Detailed handoff, support through implementation, then look at what people actually do with it and fix what I got wrong.
Track record
Years in the craft, releases that went out, the industries the work went into.
Remote from Europe. Systems design, large platforms, and work shaped by real user feedback.