I own the product end to end — and I know the difference between “it works” and “it feels great.”
Fifteen years shipping web products — the API, the data, and the interface. Happiest when the feature is mine from the plan to the pixels: I prototype in code, ship with tests, and still care how it feels.
React · TypeScript · Vue · Node · Figma
2014 – 2026
Twelve years on one of the world’s largest freelance marketplaces. Two kinds of work: the product pages people use every day, and the infrastructure and UI components those pages are built from.
Product screens stay inside the company. The work is the surfaces, the platform, and the quality bar.
2018–2026, on the product team. Pages and features from planning with PMs and design through tests and gradual rollout.
Pages
Owned it as the one engineer on the feature — a light CRM where clients review applicants, filter them, and send invites. The UI was built from scratch; tests (Cypress, Jest) and rollout sat with me. Shortlisting and inviting became noticeably faster.
Built the interview review page: a custom video player with YouTube-style controls and an AI-generated summary of each interview. Clients screen from a recording instead of scheduling a live call. The player had to feel native to the product — not a third-party widget dropped on the page. Interaction work that later drew on OneLinePlayer.
Features from planning to release, with PMs, designers, and QA — design docs, tests, CI, and gradual rollouts. I didn’t wait for a pixel-perfect spec on every state: I asked for intent, then made the call in the UI. I reviewed what teammates shipped and caught product inconsistencies at a glance.
The layer under those pages: APIs, microfrontends, two core migrations, and the shared component library.
Platform
I started on Infrastructure (2014–2018), designing PHP BFF APIs and the microfrontend layer every upwork.com page sat on. Later I helped drive two company-wide migrations of the frontend core — first to Vue 3, later to React, Next.js, and GraphQL.
The job was evolving what already shipped, not throwing it away: a shared core, fewer one-off stacks, better developer experience. The next page didn’t start from scratch.
Co-built Upwork’s shared UI component library. Day-to-day with design: Figma to Storybook, implemented in Vue and React. Fidelity and reuse — components high-traffic teams could trust, not a parallel visual language. Filling gaps, refining patterns, keeping the system honest as the product grew.
2011 – 2014
Fullstack engineer on Veeam’s marketing team — brand sites, content, careers. Stakeholders were marketers and communicators, not only engineers. The work was the surfaces visitors actually see, and the systems that feed them.
Proposed and built the company’s in-house single sign-on on OAuth2, used across internal frontend applications. Initiative first, then a system other teams could actually adopt.
Designed and built a headless internal CMS — REST API plus an admin panel — that served content to the marketing web apps. Brand pages stopped being hand-edited islands.
The HR website — a public recruiting and brand surface. Same job as any marketing page: clear hierarchy, a path to apply, a company that looks like itself.
