Angular architecture that stays understandable
Component APIs, shared libraries and Nx monorepos with explicit ownership of state and behavior. I focus on changes teams can reason about, review and test.
Explore the library source and tests ↗Kamil Furtak / Senior Angular Engineer
Angular expertise.
Built for complex products.
I build reusable Angular libraries, map-based interfaces and frontends that can evolve without losing what already works. If that sounds like your team's next challenge, let's talk.
01 / Where I can help
Complex interfaces.
Clear responsibilities.
Maps that belong in the product
OpenLayers integration, coordinate projections, drawing, selection and editing workflows. My library examples make these interactions available to inspect and try.
Try 27 interactive map examples ↗UI modernization with continuity
Move established interfaces forward in manageable steps. Preserve filters, selection and unfinished edits while making room for new components and clearer application boundaries.
Try the independent migration workbench ↗02 / Evidence you can explore
Start with the work.
Then start a conversation.
Maintained open source
ng-openlayers
A published Angular/OpenLayers wrapper. My maintainer work includes lifecycle ownership, projection changes and checking the package in an independent Angular application.
Read the project overview ↗Independent architecture case study
Integration boundaries
A public walkthrough of browser/API boundaries, generated contracts and failure modes around identity integration. It explains the engineering decisions using independent portfolio material.
Explore the case study ↗Also contributed accepted changes to bolt.diy and Hindsight. The pull requests show the implementation and upstream review.
03 / How I work
Hands-on delivery.
Decisions you can follow.
I start with existing behavior, integration boundaries and the constraints the team has to live with. Then I look for the smallest useful change that makes the next one easier.
- Make ownership explicit. Keep domain state, rendering and external integrations understandable.
- Check the real workflow. Use regression tests, browser checks and package-consumer validation where they matter.
- Leave a usable trail. Document the decision, its tradeoffs and how to verify it.
I use AI tools for implementation and investigation, with source review and verification. My public samples identify their scope and the evidence behind them.
Engineering review guide ↗Let's talk
Building something
in this space?
Tell me about the product, the frontend challenge and the role you have in mind. For my employment history and background, download the CV.