Dawid Kostrzewa

Senior Frontend Engineer

8+ years of experience in React, Next.js, and TypeScript. I lead frontend architecture in production applications. I've also worked as a full-stack engineer on backend projects — Node.js, PostgreSQL, and headless CMS.

LinkedIn
8+years
of commercial experience
Frontend
React · Next.js · TypeScript
Fullstack
Node.js · PostgreSQL · Supabase
Mentoring
and content creation

01.About me

I work commercially as a Senior Frontend Engineer. I build web applications in React, Next.js, and TypeScript — but the frontend specialization isn't a hard line. When a project needs it, I take ownership of the database, the API, and CMS configuration.

My day-to-day is leading frontend architecture in Scrum teams. I talk to stakeholders about requirements, pick the architectural approach, and ship it to production. I build Design Systems, optimize performance, and set up testing practices.

Outside of client work, I mentor frontend developers, run code reviews, and write technical content on my blog and Instagram. I also build my own products, including a fullstack personal-finance app.

ReactNext.jsTypeScriptNode.jsPostgreSQLDesign Systems

02.How I work

I work as a Senior Frontend Engineer in Scrum teams. I own the full lifecycle of a feature: refinement, architecture, implementation, and production monitoring.

01

Refinement and requirements

I show up to refinements with the product manager and stakeholders to clarify requirements, surface technical constraints, and flag risks at the boundary with other teams. The more we resolve before implementation, the cheaper the changes are later.

02

Architectural decisions

Before implementation, I design the module structure, ownership boundaries, and conventions the team will keep using. Technology choices are documented and discussed: a library or pattern should be driven by the project's needs, not the author's preferences.

03

Implementation and code review

I deliver work that fits team standards: readable, tested, and ready for handover. If a feature needs changes in the API, database, or CMS, I handle them myself instead of blocking on another team. Code review is an equal part of the process — I review peers' work and ask for review on mine.

04

Post-release monitoring

After release, I watch how the feature performs in production: Core Web Vitals, errors, and user feedback. Findings come back to the team as concrete tasks — refactoring, optimization, or architectural fixes in areas that proved hard to maintain.

03.What I do

Day-to-day frontend and fullstack work, tech leadership and performance, personal products, and mentoring outside my full-time role.

Frontend Architecture

React, Next.js, TypeScript as my daily stack. State management, advanced component patterns, render optimization, REST/GraphQL integrations.

Backend & Infrastructure

Node.js and Express for APIs, PostgreSQL with Prisma, Supabase for auth/storage, PayloadCMS and Contentful for content. End-to-end feature ownership.

Design Systems & Tech Leadership

Code review, testing standards, shared Design Systems used across multiple teams. Onboarding new developers to the project.

Performance & Scale

SSR strategy, code splitting, caching, data fetching. Data-heavy apps: real-time maps, analytics dashboards, complex business tables.

Own Products

DailyBudget.pl — fullstack personal finance app with multi-tenancy, encryption, and AI receipt scanning. From concept to production.

Mentoring & Education

1-on-1 mentoring in React and JavaScript. Technical content on blog and Instagram.

@dev.dawid technical posts

04.Technologies

The stack I use commercially and in my own projects.

JavaScript
TypeScript
React
Next.js
Node.js
Angular
PostgreSQL
Tailwind

05.Selected writing

06.Get in touch

The fastest way to reach me is LinkedIn or the contact form.