Technical skills and ecommerce judgment
The stack is table stakes. What actually determines the outcome is knowing which part of the stack a given problem needs, and that judgment only shows up when it's tested against real stores under real constraints.
Shopify Plus & Commerce Architecture
- Shopify Plus
- Shopify 2.0
- Custom Themes
- Liquid
- Shopify Functions
- Checkout Extensions
- Checkout UI Extensions
- Shopify Markets
- Metaobjects
- Storefront API
- Admin API
- Private & Public Apps
Where most of the work in the case studies actually lives: custom apps, checkout extensibility, and theme architecture built to survive being touched by more than one developer.
See the case studyFrontend
- React
- Next.js
- Remix JS
- JavaScript (ES6+)
- Tailwind CSS
- SCSS
- HTML
React and Next.js power the headless PDP layer at The Sleep Company. Remix and GraphQL power the headless builds at VISEO Asia.
Backend & APIs
- Node.js
- RESTful APIs
- GraphQL
- Laravel (PHP)
- Prisma
The virtual-cart validation behind the discount engine, and the real-time middleware behind the inventory sync, are both backend-first problems before they're anything else.
See the case studyDatabases
- MySQL
- MongoDB
Relational where the data is structured and relationships matter, document-based where the shape of the data varies by merchant or by app configuration.
Performance Engineering
- Core Web Vitals (LCP, CLS, FID)
- GTMetrix
- Headless Architecture
- Server-Side Rendering
- Lazy Loading
Every deployment gets validated against Core Web Vitals, not assumed to be fine. That discipline is the reason this site itself runs a 100 on Lighthouse.
See the case studyCRO & Testing
- A/B Testing
- PDP & PLP Optimization
- Post-Purchase Funnels
- Upsell Flows
- Conversion Rate Optimization
CRO only works in the right order: UX research finds the problem, analytics sizes it, and only then does an A/B test validate a specific fix.
See the case studyMulti-Market Commerce
- Shopify Markets
- Multi-Currency
- Multi-Language
- International Storefronts
- Multi-Store Setup
One theme architecture, several brands, every market they operate in, without a fork per market silently drifting from the others.
See the case studyLeadership
- Team Leadership
- Agile / Scrum
- Sprint Planning
- PR Reviews
- Code Reviews
- Mentoring
- Jira, ClickUp, Trello
Sprint completion sitting at 90–95% and escalations down 50% year over year aren't process theater. They're what a clean backlog and an enforced PR review SLA actually produce.
See the case studyHow I think about the business side
Technical skill only matters when it's pointed at the right problem. These are the frameworks I actually use to decide what that problem is.
AOV, conversion, LTV — in that order
A feature request is usually a symptom. These three numbers point at the actual disease, and which one is broken determines whether the fix is a post-purchase flow, a checkout audit, or a retention loop.
Read the frameworkBuild vs. buy is a real decision, not a default
Use an app when the use case is standard and proven. Build custom when no app exists, the available ones hurt performance, or the logic is too specific for a general-purpose app to handle without becoming a liability.
Read the frameworkHeadless earns its cost, it isn't a default
Simple SKUs, a clean UX requirement impossible in native Shopify, and a dedicated team: headless is worth it. Fast-moving marketing and a lean team: native Shopify 2.0 gets you further, faster.
Read the frameworkCertifications
- Shopify Theme Developer Certification
- Salesforce Commerce Cloud (SFCC) B2C Developer Certification