Maciej Kankowski Available · B2B· Gdynia, PL Email me
Frontend tech lead Independent contractor, B2B Gdynia, Poland · remote

Enterprise frontend,modernised withoutpausing delivery.

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.

● Right now

Leading a six-person frontend chapter inside a 40+ engineer program. This year: five frontend apps, component library included, brought onto React 19, Vite and Node 22, a release train I run as release master, and a governed AI workflow the whole team ships with. Under contract with Jit Team. The full breakdown.

Maciej Kankowski, independent frontend tech lead
Fig. 01M. Kankowski
  • 10+
    Years delivering enterprise web platforms
  • 6
    Frontend engineers under my technical direction
  • 40+
    Engineer program I work inside today
  • 5
    Sectors shipped in: HR, logistics, energy, finance, health
01 / Where I help

Where I am usually called in

Four situations I have been contracted to fix. If one of them is your quarter, we are talking about the same problem.

  • 01

    A product that got old while you were shipping it

    Every release costs more than the last one, coverage is thin, and nobody volunteers to touch the oldest modules. The rewrite branch is not an option, so modernisation has to happen on a system that stays in production.

  • 02

    A workstream without technical direction

    Six capable engineers pulling the architecture in six directions. Decisions get made inside pull requests instead of before them, and the same discussion reappears every sprint.

  • 03

    AI adopted per person, not per team

    Everyone has a licence, everyone prompts differently, and none of it is visible in the release process. The output is uneven and the gain is impossible to measure.

  • 04

    A release process people are afraid of

    Deploys are rare because they are risky, and they stay risky because they are rare. Fixing the loop is usually worth more than any single feature on the board.

02 / Now

Current engagement

Fourteen months on one program, in detail: what I found, what I changed and what came of it. All four situations above, in one place. The fastest way to judge the fit.

Active Aug 2025 – present · B2B, rolling scope

Frontend Tech Lead

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.

React 19TypeScriptViteVitestNode 22ExpressMUIStorybookZodPlaywrightGitLab CIJenkinsDockerRenovateMedalliaGlobalLink StringsClaude Code
5 appson React 19, Vite, Node 22, component library included
Renovatedependency updates run as a process, not a monthly clean-up
Library + UXshared component library and a UX process, launched
1 form engineonboarding rebuilt as a micro-frontend, reused across apps
Starting point
Four apps on an ageing stack (Create React App, React 17–18, Node 16–18) with dependencies updated by hand. No shared component library and no UX process. Releases assembled by hand. AI used per person, with no shared rules.
Direction
Lead a frontend chapter of six engineers and a designer across four product teams: backlog, cross-team reporting and capacity planning. In September I reorganised the team around the roadmap.
Modernisation
Brought all five frontend apps onto React 19, Vite, TypeScript and Node 22: the four existing apps migrated without pausing feature delivery, sequenced by risk and shipped as a release of its own in June 2026, and the new component library built on the same stack.
Micro-frontend
Led the rebuild of candidate onboarding as a reusable form engine embedded as a micro-frontend, replacing a second copy of the form that had been drifting apart. I raised it in my second week and chose to embed it in the apps we already ran rather than adopt a new framework. The senior engineer designed and built the engine; I set the direction, reviewed the integration contract, ran the release and own the security of the embedded surface. In production in six weeks over Christmas, and reused by a second app two months later.
Library and UX
Launched the shared component library and a UX process with our designer, so new features are designed and approved before they are built.
In progress
Leading the redesign of the entire app onto the new design system: the roadmap, the design process and the component library are in place, and the migration runs module by module alongside feature work.
Release
Release master for six monthly trains and eight hotfixes for about 40 developers. Replaced hand-assembled releases with a documented, feature-flag-first process and blameless post-mortems.
Security
Security headers on every app, scan findings closed, and a security audit of the whole frontend estate turned into prioritised work the client could plan.
Dependencies
Dependency upkeep moved from manual clean-ups to an automated Renovate process: small updates flow in on their own, major ones get a review.
API contracts
Automatic Zod validation of API responses, with schemas generated from the backend's API spec, so the frontend always checks against the current contract.
Customer experience
Brought in Medallia for in-app feedback and digital-experience analytics.
Localisation
Brought in GlobalLink Strings (formerly Applanga) for translations, from vendor analysis and the client decision to a working integration.
AI-native
Moved the team from per-person Copilot to Claude Code, policy first: AI-usage principles reviewed by compliance and cybersecurity, then a shared team setup with guardrails and commands that encode how the team works.
Quality
A regression suite, a test strategy centred on API contracts, and a nightly audit that gives every failing end-to-end test an owner.
Developer experience
A local environment that runs all four frontends and a setup that lets engineers work on several branches in parallel.
Hands-on
Still writing production code while leading: I built the core of the new planning module and made it fast enough for real planning data.

Fourteen months, in order

  1. Aug–Oct 2025

    Joined. Design-system groundwork and features in the talent app.

  2. Nov 2025–Jan 2026

    Feature flags and release automation. Release 5.0 across four apps, with onboarding rebuilt as a reusable micro-frontend.

  3. Feb–Mar 2026

    Component library kick-off. Medallia in the main app. The team moves from Copilot to Claude Code. My first release as release master.

  4. Apr–Jun 2026

    Component library published. A written release process. The four-app migration, in production in June.

  5. Jul 2026

    GlobalLink Strings (then Applanga) integrated. New planning module.

  6. Aug–Sep 2026

    Dependency updates on Renovate. Automatic Zod validation. UX process launched. Redesign roadmap, and the team reorganised around it.

  7. Now

    Leading the redesign of the entire app.

03 / Engagements

What you get

Four ways to contract me. Each one has a defined deliverable, agreed milestones and an end date.

Fractional lead01

Interim frontend tech lead

A contracted mandate to set technical direction and unblock delivery. Term, milestones and acceptance criteria fixed before the first commit.

  • Architecture decisions written down, not held in one head
  • A workstream that can decide without me
  • Reporting against the milestones we agreed
Modernisation02

Legacy to modern React and Node

Turn a long-lived, hard-to-change product into a maintainable, component-driven stack, as a phased migration rather than a freeze.

  • A migration plan with phases you can stop at
  • Component-driven architecture your team owns
  • Delivery continues while the migration runs
AI-native03

AI-native team enablement

Multi-agent and AI-assisted workflows across the SDLC, built into the pipeline instead of into individual editors.

  • Working pipelines, not a workshop deck
  • Guardrails that keep output reviewable
  • Documentation and handover to your team
Audit04

Frontend and delivery audit

A clear-eyed review of architecture, performance, testing and release process, delivered as a prioritised action plan with no filler.

  • Findings ranked by what they cost you
  • A plan your team can execute without me
  • Fixed price, fixed duration

All four are contracted and invoiced by mackan.it Maciej Kankowski on B2B terms. I supply my own equipment and software, take no exclusivity and run several clients in parallel, including the website clients of my studio. Full engagement terms.

04 / Earlier work

Earlier work

Before the current engagement. Delivered under contract with Jit Team, a Gdynia software-engineering consultancy that places specialist contractors with international clients. End clients are generalised by industry under NDA.

2022–2025 Logistics · EMEA

Global logistics control tower

Cloud-native web client for a stock-transfer platform spanning the entire EMEA region, including AI-assisted load recommendations. I owned end-to-end testing for the product.

Vue.jsTypeScriptAWS LambdaPlaywrightCypressFigma
~40%fewer defects
~€60k/mounlocked
~1.5h/daysaved in planning
2021–2022 Health · Wearables

Digital health and wearables platform

Led a small team delivering a health-sector web application and a native iOS app integrating wearable health data, taking them from MVP to production. Owned the iOS release process, from version tags to app signing, and ran builds and deployments on the team's existing AWS setup.

Next.jsReactNative iOSAWS EKS
MVP → prodled the team through it
2020–2021 Finance

Bond and debt-documentation platform

Modernised a security-critical financial system over roughly two years. Design-system-aligned work seeded three new products, and I guarded the release process as Scrum Master while driving frontend performance.

ReactTypeScript.NET Core
3new products seeded
~2 yrmodernisation
2019–2020 Energy

District-heating infrastructure platform

Greenfield internal platform with map-based 3D visualisations. I joined as the first engineer on the account and helped grow it into roughly five parallel workstreams and about twenty people, leading interactive UI and UX prototyping.

ReactTypeScript3D / map
1stengineer on the account
~20people at peak

Earlier in my career I also shipped native mobile apps (iOS with Swift, Android with Kotlin) and full-stack web. Useful context, but the work above is where I focus today.

05 / AI-native

AI-native engineering

Beyond autocomplete. I design the system around the model, so it behaves like a reliable teammate inside a real delivery pipeline.

  1. AgentPlan
    ● Human approves
  2. AgentImplement
  3. AgentReview
    ● Human reviews
  4. AgentTest
  5. PipelineCI and release
/ 01

Multi-agent workflows

Specialised agents for planning, implementation, review and test that hand work off to each other and keep humans in the loop where it matters.

/ 02

AI in the SDLC

Generation, refactoring and code review wired into branching, CI and the release process, not bolted on after the fact.

/ 03

Legacy, accelerated

Agentic tooling used to map, document and incrementally modernise a large, long-lived codebase without freezing delivery.

/ 04

Team enablement

The patterns, guardrails and review culture that let a whole team adopt AI safely and consistently, and that cover the AI-literacy duty the EU AI Act (Art. 4) puts on every company using AI. Raising the floor, not just the ceiling.

06 / Process

How an engagement runs

No surprises after the signature. The scope is written down before anything starts.

  1. A call

    What is slow, what is at risk, and what "done" would look like for you.

  2. Scope and milestones

    I write the scope, the milestones and the acceptance criteria. You approve them before work starts.

  3. Delivery

    I work in your repository and your process, reporting against the milestones we agreed.

  4. Handover

    Documentation, patterns and pipelines stay with your team. The engagement has an end date.

07 / Stack

Capabilities and credentials

What I bring to a contract, and where the edges of it are.

Leadership
Technical direction · delivery and release management · delivery metrics and reporting · architecture · mentoring and training · business analysis
AI engineering
Multi-agent workflows · AI-assisted delivery · agentic SDLC · Claude Code · AI-usage policy and guardrails
Frontend
React · Next.js · Vue.js · TypeScript · Vite · Vitest · JavaScript ES6+ · design-system component libraries · micro-frontends · accessibility
Backend, quality
Node.js · REST APIs · CI/CD with GitHub Actions and GitLab CI · Playwright · Cypress · release engineering · CSP, dependency and container hygiene
Design
Figma · Claude Design · design systems · UI and UX prototyping · design to code handoff
Cloud
AWS with simple configurations · AWS Lambda · Docker and Kubernetes basics (working knowledge, not deep infrastructure work)
Languages
Polish (native) · English (B2)
Education
Gdańsk University of Technology · Gdynia Maritime University
08 / Résumé

CV.

One page, kept current. Frontend tech lead, 10+ years, enterprise platforms across five sectors. The web version reads better on a phone.

Your browser will not display the PDF inline.

Open the PDF

09 / FAQ

Questions before the first call

The short answers. Anything else goes in the email.

Who is Maciej Kankowski?
An independent frontend engineer and tech lead based in Gdynia, Poland, with 10+ years building enterprise web platforms. I run my own engineering practice, mackan.it Maciej Kankowski, and take fixed-scope B2B contracts covering technical direction, legacy modernisation and AI-native engineering workflows.
Are you available for new contracts?
Yes. I take on new contracts and run several clients in parallel, including the website clients of my studio. The fastest way to reach me is email.
How do you contract?
B2B, through my own registered business, mackan.it Maciej Kankowski, NIP 5882448371. Every engagement has a defined scope, agreed milestones and an end date. I supply my own equipment and software, take no exclusivity, run several clients in parallel, including the website clients of my studio, and carry responsibility for the result of my work. Full engagement terms.
Is a B2B contract with you affected by the 2026 labour-inspection reform?
Since 8 July 2026 a Polish labour inspector can decide that a B2B contract is in fact employment, and the test is how the work is actually done (Art. 22 of the Labour Code), not what the contract is called. My engagements are built on the factors that test looks at: a defined scope and an end date, payment for accepted results, my own equipment and software, my own choice of method, working time and place, no exclusivity, and liability for my own defects. The engagement terms set it out point by point.
What technologies do you work with?
My core stack is React, Next.js, Vue.js, TypeScript and Node.js, with CI/CD and Playwright or Cypress for end-to-end testing, plus design work in Figma and Claude Design. On the cloud side I am comfortable with simple AWS and Docker or Kubernetes configurations rather than deep infrastructure work.
What does AI-native engineering mean in practice?
Multi-agent workflows wired into the delivery pipeline rather than into individual editors: planning, implementation, review and test agents that hand work off, guardrails that keep the output reviewable, and documentation so the team keeps using them after I leave.
How does your work sit with the EU AI Act?
Engineering with AI tools is not a high-risk use under the AI Act, but it still carries duties, and I treat them as part of the job. Client code and data go only into AI tools that meet the client's security and confidentiality requirements, and every AI-assisted change is reviewed by a person before it ships. The enablement work covers the AI-literacy duty that every company using AI has carried since February 2025 (Art. 4): written principles, a shared setup and training. If an engagement touches a high-risk area such as recruitment or worker management, its classification is settled in writing before work starts. How I use AI is described in the engagement terms.
Do you also build websites for small businesses?
Yes, through my studio at studio.mackan.pl. Fast, mobile-first, SEO-ready business websites for local companies in Poland and abroad, in Polish or English, with design, copy, launch, domain, SSL and hosting handled end to end in fixed-scope packages.
10 / Contact

Let's talk about the contract

Email me

Available for frontend leadership, modernisation and AI-engineering contracts. The fastest way to reach me is email. Tell me what is slow and what your deadline is.

Second practice

Websites for small and local businesses

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.

studio.mackan.pl