Senior React developer for complex frontend applications
Based in Wroclaw, Poland · EU timezone · Available for new projects
I've been building with React since 2016. Component architecture, state management, design systems, performance optimization — I've done it all across dozens of production apps. Whether you need someone to join your team or build a frontend from scratch, I deliver production-grade React code.
Complex dashboards and data-heavy UIs
Real-time analytics dashboards, admin panels with hundreds of data points, and interactive tables with filtering, sorting, and virtualization. Built for performance at scale with TanStack Query and Zustand.
Design system implementation
Component libraries built on Radix or shadcn/ui primitives, documented with Storybook, and themed with Tailwind CSS design tokens. Accessible, composable, and consistent across your entire product.
Single-page applications
Client-rendered SPAs for tools that don't need server rendering — internal portals, productivity apps, and embedded widgets. Optimized bundle size, lazy loading, and offline-capable when needed.
Migration from other frameworks
Moving from Angular, Vue, jQuery, or legacy React class components to modern React with hooks, TypeScript, and current best practices. I migrate incrementally — no big-bang rewrites.
Performance optimization
Auditing slow React apps: identifying unnecessary re-renders, fixing memo/callback misuse, implementing virtualization, optimizing bundle splits, and setting up proper profiling. Measurable improvements, not guesswork.
Component architecture
I design component trees that scale. Compound components, render props, composition over inheritance. Clean separation of container logic and presentational UI. Components that are easy to test, reuse, and refactor.
State management
TanStack Query for server state, Zustand for client state. I know when to reach for global state and when local state is enough. I've used Redux at scale and know when it's overkill.
TypeScript integration
Strict TypeScript from day one. Generic component props, discriminated unions for state machines, Zod for runtime validation, and end-to-end type safety from API to UI. No any types.
Testing strategy
I test what matters: integration tests with Testing Library for user flows, unit tests for complex logic, Playwright for critical E2E paths. Not 100% coverage — meaningful coverage that catches regressions.
Accessibility (a11y)
ARIA attributes, keyboard navigation, focus management, screen reader testing. I build on top of accessible primitives (Radix, HeadlessUI) and verify with real assistive technology, not just automated audits.
Performance profiling
React DevTools Profiler, Chrome Performance tab, Lighthouse CI, and real-user metrics. I identify the actual bottleneck before optimizing — not premature memo everywhere.
Codebase assessment
I review your existing frontend: component structure, state management approach, testing coverage, and performance baseline. For greenfield projects, I design the architecture upfront.
Iterative delivery
I ship working features every two weeks. You review real UI, not mockups. We iterate together on UX, adjust priorities, and keep scope honest. Transparent progress throughout.
Clean handoff
Documented components, typed APIs, meaningful test coverage. Your team inherits a codebase they can actually work with. I can stay on for maintenance or hand off completely.
If you're building a full web application with SEO, server rendering, and an API layer, you need Next.js. If you're building a client-side SPA, an internal tool, or a widget library, pure React is the right choice. I do both — we can figure out the right approach on a call.
Yes, frequently. I join existing teams, take over codebases from previous developers, and fix performance issues in production apps. I'm comfortable with legacy class components, older state management, and incremental modernization.
TanStack Query for server state (API data, caching, pagination), Zustand for client state (UI state, form state, local preferences). I avoid Redux on new projects unless the team already uses it. Context API for simple cases like themes and auth.
Yes. I build component libraries on top of Radix or shadcn/ui, style them with Tailwind, and document them in Storybook. Accessible by default, themeable, and designed for your team to extend independently.
Integration tests with React Testing Library for user-facing behavior, unit tests for complex business logic, Playwright for critical end-to-end flows. I focus on tests that prevent real bugs, not vanity coverage numbers.
I work on a daily or monthly rate depending on the engagement. Book a free 30-minute call and I'll give you an honest estimate based on your project scope and timeline.
Ready to hire a senior React developer?
Book a free 30-minute technical call. I'll review your requirements and tell you honestly if I'm the right fit.