Skip to content
Kamil Wierzbicki

Technology serving your business

Unlike many developers, I don't build solutions that only look good on my CV. I focus on results, here and now.

Illustration: scattered notes and pieces of an interface line up first into a plan, then into a finished online shop with whole-bean coffee and a cart.

"Nothing is impossible! There are only problems waiting for me to solve them."

Portrait: Kamil Wierzbicki, Front-End Developer / IT Architect (React/TypeScript/Next.js/Astro)

Kamil Wierzbicki

Front-End Developer / IT Architect

I specialize in TypeScript, React, Next.js and Astro, with a strong flair for cloud computing (AWS) and backend development. My approach is a full-system view. I combine excellent UX with a solid technical foundation, with a focus on security and performance. I build modern solutions: from web and mobile applications and websites to e-commerce and online platforms. For 9 years, I have worked with businesses and technical teams, taking responsibility for the quality and long-term stability of the products I deliver.

My tech stack

  • TypeScript
  • React
  • Next.js
  • Astro
  • AWS
CrownRoots

Full-System View

The willow in my logo is no accident. A spreading crown needs strong roots. Instead of focusing only on what you can see, I take care of the whole application ecosystem. I start with architecture and technology tailored to your goals, building the foundation that excellent UX grows from. As a result, technology becomes the driving force behind your success, not a source of unpredictable problems.

Architecture: what holds it all together

You can't see it, but everything depends on it: security, well-organized data and a plan for future growth. So a year from now, you add new features instead of rebuilding everything from scratch.

  • Lower maintenance costs
  • Secure, well-organized data
  • Growth without having to rebuild from scratch

Front-end: what your customers see

Performance, looks and ease of use. An interface that guides customers to their goal and works just as well on a phone as on a computer.

  • Higher conversion
  • Better visibility in search engines
  • A website accessible to every customer (WCAG 2.1)

Stability, lower risk, higher return

  1. Illustration: technology tailored to the company's needs (product development plan and priorities)

    Tailor-made technology

    The technology you invest in should be like a good suit, tailor-made. It should fit your company and the goal you want to achieve. That's why I build solutions around your real needs, not around my CV. I help you name and organize your needs, set priorities and turn them into a clear action plan. You get a development roadmap and a list of priorities that can be delivered step by step. This way, from day one you know what is being built and why, and everything supports how your company operates.

  2. Illustration: application quality and stability (tests, code reviews, predictable releases)

    Top quality

    I could talk about tests, code reviews and quality standards. I always take care of them, but for you only one thing matters. You want to finally be able to trust the technology you invest in. In practice, this means code written so it's easy to change, tests that guard against bugs and checking every change before it goes live. As a result, your website or application behaves predictably and won't let you down at a critical moment, for example during a big marketing campaign, a key sales period or Black Friday.

  3. Illustration: partnership and IT support when problems arise and after launch

    Real support

    Working together is about more than technology. It's also a relationship with a partner who understands your goals and tells you straight how things stand. I make sure that what we build genuinely supports your business. When a bug, a drop in performance or an outage comes up, I'm available. I help find the cause and fix it fast. Even after our engagement ends, you can count on support and advice whenever you need it.

  4. Illustration: process optimization and lower costs through technology

    Higher profit, lower costs

    When technology fits your company, you get a tool that supports your bottom line. I look for places where you lose time and money: slow processes, manual data entry, no automation of repetitive tasks, high costs of maintaining legacy code. I simplify your team's work and take repetitive tasks off their plate (automation, integrations), so everything runs faster and without mistakes. The result? Lower costs, shorter handling times and more room for your customers or for testing new ideas.

  5. Illustration: architecture ready to grow without rebuilding from scratch

    Built for the future

    When I design today, I think about tomorrow. Today you may not need an extensive solution, but in a year or two things will change. It might be a new market, a new feature or an integration with another system. That's why I plan so that the application meets current needs and leaves room to grow (clean code, a well-thought-out structure), without rebuilding everything from scratch. What does that give you? No more "small changes" that take months and block sales or marketing. Instead, you add new features step by step, with no downtime and no risk to stability. And ultimately: faster business growth and lower maintenance costs in the long run.

From IT technician to architect

9 years of growing responsibility: from the first landing pages to designing the architecture and building an application people trust with their most important data.

Education and courses

  • Master of Science in Computer ScienceCloud Computing · Warsaw School of Computer Science · 2024

  • Bachelor of Engineering in Computer ScienceInternet Engineering · Warsaw School of Computer Science · 2021

  • Architektura na FroncieTomasz Ducin, Maciej Aniserowicz · 2021

  • Architecting on AWSCertificate of Completion · 2019

  • Google Umiejętności Jutra: AI 3.0Google · 2026

Full CV · 9 years of experience
  1. 2017– 2019

    FOXKOMPUTER

    IT Technician

    Rollout of a new e-commerce store, product pages and landing pages built together with NVIDIA, Intel, AMD, ASUS, MSI and GIGABYTE.

    First steps as a Front-End Developer

  2. 2019– 2022

    POROWNEO.PL

    Junior → Front-End Developer → Team Leader

    A new motor insurance comparison platform, dedicated sales funnels, partner integrations and custom-built infrastructure monitoring. In the end, leading three teams.

    From junior to Team Leader

  3. 2022

    Allianz Polska

    Front-End Developer / Team Leader

    An insurance risk assessment application, leading the team and standing in for the Delivery Manager.

    Team leader

  4. 2022– 2025

    artgeist

    Front-End Developer → Tech Lead

    An engine for an e-commerce store selling in 13 markets, a company website with a CMS for HR, an ERP migration and team mentoring.

    One e-commerce store in 13 markets

  5. 2023– today

    Safe & Trust

    IT Architect / Lead Front-End Engineer

    Design and development of an app with end-to-end encryption and Blockchain records, then a hybrid iOS and Android app built on it. Co-design of the architecture of the whole ecosystem.

    A hybrid app with E2E encryption

Skills and experience

Also in my daily work

  • JavaScript
  • Node.js
  • React Native
  • Vite
  • Vitest
  • Jest
  • Playwright
  • Cypress
  • Testing Library
  • TanStack Query
  • Redux
  • Tailwind CSS
  • Material UI
  • CSS / SASS
  • Docker
  • Terraform
  • CI/CD
  • Capacitor
  • AI: Claude Code, Cursor, Copilot

Since 2020

TypeScript

I spent a lot of time with JavaScript, but I missed predictability and confidence in what I was building. That's why I've been working with TypeScript since 2020 (starting with version 3.9), which gives me better control over the project, more stable applications and easier maintenance. In practice, this means fewer bugs after releases, lower maintenance costs (bugs are caught earlier) and easier onboarding of new people to the project. I refined my approach to typing and front-end architecture in the "Architektura na Froncie (ANF)" front-end architecture course. Thanks to that, my code is clear and easy to extend.

Since 2019

React

I started with React in 2019 and have been working with it consistently ever since, commercially for over 7 years. I know its strengths and common pitfalls, which lets me build stable, high-performance applications. Today I use React to build: web applications (team tools, admin dashboards), fast online stores and classic company websites. When does React make sense? When you need interactivity, dynamic elements or a cross-platform interface (web + mobile).

Since 2020

Next.js

I first came across Next.js in 2020 and saw it as a technology that would greatly strengthen the React ecosystem. Back then I leaned more toward Gatsby, but Next.js evolved faster and today offers a full stack (frontend + backend in one). When is Next.js the best choice? When you need strong Google rankings (server-side rendering, SSR), fast landing pages, an online store or an application with payments and APIs. Today Next.js is my first choice for projects that require high performance, scalability and integration with CMS platforms (Strapi, Payload).

Since 2025

Astro

Astro is a fresh approach to front-end development, built on solid foundations and sound architectural principles. In many projects it's a simpler alternative to Next.js for me, especially when performance and fast delivery matter. I've been working with Astro since 2025, and I built this website with it. When does Astro make sense? For content-heavy websites (blogs, documentation, portfolios, company websites), where loading speed and good Google rankings are the priority. I see it as a competitor to Next.js with real potential for building stable, high-performance solutions with low maintenance costs.

Master's 2024

Cloud computing

I'm not "just" a developer. I like to understand how the whole system works, from the front end through the API to the infrastructure. That's why in 2024 I completed a master's degree in Cloud Computing at the Warsaw School of Computer Science. I learned in depth how the clouds of the leading providers work: Amazon Web Services (AWS), Google Cloud Platform (GCP), Microsoft Azure. What does that mean in practice? I can design cloud infrastructure that is stable, secure and fits the budget. I choose the right services (servers, databases, serverless), automate deployments and monitor costs. As a result, the frontend and backend run in a stable, cost-effective environment that is easy to grow.

Since my first project

Architecture

Since my first project, I've looked beyond the application I'm working on. To me, architecture is not just choosing technologies, but also designing processes and data structures and making conscious trade-offs between business goals and technical constraints. That's why I design solutions tailored to the client's needs, while relying on proven mechanisms and patterns that make future development and maintenance easier.

Let's work together

Building a new application or growing an existing one? I combine technical expertise with business thinking. I speak plainly, help you make decisions and take responsibility for delivering them, instead of just following instructions.

I help build and grow products, streamline processes and reduce the risk of costly mistakes. From architecture, through implementation, to long-term maintenance.