At CIBC I own the pilot and verification process for a monthly consumer digital banking release, and I wrote the runbook that defines it. Outside the bank, I build: two live applications, two ecosystems, both test-covered.
Each move went closer to the release, and then closer to the build.
Two applications, two ecosystems. Both live, both public, both with test suites and automated deploys.
A Quranic Arabic learning app. A curriculum path, a lesson player, an SM-2 spaced-repetition engine, and prayer-time calculation that runs on the device.
Ships to the home screen rather than the app stores. No review cycle, no developer account, and one release process instead of three.
A local-first personal growth app. No backend, no accounts, no telemetry and no gamification — and a PRODUCT.md that explains why each of those is absent.
An append-only event log, written only by the iPhone. Un-ticking a habit is recorded rather than erased, and a second writer, if one is ever added, merges as a set union.
I did the business diploma first and the IT degree second. The order is why I read a requirement before I read a ticket.
The date stakeholders work to is two days ahead of the true internal deadline. A late partner costs the buffer instead of the release.
Defects raised during pilot go through a structured reproduction checklist before they escalate, so the conversation starts with steps rather than opinions.
The exception path is formal: written justification, a remediation plan, and approval. The cost of skipping verification stays visible instead of quiet.
In my own work that means CI gates, offline tests, and an append-only event log that keeps any future merge a set union by ID. At the bank it means a pilot phase that surfaces two to three defects per release.
Release management, pilot and verification planning, go / no-go facilitation, defect intake and triage, exception handling, stakeholder communications, JIRA, Agile ceremonies.
Used on the consumer digital banking release train — monthly, across web, iOS and Android.
SQL, Oracle via TOAD, Excel reporting, data cleaning, descriptive statistics, visualization, MATLAB.
Used on a twice-daily Treasury reporting cycle, and on a heart-failure dataset analysis at York.
Flutter, Dart, React 19, TypeScript, Vite, Supabase, Dexie / IndexedDB, PWA delivery, spaced-repetition scheduling, unit testing, Playwright, CI pipelines.
Used to ship Tadabbur and Kusuo — both live, both public.
Git, GitHub Actions, JIRA, TOAD, Excel, Figma, VS Code.
Used daily, on both halves of the work.
The subject line is pre-filled, so the next thing you do is type rather than decide how to start.
Open to new roles — Toronto, hybrid, remote, or relocating.