01.
Scenarios and states
User flows, transitions, and screen families
UX Architecture
Interface Structure
It connects the product model, user roles, scenarios, data, states, and routes into a clear interface structure.
It helps establish where a scenario begins, which entities become pages or blocks, which states need to be accounted for, and how a person moves from context to a decision.
The result is an interface that is easier to use, while its architecture is easier for the delivery team to understand and more resilient as the product evolves.
02.
Design system
Reusable patterns, components, principles, and documentation.
03.
Delivery
Testing, automation, builds, AI-assisted workflows, and a design system in code.
Work
Selected work
These projects are based on real product experience. Where source material cannot be shown directly, public-safe versions have been prepared: the brand, visual layer, and part of the context have been updated, while the task type, interface complexity, solution logic, and implementation approach remain intact.
Coastal Travel Marketplace
CoastKey is a redesign project grounded in a real product and the experience of working on it. The public NDA-safe version brings B2C/B2B scenarios and operational workspaces together in a React design system.
Startup speedTravel Marketplace
Enterprise Cloud Office
Designing a high-density enterprise interface for secure collaboration: document editors, protected content, access models, organizational roles, and a design system for the working environment.
Enterprise SaaSAccess Management
Digital Logistics Platform
UX architecture for a digital freight-forwarding operation: a web interface for internal roles, mobile scenarios for operators, and the lifecycle of requests, trips, checks, and documents.
LogisticsUX
Project Requirements Platform
Designing a decision-support tool for enterprise projects: a requirements repository, project workspaces, scoring, solution comparison, and reusable interface patterns.
Requirements ManagementDecision Support
In development
Financial Security System
A high-density interface for bank-security teams: incidents, data classification, operational staff scenarios, and a systematic UI approach for internal enterprise products.
Banking SecurityHigh-density UI
Digital Insurance Platform
A scalable insurtech platform for internal and customer-facing scenarios: enterprise workspaces, one design system, and no-code tools for configuring calculations and business logic.
InsurtechBigTech
Recruiting Platform
A two-sided recruiting platform for employers and candidates: job posting, job search, a resume builder, and interface scenarios for AI-assisted resume analysis.
HRTechResume Builder
NDA
Public-safe
Many projects are connected to real products, teams, and internal materials, so they cannot be shown directly because of NDA restrictions and limits on public disclosure.
For the portfolio, public-safe versions have been prepared: the brand, visual layer, presentation, and part of the product context have been updated, while the task type, solution logic, interface complexity, and system-oriented approach have been preserved.
This format makes it possible to show not client materials, but the way of working with product logic, UX architecture, design systems, and preparation of interfaces for implementation.
Design Engineering
Interface System
01.
Product logic
Roles, scenarios, data, states, constraints, and decisions that determine how the product behaves.
02.
Design
Information architecture, user flows, screen families, and relationships between the main parts of the interface.
03.
Component system
Reusable patterns, states, UI contracts, and rules that preserve interface coherence as a product grows.
04.
Implementation readiness
Documentation, review, handoff, quality control, and the conditions that let a solution be implemented without losing its logic.
component-audit.tslayout-contract.tshandoff.md
AI-assisted workflow
AI as Part of a Managed Process
Process
From Task to Solution
01.
Component boundaries
Components do not exist in isolation inside screens. Each element has a role, a level of responsibility, and a clear place in the system.
02.
UI contracts
States, variants, properties, and usage rules are defined so the component is understandable to design, engineering, and product teams.
03.
Documentation and review surfaces
A design system needs to be inspectable: components, states, layouts, and scenarios can be reviewed in reference surfaces and a runtime environment.
04.
Validation and implementation quality
Tests, checks, handoff, and change control help preserve consistency as the product grows and new scenarios appear.
Design remains a core responsibility, even in smaller projects
Automation speeds up the work, but product logic, component boundaries, and quality control must remain deliberate team decisions.
Resilient interface architecture, consistent patterns, and predictable outcomes are what distinguish a system from a collection of screens.
Design Systems Evolve with Code
First, the product logic is understood. Then come structure, the system, the visual layer, concepts, and ideas—all built on a shared foundation. The interface develops as part of a durable product process.
A design system evolves with both the product and the codebase. It has rules, owners, checks, and a change lifecycle.
This approach is especially useful for B2B, B2C, and enterprise products, where the interface must absorb growth: new roles, scenarios, data types, states, implementation constraints, and public or private material boundaries.
tokens.jsonbutton.tsx
I work with complex B2B, B2C, and enterprise products as well as websites, landing pages, MVPs, internal tools, and interface redesigns.
The format follows the problem: from UX architecture and design systems to website structure and implementation preparation. I audit interfaces and workflows, then turn findings into recommendations, priorities, and a practical next-step plan.
I can also establish an appropriate private-data workflow, shape the delivery process around the project, and carry implementation through to a finished interface, website, or another technical outcome.
