Welcome.

Rafał MikuckiLead Frontend Engineer

Frontend architecture, design systems, SDKs, and product engineering with end-to-end ownership from idea to production.

Discuss a role
Core technology stack:
  • React
  • TypeScript
  • Frontend architecture
  • Design systems

Profile

Lead Frontend Engineer
Warsaw, Poland

Engineering complex products from idea to production.

I am a frontend-focused product engineer with experience across SaaS, fintech, loyalty, Web3, developer platforms, and internal tools. I have led frontend architecture, hands-on product delivery, and teams of 10+ engineers while collaborating closely with product, design, backend, and client stakeholders.

React • TypeScript • Next.js • Frontend Architecture • Design Systems • SDKs • Product Engineering • Platform Engineering

Commercial experience
+10 years
Core frontend stack
React · Next.js · TypeScript
Former frontend team lead
10+ engineers

Tools I use

Selected work

Selected systems, products, and engineering challenges.

GitHub profile

My strongest work sits at the intersection of product engineering and technical complexity.

Snag Solutions loyalty program dashboard shown on a desktop monitor

Project 01 / 05

Snag Solutions

Live product

Onchain Loyalty Engine

A configurable platform for creating points, tiers, balances, rewards, and loyalty rules across wallets, applications, campaigns, and digital ecosystems.

Business challenge

Enable brands to launch tailored loyalty programs without rebuilding their product, while supporting self-service administration, headless experiences, and onchain activity.

Contribution

  • Owned frontend and backend delivery for a platform supporting 100+ brands across 15 networks and 50 loyalty mechanisms.
  • Rebuilt 2 GB CSV processing for millions of rows, cutting runs from hours to minutes and memory from 2+ GB to a few hundred MB.

Technologies

  • React
  • Next.js
  • NestJS
  • PostgreSQL
  • Redis
  • BullMQ
  • Web3
Visit live product
Agg Market prediction-market trading interface shown on a laptop

Project 02 / 05

Snag Solutions

Live product

Prediction Market Infrastructure

Developer infrastructure for launching differentiated prediction-market experiences with aggregated markets, flexible authentication, and reusable product components.

Business challenge

Turn fragmented markets and liquidity into one coherent product experience while keeping the integration layer modular enough for different brands and audiences.

Contribution

  • Led frontend architecture from early concept to a partner-ready platform, defining package boundaries and building four public packages plus nearly all major frontend surfaces.
  • Built a modular SDK for API logic, React state, reusable UI, and authentication, helping partners integrate in days rather than weeks.

Technologies

  • TypeScript
  • React
  • WebSockets
  • Polling
  • Storybook
  • Design systems
Visit live product
Mercedes-Benz Stock mobile vehicle discovery and leasing interfaces

Project 03 / 05

Silk Software House

Portfolio summary

Mercedes-Benz Stock

A vehicle-leasing application for finding immediately available cars, comparing inventory, and routing customer inquiries to an appropriate dealer.

Business challenge

Make a large vehicle inventory understandable through location-aware search, advanced filters, multiple result views, detailed specifications, and dealer-facing administration.

Contribution

  • Designed the complete UI and UX for the vehicle discovery and leasing experience.
  • Implemented the frontend end to end with a mobile-first responsive system and cross-browser support.
  • Integrated the frontend with backend services and owned Google Analytics conversion tracking.

Technologies

  • HTML
  • CSS
  • JavaScript
  • React
  • PHP
  • Google Analytics
Boson Protocol marketplace artwork shown on a laptop

Project 04 / 05

Boson Protocol

Public case study

Boson Marketplace

A decentralized marketplace where sellers and buyers can list, discover, trade, transfer, and redeem physical or phygital products as redeemable NFTs.

Business challenge

Translate wallet, protocol, marketplace, and real-world fulfilment flows into a coherent commerce experience for both sellers and buyers.

Contribution

  • Led frontend implementation in the early-stage team and contributed to the Node.js backend.
  • Owned product creation, listings, cart, checkout, disputes, and responsive delivery.
  • Integrated real-time communication and Web3 journeys across wallets, NFT ownership, and marketplace transactions.

Technologies

  • React
  • Node.js
  • Boson Protocol
  • Polygon
  • WalletConnect
  • IPFS
  • The Graph
  • XMTP
View case study
T-Mobile logo shown on a laptop for the integrated communication system case study

Project 05 / 05

Silk Software House

Portfolio summary

Integrated Communication System

A unified interface for managing telecommunications services and bringing mechanisms from multiple client systems into one consistent environment.

Business challenge

Make complex operational workflows easier to manage across IVR configuration, call groups, conference bridges, reporting, and inbound and outbound call plans.

Contribution

  • Defined the application architecture from the ground up and owned the complete frontend implementation.
  • Delivered most of the backend, connecting Apollo Client and Server through GraphQL with MongoDB persistence.
  • Integrated T-Mobile’s legacy SOAP API into a consistent set of application workflows.

Technologies

  • React
  • Redux
  • Node.js
  • Apollo GraphQL
  • SOAP
  • Redis
  • MongoDB

Selected client projects and product integrations

Standards

How I approach production engineering.

Strong frontend engineering is more than implementing screens. It means creating systems that remain understandable, resilient, accessible, and easy to change after the first release.

  1. Clarity before complexity

    Architecture, component boundaries, APIs, and code should make their intent clear before introducing abstraction or cleverness.

  2. Build for change

    Products evolve continuously, so I design frontend systems, contracts, and reusable components that can grow without forcing unnecessary rewrites.

  3. Reliability is part of the experience

    Loading, error, empty, responsive, accessibility, reduced-motion, and recovery states belong in the implementation from the beginning.

Method

From unclear problem to dependable release.

I work best when product thinking and engineering decisions happen together. The goal is not only to ship a feature, but to understand the problem, reduce risk, and leave the product easier to evolve.

Content note: My process adapts to the maturity of the product, team, and technical constraints.

  1. 01Shared context

    Understand

    Clarify the user problem, business goal, constraints, dependencies, and the outcome that would make the work successful.

  2. 02Clear direction

    Design the system

    Define the user flow, data requirements, component boundaries, API contracts, edge cases, and technical trade-offs before implementation.

  3. 03Production-ready feature

    Build and integrate

    Implement the feature with maintainable architecture, accessible interactions, resilient states, tests, and close collaboration across the team.

  4. 04Release confidence

    Validate and improve

    Review the real behavior across devices, monitor failures and performance, gather feedback, and improve the system after release.

Initialising

Rafał Mikucki · Lead Frontend Engineer