Warsaw, Poland52.23°N 21.01°E

Tomasz Flis

Fullstack Developer

Over a decade of building web applications for healthcare, government and HR teams — mostly Angular and TypeScript, at the point where frontend architecture meets the people who have to maintain it.

Experience
12+years
Teams
6companies
Current
LeadSoftware Smith
Scroll
01

Building things for the web since 2013

Tomasz Flis

A passionate software developer with over a decade of experience building web applications that make a difference. My journey in technology began with a fascination for how the internet connects people and ideas.

Today, I focus on creating intuitive, high-performance web experiences using cutting-edge technologies. When I'm not coding, you can find me playing with my kids, or playing video games.

Track record

6 roles

  1. Owning the frontend architecture — the shared patterns, libraries and tooling the rest of the team builds on.

    • Own the frontend architecture and its shared patterns
    • Set the coding standards and review practice for the team
    • Lead and mentor the frontend developers
    • JavaScript
    • TypeScript
    • SCSS
    • Playwright
    • Jest
    • Angular
    • REST APIs
    • Tailwind CSS

02

Skills & technologies

The stack I reach for by default, and the tools I have shipped production work with.

Frontend

09
  • Angular
  • React
  • Next.js
  • TypeScript
  • JavaScript
  • RxJS
  • Tailwind CSS
  • SCSS
  • HTML/CSS

Backend

05
  • Node.js
  • REST APIs
  • GraphQL
  • MySQL
  • MongoDB

Testing & tooling

06
  • Cypress
  • Playwright
  • Jest
  • Git
  • Docker
  • VS Code
03

Selected work

  1. 01Product · brand-builder.io

    Brand builder

    A personal branding platform built for developers, designers and tech creators who want to showcase their work authentically.

    • Next.js
    • Node.js
    • MongoDB
    • Tailwind
    Visit
  2. 02Open source · skills.sh

    Skills that travel between repos

    Agent skills for everyday delivery work. Most workflow automation hardcodes one issue tracker and one branch name, so it breaks the moment you reuse it. These separate the process from the parameters: each repository supplies its own tooling through small config files, so the same commands adapt to any tracker, branching model or stack.

    • Claude Code
    • Agent Skills
    • Node.js
    • Open Source
    VisitSource
04

Got something worth building?

I am open to new opportunities and interesting problems. Questions, proposals and plain hellos all land in the same inbox, and I do my best to answer every one.

hello@tomwebwalker.pl
Say hello

Warsaw, Poland · CET