ssam//commerce

// About — 08

An engineer for the systems behind the store.

I'm Usama Junaid. I build and operate the technology modern businesses actually run on: ecommerce platforms, the backends behind them, the integrations between systems, and the automation that removes the manual work in between.

// A — Background

Breadth as a feature.

Usama Junaid — software engineer, wearing a navy suit and sunglasses
FIG — USAMA JUNAID / PRINCIPAL ENGINEER
whoami
$ whoami
usama.junaid
 
focus ecommerce · automation · ai
posture build · operate · improve
platforms shopify/plus · custom stacks
runtime typescript · postgres · docker
hosts one server, many isolated stacks
 
status open for select engagements — q1 2027

FIG — IDENTITY CARD

My work sits at the intersection of commerce and systems engineering. On one side: Shopify and Shopify Plus storefronts, product data, and conversion infrastructure. On the other: backend systems, APIs, messaging infrastructure, and deployment pipelines.

Between them is where the real problems live — the installment-scheduling platform that has to reconcile ledgers, the webhook pipeline that can never fire twice, the catalog whose quality quietly determines what the whole store can promise.

Recent years have added AI and automation to the practice — with a bias toward LLM steps that are guarded, evaluated, and audited, and agents that execute runbooks rather than improvise policy.

This site — samcommerce.dev — is the map of that practice: work, engineering, experiments, tools, and writing under one identity, operated as its own little system.

// B — Philosophy

How the work gets done.

  1. 01Systems over pages

    A store is not a website; it's an operation with a UI. The interesting engineering is in the operation — data, flows, failures — and the interface should express it honestly.

  2. 02Boring infrastructure, exciting outcomes

    The infrastructure should never surprise you. Proven tools, small blast radii, rehearsed restores. The excitement budget gets spent on what the business can now do.

  3. 03Evidence over claims

    No invented metrics on this site, no case studies I can't defend, no clients named without permission. The work should read as credible because it's specific — not because it's loud.

  4. 04Automate the second time

    Do it manually once, deliberately, and pay attention. The second time is a script. The third time it's someone else's job entirely — that's the point.

  5. 05Legible by default

    Audit logs, runbooks, and records that outlive the moment. Systems should be explainable to the next engineer — including future-me, who remembers nothing.

// C — Interests

What gets attention off the clock.

Ecommerce platformsProduct data modelingLLM tooling & evalsAgentic workflowsMessaging systemsSelf-hostingDockerPostgreSQLDeveloper experienceDesign systems

// Engage

The best conversations start specific.

A system, a bottleneck, a deadline — bring one and we'll have plenty to talk about.