Clinton Brown — Shopify & Headless Commerce Engineer

01 / 05

Selected work

Four open-source builds. Each ships the same job twice and measures the difference, so the numbers are a command you can re-run rather than a claim.

01Shopify Campaign Velocity LabShopify theme · Open sourceOne storefront built twice — content in Liquid, then in sections and metafields — with twelve campaign requests replayed through both.10 / 12Campaigns shipped by configuration
02Shopify Headless Perf LabHeadless storefront · Open sourceA headless Hydrogen storefront shipped in two modes, so every performance number can be re-run by anyone who clones it.−47%Largest Contentful Paint
03Shopify Inventory Sync LabIntegration service · Open sourceA webhook consumer that keeps stock correct under Shopify's at-least-once, out-of-order redelivery.0 unitsLedger drift across six seeds
04Shopify Bulk Metafield EditorEmbedded admin app · Open sourceAn embedded Polaris app built around the Admin API's cost limit, where a naive retry loop drops writes and still reports success.0 lostWrites dropped by the cost-aware client

02 / 05

Capabilities

The tools I reach for first. The rest — WooCommerce, BigCommerce, Vue, Redis, MongoDB, AWS, Klaviyo, GTM, Stripe, ShipStation — is on the full background.

Commerce: Shopify Plus
Hydrogen
Storefront API
Admin API
Liquid
Checkout Extensibility
Front end: React
Next.js
TypeScript
Tailwind CSS
Back end: Node.js
GraphQL
PostgreSQL
MySQL
Laravel
Delivery & measurement: GitHub Actions
Vercel
Docker
Lighthouse CI
GA4

03 / 05

How I work

Three habits that show up in every build.

Performance is a budget, not a sprint. A storefront accumulates cost one reasonable request at a time — a reviews app, a popup, an upsell widget. I put the number on the pull request that introduces it, so the merchant is choosing between a feature and a measured cost while it is still one line to revert.

Decisions get written down. Short decision records for the calls that shaped a build, and runbooks for the failures support will meet at 2am. The person picking the store up in six months is usually not me.

Risky work ships in phases. On a replatform I like navigation and catalog pages to land and settle before the PDP, so there is a working store at every step rather than one launch that has to go perfectly.

04 / 05

Experience

The last four roles. Six-role history on the full background.

Dec 2025 — Jun 2026

Senior E-Commerce Full Stack Developer

Netalico · Remote

Owned day-to-day Shopify Plus delivery across merchant accounts — Checkout Extensibility, custom apps on the Admin and Storefront APIs, and a Node.js service syncing ERP catalog and inventory into Shopify with webhook handling and retry logic. Brought PDP and collection LCP down ~22%.

Jan 2024 — Nov 2025

Senior Ecommerce Engineer

Human Good Kind · Nashville, TN

Led a headless migration to Next.js and the Shopify Storefront API for a DTC brand, phased so navigation and catalog landed before higher-risk PDP work. Checkout stayed on Shopify. Email-attributed revenue rose ~14% over two quarters; a shipping-message test lifted checkout-start ~6%.

Dec 2022 — Dec 2023

Senior Full Stack Engineer

Acklen Avenue · Nashville, TN

React/Next.js clients and Node.js services for enterprise SaaS. Tuned PostgreSQL schemas and indexes on the heaviest report path, taking response time from ~4.5 s to under 900 ms.

Oct 2019 — Nov 2022

Senior Shopify Developer

UPQODE · Nashville, TN

Shopify and Shopify Plus builds for retail, CPG and subscription merchants. Rebuilt three Plus themes around reusable Liquid sections and metafields so marketers could launch without theme deploys. Mobile Lighthouse on priority templates went from the low 40s into the mid-70s.

Full background

05 / 05

Contact

Hiring for a Shopify or headless role, or want a second opinion on a store? Send a line or grab a time — whichever is easier.

Have a storefront that needs to be faster, or a build that needs an owner who measures?