Service 01
Production code and architecture decisions — not just tickets.
I've been writing Angular professionally since AngularJS days. That's not a boast — it means I've seen every migration, every paradigm shift, and every pattern that sounded brilliant at the time and aged badly. I know what good Angular looks like at scale.
At InPost I architect and build micro-frontend platforms that serve operations staff across Europe. That means real constraints: multiple teams, independent deployments, shared design systems, and the requirement that nothing breaks when one team ships at 2am on a Friday.
I work with components, yes — but I think in systems. Who owns what state? Where does data fetching live? How does this scale to ten teams? I make those calls, document them, and defend them in reviews.
Deliverables
How I work
Before writing a line, I understand the system. What exists, what the team has tried, where the actual pain is. A lot of frontend problems are organisational problems in disguise.
State management, data layer, routing, error boundaries — the boring infrastructure that makes everything else maintainable. I do this deliberately, not as an afterthought.
I pair, I review, I document. Good code that only one person understands is a liability. I leave codebases in better shape than I find them.
Bundle size, render performance, Lighthouse scores — I track what matters. Performance isn't a separate phase. It's a habit.
Tools & tech
Related work
FAQ
Ready to start?
Based in Poland, open to remote work across Europe and beyond. My inbox is genuinely friendly.