Konrad Szczepanowski
Konrad SzczepanowskiOpen to roles
Frontend DeveloperOpen to frontend roles
Frontend DeveloperPortfolio — 2026

Sharpfrontend.Cleancode.

I build polished interfaces with React, Next.js, and TypeScript — with care for UI, performance, accessibility, and code a team can confidently extend.

[01]About

I'm Konrad — a frontend developer with an eye for UI and a habit of keeping the code clean.

I do my best work where an interface needs to be fast, responsive, and visually considered. I like building components that feel light on the surface, but have clear TypeScript, predictable states, and a tidy structure underneath.

I use AI to move faster, not to stop thinking. What matters to me is still the craft: accessibility, performance, communication, and code the next person on the team can build on without dread.

Technologies
FocusUI craft / performance / accessibility
WorkflowAI-assisted workflow
4+Years of Experience
4Case Studies
10+Projects Created
Portrait of Konrad
[02]Selected work

Want to see how I work in practice?

Let's walk through the projects on a call.

[03]Tech stack

The stack I use to ship production interfaces.
No decoration for decoration's sake.

I mostly work in the Next.js or React ecosystem: components, routing, forms, animation, performance, accessibility, and API integrations.

ReactUI
Next.jsFramework
Express.jsFramework
TypeScriptLanguage
Tailwind CSSStyling
Z
ZustandState
FigmaDesign
Node.jsRuntime
PostgreSQLDatabase
MongoDBDatabase
ClaudeAI Tool
CodexAI Tool
[04]Skills

I bring frontend that is visually precise and technically calm enough to maintain.

01

Frontend Engineering

I build React, Next.js, and TypeScript components with clear APIs, predictable state, and code that can keep growing after the first release.

02

UI & Motion

I care about responsive layouts, microinteractions, type rhythm, and animation that helps people understand the interface instead of just decorating it.

03

Product Thinking

I do not stop at JSX. I think through users, requirements, edge cases, and how to get from an idea to something shipped and usable.

[05]How I work
01Step 01

Understand the problem

I start with context: the goal, the user, the constraints, and what actually needs to change in the product.

02Step 02

Shape the solution

I break the work into states, components, and flows. If something is unclear, I clarify it before it becomes debt in the code.

03Step 03

Implement

I write TypeScript-first frontend while keeping an eye on responsiveness, accessibility, performance, and clear ownership boundaries.

04Step 04

Test and iterate

I check edge cases, polish the details, and leave the solution in a state that can be extended without digging for missing context.

[06]How I approach work
01

Care for detail

I pay attention to the things that are easy to miss: spacing, hover and focus states, empty states, transitions, contrast, and small inconsistencies that make a product feel unfinished.

02

Clear communication

I would rather name a risk early, ask for missing context, and show progress than silently deliver something the team does not need.

03

AI as workflow leverage

I use AI for faster research, prototyping, and solution checks, but the technical decisions, quality, and responsibility stay with me.

04

Ownership of the outcome

I do not treat a task as done just because the code compiles. I care whether the interface works, makes sense, and can be maintained.

[07]Contact

Hiring a
Frontend Developer?

Send a few words about the role, team, or product. I will reply with something concrete.

Open to frontend role conversations