Frontend developer who treats interfaces like architecture
Ten years of shipping production frontends — architecture that compounds, performance you can measure, end-to-end ownership from greenfield through maintenance.
- > location:
- Rzeszów, PL (UTC+1)
- > status:
- available for select work
- > current:
- Lead Frontend @ Chaiz
- > focus:
- architecture · performance · end-to-end DX
Selected work.
-
CyclingHero
CyclingHero: Bike Tours and Cycling Trips in Italy
Custom bike tours through the Dolomites, Veneto, and Tuscany — itineraries built around the rider, with the logistics quietly handled in the background.
-
Murako
Murako: architecture studio, Rzeszów
Marketing site for an architecture studio that designs houses people actually want to live in — built on Astro with a Keystatic Cloud editorial workflow.
-
Sumo App
Real-time sumo tournament tracker — live SSE updates, command-palette navigation, hand-prompted sumi-e illustrations
Live basho standings, wrestler profiles, and a build-time pipeline of sumi-e ink illustrations — because if you're going to learn about sumo, you might as well do it properly.
> whoami
Most of my work happens at the intersection of architecture and shipping — setting up the patterns, toolchains, and mental models that let a team move fast without creating technical debt. I'm at my best when a problem mixes domain complexity (multi-tenant SaaS, multi-language, regulated flows) with frontend craft (design systems, micro-interactions, accessibility).
Frontend Architect with 10+ years building production web applications, leading frontend teams up to nine engineers, and shipping the architectural patterns and performance wins that compound for years. Comfortable owning the full architecture from greenfield setup through migrations and developer-experience overhauls — release cycles cut from weeks to days, monorepos that ship one TypeScript codebase across iOS, Android, and web, page weight reduced by two-thirds where it counted. Happiest where domain complexity meets frontend craft.
Outside the editor I read more architecture monographs than I should, attempt (badly) to learn Japanese, and keep a running list of architectural decisions that bit me at least twice — partly so I don't repeat them, mostly because the list is genuinely funny.
- location:
- Rzeszów, PL (UTC+1)
- stack:
- TypeScript, React, Tailwind, Bun
- editor:
- Zed
- drinking:
- Brasil, Aeropress, inverted, no sugar
Selected milestones.
- 2025
Lead Frontend Developer
@ Chaiz
Reworked release cycle from biweekly to continuous · Tailwind adoption (+50% velocity)
- 2021
Frontend Technology Lead
@ spaceOS
12-language localisation system · 9-person FE team · deploy time 1 week → 2 days
- 2018
Senior Frontend Developer
@ Neti-Soft
jQuery → Angular migration · mobile-first practice introduced to the team · self-organised delivery
- 2014
Software Developer
@ Petrosoft.pl
Where the timeline starts.
What I ship.
-
Frontend architecture
The patterns and toolchains that let a team ship fast for years, not just sprints. Greenfield setup, monorepo plumbing, migration plans for legacy stacks — the work that compounds quietly in the background.
-
Performance & Core Web Vitals
Audits that come back with a fix list, not a slide deck. INP and LCP that move, font and image pipelines that hold, RUM telling you when something regresses — numbers a stakeholder will actually read.
-
Design-system-driven development
Figma to production with the seams hidden. Tokenised in Tailwind (or whichever stack the team runs on), documented in Storybook, kept honest by Chromatic and contract tests — so the design system holds up after the launch.
-
Team leadership & mentoring
Led teams up to 9. Hire, calibrate, mentor, set the bar — then shorten the path from spec to merged PR without lowering it.
The terminal is still open.
I'm currently open to collaborations on greenfield architecture, performance work, highly synchronised design systems, or anything involving meaningful complexity. The shorter the deck, the better.