SaaS and operational UI
Multi-step workflows, administration surfaces and customer portals that keep complex actions understandable.
Senior React delivery for product teams
I design and build production React interfaces for teams that have moved beyond simple screens. That includes dense workflows, shared component systems, data-heavy views and frontends that need careful rescue rather than another patch.
React product engineering
The work starts with product behaviour and information structure, then chooses the simplest React architecture that will support it.
Multi-step workflows, administration surfaces and customer portals that keep complex actions understandable.
Reusable patterns and design-system foundations that improve consistency without creating an abstract component maze.
Tables, filters, search, permissions and asynchronous states made fast and predictable across real user journeys.
Routing, state boundaries and feature structure reorganised so teams can change one area without breaking another.
Keyboard behaviour, semantic structure and responsive layouts treated as core product quality rather than late fixes.
Unnecessary renders, slow screens and costly bundles investigated with profiling before targeted improvements are made.
Frontend delivery options
A new interface, an overloaded roadmap and a troubled codebase need different kinds of ownership.
A customer-facing workflow, portal or application area designed and delivered as a complete frontend outcome.
Senior React ownership added to an established team for roadmap delivery and technical decision-making.
Focused work on a frontend where regressions, performance or architecture are preventing confident releases.
Product fit
I am most useful when I can collaborate across those boundaries instead of receiving screenshots with the difficult states left unspecified.
International client experience
I have worked directly with clients in the United States, Canada, the United Kingdom, Germany and other international markets. For roughly the past six years, most of my client work has been with US-based businesses—across time zones, established team workflows and direct stakeholder communication.
Selected React work
Examples of React used as part of complete applications rather than isolated component demos.
The ESG Rating application helps users efficiently fill out questionnaires, and the Croatian Chamber of Economy (CCE) to collect, process, evaluate and rank ESG-related…
View project
BatonAI is an AI coding agent that can Orchestrate a team of AI software engineers to create enterprise-quality software faster and more efficiently.
View project
Frontend toolkit
React engagement details
Framework choice is only one part of delivery, so the first conversation also covers design, APIs, release ownership and existing constraints.
Yes. I translate the design into responsive states and reusable components, while raising missing behaviours, accessibility issues and technical edge cases before they become rework.
Yes. I choose rendering and routing patterns around the product, performance and hosting requirements rather than treating Next.js as mandatory for every React application.
Yes. This is a common fit: I can own React implementation, agree API contracts with backend developers and make frontend trade-offs visible to product and design.
Yes. I begin with the most repeated and risky interaction patterns, then consolidate them without forcing the entire interface into a disruptive redesign.
Yes. I focus automated coverage on business-critical behaviour and use browser-level testing where integration between UI, routing and APIs carries the real risk.
Yes. For a complex or inherited frontend, a bounded review can produce an implementation plan and confirm whether a larger engagement is sensible.
Bring the difficult user flow
Share the interface, designs or codebase and explain what users need to accomplish. I will suggest a focused first step based on the state of the product.