Frontend systems
Interfaces that stay sharp as the product grows.
My default lane is typed, component-driven frontend work with enough structure to scale without feeling rigid.
Full-stack development for ambitious digital products
I'm Catalin "cLu" Stroe, a full-stack developer blending product thinking, motion, and modern frontend engineering. I help founders and teams turn ambitious ideas into polished sites, dashboards, APIs, and full-stack products that people actually enjoy using.
5+
years building web products
Full stack
frontend, backend, APIs, and product flow
Remote
async-friendly collaboration
Frontend
Next.js
High-performance interfaces with deliberate motion and clear interaction design.
Product
UX + flow
Landing pages, dashboards, onboarding, and systems that feel coherent end to end.
Backend
APIs
Data flows, integrations, and application logic that support the frontend instead of slowing it down.
Studio
cLu
Direct collaboration, fast iteration, and a strong bias toward shipping work with character.
Fast without feeling rushed
Strategy, layout, motion, and implementation in one loop, so the work stays sharp instead of getting watered down between handoffs.
Why teams hire me
I care about structure as much as spectacle. That means sharper navigation, clearer messaging, stronger interaction states, and systems that still feel good once real users start clicking around.
The goal is never motion for its own sake. It is to guide attention, reinforce hierarchy, and make the product feel more intentional.
A few turning points that shaped how I approach product design, full-stack development, and modern frontend engineering today.
Focused on shipping sharper product surfaces: portfolio experiences, frontend systems, and full-stack applications with better pacing, hierarchy, and interaction quality.
Went deeper into full-stack delivery, pairing frontend craft with backend services, integrations, and the kind of practical decisions that make products easier to ship.
Started from curiosity, experimentation, and a lot of iteration. That foundation still shapes the way I work: keep learning, keep shipping, and keep raising the bar on the details.
Core stack
Less filler, more signal: typed frontend architecture, practical backend work, and data tooling that helps ship real features without making the stack feel bloated.
Frontend systems
My default lane is typed, component-driven frontend work with enough structure to scale without feeling rigid.
Backend and APIs
I build the backend pieces needed to keep the frontend fast, consistent, and easier to evolve.
Data layer
I reach for managed backends when they help teams move faster without turning the codebase into a workaround factory.
Mobile and native
I can work beyond the web too, whether that means React Native for shared product logic or Swift and SwiftUI for Apple-native interfaces.
AI tools
This is part of my workflow, not an afterthought. I use AI tools to move faster, evaluate alternatives, and keep momentum high while still making the actual product decisions myself.
I use AI tools daily to accelerate implementation, explore options, and unblock research faster.
I use them to test approaches, draft structures, and tighten rough ideas before I commit them to code.
They help me pressure-test edge cases, spot weak assumptions, and move through repetitive work with more speed.
The point is not replacing judgment. It is shipping better work faster with stronger feedback loops.