Roman-Leonid Yurchenko

Placeholder copy

I have spent six years delivering Shopify work, mostly as the engineer an agency brings in once a build stops being routine. Over the last three that has narrowed to complex storefront logic and Plus platform engineering — Functions, checkout extensibility, and configurators whose difficulty is the state model rather than the markup. I want to go further into the architecture and platform decisions, on a team where those are made rather than inherited. I am open to a senior role or a continuing agency collaboration; the difficulty of the work matters to me more than the shape of the arrangement.

Ownership

I take the whole problem, including the parts that turn out to be someone else’s. I say what I do not know rather than guessing in public.

Constraints first

Most Shopify decisions are placement decisions, and placement is decided by what the platform will reliably enforce. I work out the boundary before the implementation.

Maintainability

I write for the developer who inherits it. If a solution requires me to explain it, it is not finished.

Communication

Written status without being asked. Tradeoffs stated as tradeoffs, not as recommendations with the reasoning removed.

Placeholder copy

1. 0170+ Shopify storefronts across 30+ clients, the majority inside agency delivery teams rather than direct to merchant.
2. 02Shopify Functions and Checkout UI Extensions running in production on Plus stores, replacing three paid apps on one of them.
3. 03A four-year partnership with one agency, building from Figma files to launch across roughly twenty projects.

Platform

• Shopify Plus
• Functions
• Checkout Extensibility
• Metaobjects
• Markets
• B2B

Languages

• Liquid
• TypeScript
• Rust (Functions)
• GraphQL

Frontend

• OS 2.0 theme architecture
• Alpine
• Tailwind
• Next.js

Tooling

• Shopify CLI
• Git
• GitHub Actions
• Vercel