About

ENGINEER
BETWEEN
SYSTEMS.

I started in web development and gradually moved deeper into the systems behind commerce — APIs, ERP integrations, automation and infrastructure.

Most of my work now sits between customer-facing commerce and the operational systems that keep it running: storefronts, marketplaces, NetSuite, and the automation connecting all three. The problems I like most cross system boundaries, where the hard part isn’t the code — it’s understanding how a business actually operates before deciding what to build.

Current focus

What I am working on

Ecommerce Coordinator
Sinister Diesel

The title covers the ecommerce operations side; day to day the work is systems engineering — designing and running the Miva↔NetSuite and TikTok↔NetSuite integrations, the monday.com automation, the storefront design-system revamp, and the operational tooling around all of it, in production.

Experience

The trace so far

Jun 2026 — present

Ecommerce Coordinator

Sinister Diesel

The title covers the ecommerce operations side; day to day the work is systems engineering — designing and running the Miva↔NetSuite and TikTok↔NetSuite integrations, the monday.com automation, the storefront design-system revamp, and the operational tooling around all of it, in production.

2021 — Jun 2026

Freelance / Contract Web Developer

Independent

30+ production websites built and launched on Webflow and WordPress for healthcare, ecommerce, music and professional-services clients — owned end to end from requirements through launch, hosting and ongoing support.

2023 — 2024

Web Developer

Meptics

Production web development alongside freelance work, ahead of moving into ecommerce and systems engineering full-time.

2020 — 2024

BS, Software Engineering

University of Sahiwal

Foundation in software engineering — most of what is on this site was learned building production systems afterward.

How I work

Before the code

Understand the operation first

Most integration bugs are really misunderstandings of how the business actually works. Reproducing years of undocumented middleware behaviour is an interviewing problem before it is a coding one.

Make failure boring

Idempotent writes, dry runs, flags that default to off, and a blast radius of one board group. The goal is that the worst case is visible and recoverable.

Own it in production

Designing it is half the job. Deploying it, watching it, and being the person who answers when it stops is the other half.

GET IN TOUCH