Maksym Kuzmitskyi
Frontend · React · TypeScript
I build software around complex interfaces, state and data. React and TypeScript are my main tools. Alongside frontend development and service integration, I also design AI-assisted workflows with useful repository context, focused checks and human review.
Kraków, Poland
Four selected projects showing different sides of my work: frontend architecture, shared UI, service integration and product development.
Procter & Gamble · via Luxoft / DXC
Frontend Architect / Tech Lead
I authored the frontend low-level design and helped deliver an internal promotion-planning application with linked spreadsheet editing, business-rule validation and a draggable campaign timeline.
React · TypeScript · Redux · REST APIs
Read case study: Procter & Gamble · via Luxoft / DXCHonda Canada · via Assembly Canada
Tech Lead Full Stack Developer
I reworked shared React components for brand-specific layouts, improved local state isolation and worked extensively with Cypress and Cucumber in a test-first workflow.
React · JavaScript / TypeScript · Node.js · Sitecore · Cypress · Cucumber
Read case study: Honda Canada · via Assembly CanadaMotorola Solutions
Full Stack Engineer → Frontend Team Lead / Technical Product Owner
I developed React and Node.js functionality with PostgreSQL-backed middleware, contributed to shared UI and accessibility, and later led frontend delivery for the corporate web platform.
React · Node.js · PostgreSQL · Storybook · Adobe AEM
Read case study: Motorola SolutionsLiberty Mutual Insurance
Senior Frontend Developer
I build React and TypeScript quoting and checkout flows connected to federated GraphQL services, with a focus on maintainable UI, service contracts and reliable delivery.
React · TypeScript · Node.js · GraphQL · CSS/SCSS · Playwright · AI/MCP
Read case study: Liberty Mutual InsuranceMost of my work sits where interfaces, application state and services meet. I care about how a feature behaves, where its data belongs and whether another engineer can understand the decisions behind it.
My experience includes hands-on development, frontend architecture and team leadership. Across enterprise applications, multi-brand websites and customer-facing journeys, I have worked on both the implementation and the structure that supports it. I also design AI-assisted workflows with clear context, checks and human decision points.
Writing the code is part of the work. I also care about the decisions around it: how state is owned, how failures are handled, how a change reaches production and what the next engineer needs to know. AI-assisted work follows the same engineering expectations.
I start with the required behavior, the existing code and the contracts between UI and services. I look for clear ownership of state and data, and an implementation that fits the system. A new feature does not automatically need a new abstraction.
Tests, type checking, accessibility and code review belong inside implementation. I pay attention to loading, error and recovery behavior as well as the happy path. At Honda Canada, writing Cypress and Cucumber tests before implementation was part of this practice. I use focused checks and human review for agent-assisted changes too.
A change has to work beyond a local development session. I consider integration points, configuration, dependencies and CI behavior, and support deployment and release work. My experience also includes working knowledge of AWS.
I make requirements and trade-offs explicit with product, design and backend colleagues. When a decision affects other engineers, I document why it fits the problem. For agent-assisted work, I maintain repository-specific instructions and session handoffs, check saved context against current sources, and make permitted actions and human decision points explicit.
Notes on frontend development, software design and the practical details of building applications.
Horizontal scaling multiplies connection pools, retries, and deployment overlap as well as capacity. The useful questions concern admission limits, health-check meaning, draining, and which state a replacement instance can actually recover.
A local build can accept a dependency change while a related service rejects its contract. The useful work is establishing the scope and freshness of the evidence, including when the original proposal should be closed rather than completed.
CloudFront, ALB, ECS, RDS, and an optional Redis layer are enough to explain a useful deployment. The less obvious work is controlling identity, cache behavior, outbound access, connection budgets, and the cost of keeping the system recoverable.
I share frontend news and the reasoning behind it throughout the day. Pick the language that feels natural to you.
Selected examples from my earlier work in web design and development.
If something in my work or writing connects with what you are building, I would be glad to hear from you. You can reach me about frontend engineering, service integration, AI-assisted development workflows, a project or an engineering role.
Best for quick questions
Check out my code
Tech discussions & updates
Frontend news & architecture
Новости фронтенда и мои комментарии
Kraków, Poland