Vladyslav P.

I build the interactive end of the web: scroll-driven sites, 3D scenes you move through in the browser, and motion that still holds up on a phone. Three.js, React Three Fiber, WebGL and GSAP, on React, Next.js or Nuxt. Recent work: a nine-floor 3D world for T-Pain's record label, where each floor is a 360 room you drag to look around, with objects marked and clickable and a store built into the space. Before that, a live plan of a 14-hectare residential estate you turn through the seasons, with map layers, sectors, and floors you can step between. On both I built the scenes, the camera and the interaction logic. The other half of what I do is taking over React products that have outgrown their first version and getting them shipping fast again: architecture, types, tests, no rewrite and no feature freeze. That usually means a half-finished handover, a product that has outgrown its first version, or a team that ships slower every month than the month before. I go in, read the code, find what is actually holding things back - architecture, build, types, missing tests - and fix it while features keep shipping. The longest of those was five years at C the Signs, a UK healthtech company whose early cancer detection platform is used by NHS clinicians. I joined when it was an early-stage startup with one React codebase and one release train, and left with three product teams shipping independently. Some of what I did there: • Split a monolithic React codebase into 5 micro-frontends using Module Federation, so the company could grow from 2 Scrum teams to 3. Releases went from one shared train every two weeks to several per sprint, with no team blocking another. • Built and published an internal design system as a versioned npm package: 20+ components, Storybook docs, semver and migration guides, used by two teams. • Moved a 30+ page product from JavaScript to TypeScript incrementally, with no feature freeze. • Set up the testing practice from nothing: Jest, React Testing Library and Cypress, none of which existed when I started. • Built a client-side error handling framework that reported every runtime error to Rollbar, raised a Slack alert, opened a support ticket automatically, retried what was recoverable, and showed the user real guidance when the error was one we already knew about. How I work now: TypeScript, React, Next.js and React Native day to day, Vue and Nuxt on the creative side. I cross into the backend-adjacent layer when it helps - Node, Express, NestJS, REST and BFF design. Claude Code and Copilot are part of my normal workflow, not an experiment, which is most of why I can move fast on unfamiliar codebases. I also go after cost and performance problems in code I'm handed. Most recently, a cost and security audit of a high-traffic Firebase and GCP platform: I read the whole repository against 100 days of real billing, logged 49 findings with evidence and effort, and the monthly run rate went from about $1,200 to a $300-500 average. Domains: healthcare, B2B dashboards, travel and booking, agriculture, brand and agency work. Available now, 30+ hrs per week. Good fit if: you have a site or a launch that needs to move - scroll, 3D, motion - or a React product that has outgrown its first version and needs a senior who will think about architecture rather than close tickets. Tell me what you are working on and I will tell you straight whether I am the right person for it.