I work on digital products from the first prototype to the fixes after launch. I find where people drop off, make slow or hard-to-use pages fast and accessible, build features properly without a long ramp-up, and turn AI demos and ideas into products that hold up with real users.
Worked acrossEnterprise pricing and promotion software · fintech · translation software · large-scale web apps · real estate and property management software · booking platforms · microlearning and training software · community products
UX & conversion audit
The problem
People land on your site or sign up, then stop somewhere before the product makes sense to them. You can see it in the numbers, but not where it happens.
What I do
I go through your site and product the way a new user would, on desktop and on a phone. Depending on what you need, that includes screenshots of where each issue happens and a comparison with two or three competitors. Every audit ends with a walkthrough of what matters most, in plain language, and what I'd change. Then I design and build the fixes.
Where I've done it
At Code of Talent I worked on conversion: I simplified user flows, prototyped a new onboarding, and built a guided product tour. I also built my own audit tooling that measures performance, accessibility and mobile issues in a real browser, so the findings start with real data.
How we start
A small fixed-price audit, about 2 to 5 days, depending on the product's size and business domain. You get a ranked list of issues, two or three quick wins I can ship first, and a proposal for the larger changes.
The site looks fine on your laptop, but it's slow on a phone, the layout breaks on small screens, or parts of it can't be used with a keyboard or screen reader. Most visitors won't tell you. They just leave.
What I do
I measure the site with Lighthouse, plus real-user data where there's enough traffic. Then I fix what slows it down or shuts people out, and check the result on real devices. If you don't have monitoring yet, I can set it up, so you can see where things break for users.
Where I've done it
At RELEX I was on the on-call rotation, where I tracked down and fixed performance issues caused by large amounts of data, on both the client and the server.
How we start
One page, usually the one that brings in the most sign-ups, measured before and after.
You have a prototype, a redesign, or a backlog, and you need it built properly without a long ramp-up.
What I do
I own frontend work end to end: architecture, implementation, testing, reviews, and the follow-through on performance after launch. I learn your business domain first, so the code fits your product.
Where I've done it
At RELEX I led two frontend epics end to end, from planning and technical requirements to delivery, working with backend, product and design.
At Cognizant I designed a micro-frontend architecture and set up a Lerna monorepo for a team of 50+ engineers.
On that app I also integrated payments, analytics and error tracking. I use Sentry and Datadog to see what breaks and for whom.
How we start
One well-scoped feature or epic on a fixed timeline, so we can both see how we work together before committing further.
You have an AI-built demo, or an idea that still lives in a doc. It works when you click through it yourself, but you don't know if it will hold up with real users, real data and a real codebase.
What I do
I map the flow, design the key screens and build a working prototype, using AI tools to move quickly. Then I decide what stays, what gets rewritten, and what it takes to run it in production.
Where I've done it
At RELEX I turned a vibe-coded concept into a production-ready feature, working closely with design. I checked the AI-generated code against the product requirements and our architecture, and reworked what wouldn't hold up long term.
Fika for Substack, Retrobox and Huecode each started as an idea that I designed and built myself, with AI coding agents.
How we start
You show me the demo or tell me your idea, and I tell you what it would take to ship it. If it's only an idea, we take it to a first prototype you can test with users. We make the decisions together, from the product brief and design to the architecture and tools.
Things I've shipped in public, and things I'm still figuring out
Side project · Live
Fika for Substack
Problem: Substack’s recommendation system is built around algorithms and popularity signals. But the writers that matter most don’t always show up there.
What I built: an appreciation-based flow: sending one kind word to a writer, getting a slice of the current week's cake in return and the appreciation remains on a wall forever, for everyone.
Result: shipped and live, a small working experiment to better understand the discovery through appreciation problem.
Problem: Every web app needs eight color roles (primary, secondary, accent, neutral, plus four status colors), each in eleven shades to hold up across hover states and dark mode. Most palette tools stop at a handful of hex codes and leave the rest to you.
What I built: Huecode turns a theme description or an image into a complete 8-role Tailwind color system, each expanded into a full 11-shade scale. Every palette previews live against a demo dashboard, a component kit, and a marketing page, in light and dark mode, so you can see it working before you commit to it.
Status: in active development, working on making it a community project.
I build scalable, high-performance web applications, usually somewhere between product, design, and, increasingly, AI. I design the interfaces I ship, build AI features that hold up in production, and explain the trade-offs in natural language.
Besides frontend engineering and product, there are some things I care about that are not always visible: I learn the business domain before I touch the architecture, I ask why before how, and performance and usability still matter to me long after the feature has shipped.
Product Engineering
Frontend Architecture
UX/UI
Product Thinking
Building in Public
AI-Assisted Development
Skills & Tools
What I reach for
Frontend
TypeScript
React
Next.js
Vue.js
Tailwind CSS
React Query
Zustand
Product & UX
User flows
Prototyping
UX audits
Accessibility
Figma
AI-assisted development
Claude Code
Claude Design
Cursor
OpenCode
LM Studio
Architecture
Micro-frontends
Monorepos (Lerna)
Design systems
Testing & observability
Playwright
Vitest
Jest
Cypress
Sentry
Datadog
Backend
Node.js
PostgreSQL
Go
Python
Experience
Where I've honed my skills
05/2025 — 04/2026 · Stockholm, Sweden · Remote
Senior Frontend Developer — RELEX Solutions
Retail pricing and promotion software
09/2021 — 05/2024 · Bucharest, Romania · Remote
Software Engineer, Web — Cognizant Romania
Real estate and property management software · Booking platform
A newsletter about engineering judgment in an industry obsessed with speed
This is where I think out loud about frontend engineering and engineering in general. The code I'm writing, the career lessons I'm learning, and all the invisible work that actually matters, shared one small note at a time.
