I am Maciej Kankowski, an independent frontend tech lead. For 10+ years I have delivered enterprise platforms on fixed-scope B2B contracts: technical direction, legacy modernisation, and AI-native workflows that change how a team actually ships.
Leading a six-person frontend chapter in a 40+ engineer program: five apps (component library included) on React 19, Vite and Node 22, release master of the train, and a governed AI workflow the whole team ships with. Under contract with Jit Team. Details.
Four situations I have been contracted to fix. If one of them is your quarter, we should talk.
Every release costs more than the last, coverage is thin, nobody touches the oldest modules, and a rewrite is off the table: modernisation has to happen in production.
Six capable engineers pulling the architecture six ways. Decisions happen inside pull requests, and the same debate returns every sprint.
Everyone has a licence and prompts differently, none of it shows in the release process, and the gain cannot be measured.
Deploys are rare because they are risky, and risky because they are rare. Fixing that loop is usually worth more than any feature on the board.
Fourteen months on one program: what I found, what I changed, what came of it. All four situations above in one place, and the fastest way to judge the fit.
Enterprise workforce-management platform for a global HR and staffing business: five frontend apps, a shared component library among them, built by a program of about 46 people on a monthly release train. Under contract with Jit Team; the end client is withheld under NDA.
Joined. Design-system groundwork and features in the talent app.
Feature flags, release automation, and Release 5.0 across four apps with onboarding as a reusable micro-frontend.
Component library kick-off, Medallia in the main app, Copilot to Claude Code, my first release as release master.
Component library published, a written release process, the four-app migration in production in June.
GlobalLink Strings (then Applanga) integrated. New planning module.
Renovate, automatic Zod validation, the UX process, a redesign roadmap and the team reorganised around it.
Leading the redesign of the entire app.
Four ways to contract me. Each one has a defined deliverable, agreed milestones and an end date.
A contracted mandate to set technical direction and unblock delivery. Term, milestones and acceptance criteria fixed before the first commit.
Turn a long-lived, hard-to-change product into a maintainable, component-driven stack, as a phased migration rather than a freeze.
Multi-agent and AI-assisted workflows across the SDLC, built into the pipeline instead of into individual editors.
A clear-eyed review of architecture, performance, testing and release process, delivered as a prioritised action plan with no filler.
All four are contracted and invoiced by mackan.it Maciej Kankowski on B2B terms: my own equipment and software, no exclusivity, several clients in parallel, including the website clients of my studio. Full engagement terms.
No surprises after the signature. The scope is written down before anything starts.
What is slow, what is at risk, and what "done" would look like for you.
I write the scope, the milestones and the acceptance criteria. You approve them before work starts.
I work in your repository and your process, reporting against the milestones we agreed.
Documentation, patterns and pipelines stay with your team. The engagement has an end date.
Also under contract with Jit Team, a Gdynia consultancy that places specialist contractors with international clients. End clients are generalised by industry under NDA.
Cloud-native web client for an EMEA-wide stock-transfer platform with AI-assisted load recommendations. I owned end-to-end testing for the product.
Led a small team taking a health web app and a native iOS app with wearable data from MVP to production. Owned iOS releases, from version tags to app signing, and builds and deploys on the team's existing AWS setup.
Two years modernising a security-critical financial system. Design-system-aligned work seeded three new products; as Scrum Master I guarded releases and drove frontend performance.
Greenfield internal platform with map-based 3D visualisations. First engineer on the account; helped grow it to about five workstreams and twenty people, leading interactive UI and UX prototyping.
Earlier: native mobile apps (iOS in Swift, Android in Kotlin) and full-stack web. Useful context; the work above is where I focus today.
Beyond autocomplete. I design the system around the model, so it behaves like a reliable teammate inside a real delivery pipeline.
Agents for planning, implementation, review and test hand work off, with humans in the loop where it matters.
Generation, refactoring and review wired into branching, CI and release, not bolted on.
Agents map, document and incrementally modernise a large, long-lived codebase without freezing delivery.
Patterns, guardrails and review culture so a whole team adopts AI safely, covering the EU AI Act's AI-literacy duty (Art. 4). Raising the floor, not just the ceiling.
What I bring to a contract, and where the edges of it are.
One page, kept current. Frontend tech lead, 10+ years, enterprise platforms across five sectors. The web version reads better on a phone.
The short answers. Anything else goes in the email.
Run a local business rather than an engineering program? That work goes through my studio: fast, mobile-first, SEO-ready business sites in Polish or English, with design, copy, launch, domain, SSL and hosting handled end to end. Over 8 business sites live.
