ENTERPRISE
Maintenance applications
Reusable frontend architecture for enterprise maintenance workflows.Reusable architecture for specialist workflows.
React · TypeScript
Karel Kutchan / SENIOR FRONTEND ENGINEER / PRAGUE
I build frontend systems for products that have to last.
More than ten years in web development, currently in a lead frontend role. I work with React, TypeScript and Next.js across customer portals, internal enterprise applications and the component libraries underneath them.More than ten years in web development, currently in a lead frontend role. I work with React, TypeScript and Next.js across customer portals, enterprise applications and component systems.
Architecture, accessibility and long-term maintainability are part of the delivery, not follow-up work.Architecture, accessibility and maintainability are part of the delivery.
Lead Frontend Engineer at BlueGhost. Open to senior and lead frontend roles in Prague or remote (EU), employee or contract.
WORKED WITH
FLAGSHIP CASE / ENERGY
A customer portal built as a system, not a collection of screens.A customer portal built as a system.
Frontend leadership for a customer-facing energy product: architecture, component foundations, delivery quality and accessibility across a growing application.Frontend leadership for a customer-facing product and the component foundations beneath it.
React · TypeScript · Next.js · Storybook · Playwright
PRODUCT UI
Customer journeys
Shared components
Accessible foundations · Tests · Delivery
SELECTED WORK
Complex products. Clear frontend decisions.
- Read case
- Read case
ENERGY PLATFORM
Distributed energy platform
Frontend foundations for a complex distributed-energy product.Frontend foundations for an evolving energy product.
React · TypeScript
- Case study coming soon
ACCESSIBILITY
Accessibility refactoring
Practical accessibility improvements inside an established product.Inclusive behavior inside an established product.
React · TypeScript
HOW I WORK
Senior engineering is mostly about making good decisions repeatable.Good decisions should be repeatable.
Architecture with a reason
Choose boundaries and patterns that reduce product risk.Reduce product risk.
Accessibility by default
Build inclusive behavior into components and reviews.Build inclusion into components.
Quality that supports delivery
Use tests, tooling and feedback where they protect change.Protect the changes that matter.
Leadership through clarity
Make trade-offs visible and help teams move with confidence.Make trade-offs visible.