Bio
I’m Sabin Marcu, a full-stack web developer who tends to spend most of his time where product work, platform engineering, and developer experience meet. I enjoy building software that has to be both practical and pleasant to work with, whether that means shipping a customer-facing application, tightening up a monorepo, or shaping the tooling that keeps a team moving.
Over the years I’ve worked with React, TypeScript, Node.js, GraphQL, and modern frontend tooling across a range of environments, from patient-facing healthcare software to internal platform systems and monorepo infrastructure. A recurring theme in my work is making complex systems easier to maintain: design systems that stay coherent across applications, build pipelines that scale without becoming fragile, and architectures that leave enough room for teams to evolve the product without fighting the codebase.
That has also led me into a lot of cross-cutting work. At Hootsuite, I spent a large part of my time on a 900+ package monorepo, CI orchestration, micro-frontend support, and the kind of infrastructure work that quietly improves build times, memory usage, and release confidence. At Platform24, I worked on the patient application, its React Native counterpart, embedded solutions, and a whitelabel design system built around typed contracts and build-time CSS. Outside of those larger product environments, I’ve built tools such as TSCMono, the ESLint Logical Properties plugin, Jotai query-string storage adapters, and Storybook addons that improve how interface layers and documentation environments behave together.
I also like making smaller, more focused things when they help explain an idea or validate a technique. This site includes projects such as the Rotation App, Crafting Works, and a few visual experiments and snippets like the 3D showcase and CRT screen CSS. Those pieces matter to me because they show the same pattern at a smaller scale: a preference for useful structure, careful presentation, and enough polish that the thing feels deliberate rather than throwaway.
Alongside the code, I’ve spent time teaching React and GraphQL workshops, which has been useful not just for communication, but for clarifying how I think about systems. I like work that is technically rigorous without being self-important, and I’m usually happiest when I’m helping a team make something complicated feel straightforward.
PS. Bear in mind, the above was generated with AI and I don't give enough of a damn about a section such as to check it or make it more personal. Check my Github or the projects / snippets / tools on this website if you're curious.