Skip to content

render --portfolio

4 case studies · 8 further builds · 4 cv variants

Faran Ali

Faran Ali

Islamabad, Pakistan

Principal Software Engineer Software Architect Platform Modernization & Audits

Ten years building and modernizing multi-tenant platforms across logistics, healthcare, transportation and media.

Hands-on Principal Software Engineer and Software Architect with 10+ years taking technical ownership of incomplete, unstable, or fast-growing SaaS products: auditing what already exists, producing a prioritized remediation roadmap, and leading the modernization while staying in the code.

Owns architectural roadmaps, platform hardening, and release safety across a multi-product portfolio spanning logistics, transportation, healthcare, aviation services, and media — driving one delivery team day to day and mentoring a second across backend, platform, and cross-platform mobile.

Currently
Hands-on architecture owner, two delivery teams
Focus
Platform audits, modernization, multi-tenant SaaS
Experience
10+ years, 5 companies

cat ai-practice

AI-accelerated engineering

I build the tooling, not just the prompts.

Agentic engineering is how I deliver, not something I experimented with. I author the skills, MCP servers, agents and automations my teams use, and apply them across the whole lifecycle while keeping architecture, security and financial correctness under human ownership.

What I build

  • Custom agent skills encoding domain and codebase context
  • MCP servers exposing internal systems to agents safely
  • Plugins, subagents and reusable delivery automations
  • Verification harnesses so agent output is provably checked

Where it applies

  • Discovery and architecture exploration
  • Implementation, refactoring and debugging
  • Test generation and adversarial review
  • Documentation, release prep and runbooks

What it changes

  • Work that took months now ships in weeks
  • Legacy codebases become tractable in days, not quarters
  • Review and test coverage rise rather than fall
  • Architectural judgement stays with the engineer

Proof, not projection

A production move-request platform for a Saudi public-sector housing initiative, delivered end to end: React 19 and TypeScript against a typed API contract, Laravel with token-based SPA authentication and scoped authorization, HMAC-signed idempotent webhooks into SAAML's fulfilment engine, national-address and mapping integration, bilingual RTL throughout, and staged card payments designed to recover from uncertain gateway outcomes without double-charging.

Toolchain

  • Claude Code
  • Codex
  • ChatGPT
  • Gemini
  • Agentic development
  • Custom skills & agents
  • MCP servers
  • AI plugins
  • Workflow automation
  • AI-assisted testing
  • Prompt engineering

Every agent-assisted change goes through the same review, tests and release gates as hand-written code. AI raises throughput; it does not get a vote on architecture, security or correctness.

git log --career

Career Progression.

Scroll the years. Longer roles unfold into the products, platform work, and delivery systems that filled them.

portfolio ownership

Apr 2026 — now · chapter 01/03

Principal Software Engineer

Elityx

Architecture owner across a multi-product portfolio

engagement
Full-time · product and platform ownership
team
Two delivery teams · 10 engineers · 2 QA
working with
Founders and executives

Own the roadmap. Stay in the code.

Architecture ownership across backend, platform, and cross-platform mobile work, with direct responsibility for the highest-risk implementation.

  • Audit inherited products across architecture, multi-tenancy, authorization, APIs, webhooks, credentials, and delivery risk.
  • Turn the findings into a sequenced modernization roadmap, then personally handle the fixes where failure would cost the most.

work / focus

  • Architecture roadmap
  • Platform hardening
  • Release systems

technology

  • Laravel
  • React
  • TypeScript
  • AWS
  • Terraform
  • Docker
  • CI/CD

logistics architecture

Apr 2026 — now · chapter 02/03

Principal Software Engineer

Elityx

Architecture owner across a multi-product portfolio

engagement
Full-time · product and platform ownership
team
Two delivery teams · 10 engineers · 2 QA
working with
Founders and executives

SAAML: turn logistics rules into a platform.

A multi-tenant logistics platform connecting commerce channels, contract pricing, carrier selection, compliance, shipment lifecycles, and financial operations.

  • Designed a provider-neutral carrier layer so integrations can change without rewriting shipment workflows.
  • Made contract rules, routing decisions, state transitions, and settlement traceable and safe to retry.

work / focus

  • SAAML
  • Carrier aggregation
  • Pricing engine

technology

  • Laravel
  • PostgreSQL
  • Redis
  • Horizon
  • Reverb
  • AWS

zero to one

Apr 2026 — now · chapter 03/03

Principal Software Engineer

Elityx

Architecture owner across a multi-product portfolio

engagement
Full-time · product and platform ownership
team
Two delivery teams · 10 engineers · 2 QA
working with
Founders and executives

Sakani: ship the complete journey.

Sole ownership of Sakani, a Saudi public-sector housing product from React and TypeScript screens through Laravel APIs, contracts, staged payments, and fulfilment.

  • Built Arabic-first RTL journeys with SPL National Address, Google Maps capture, bilingual contracts, and guided inventory flows.
  • Handled uncertain gateway outcomes with signed, idempotent webhooks so retries cannot double-charge or lose traceability.

work / focus

  • Sakani
  • Housing program
  • Payments

technology

  • React 19
  • TypeScript
  • TanStack
  • Zod
  • Laravel
  • Sanctum
  • HyperPay

technical leadership

Oct 2022 — Mar 2026 · chapter 01/03

Software Architect

Integrated IT Solutions

Technical Team Lead through 2024 · promoted in 2025

engagement
Full-time · team lead → software architect
team
5–8 developers · 2 QA · designer
working with
CTO and CEO

Raise the delivery system, not only the code.

Owned architecture, delivery, infrastructure, and engineering standards across a varied product portfolio while leading a multidisciplinary delivery team.

  • Connected architectural decisions to delivery sequencing, QA, infrastructure, and the constraints founders and clients actually felt.
  • Made AI-augmented development a repeatable team practice with review and verification still built into the path.

work / focus

  • Architecture
  • Team systems
  • AI-augmented delivery

technology

  • Laravel
  • Vue
  • Nuxt
  • Redis
  • Docker
  • AWS
  • CI/CD

transportation operations

Oct 2022 — Mar 2026 · chapter 02/03

Software Architect

Integrated IT Solutions

Technical Team Lead through 2024 · promoted in 2025

engagement
Full-time · team lead → software architect
team
5–8 developers · 2 QA · designer
working with
CTO and CEO

NEMT: model the operation end to end.

A multi-tenant transportation-management system for U.S. providers, designed around the complete trip lifecycle rather than isolated dispatch screens.

  • Covered broker intake, dispatch, driver and vehicle operations, compliance capture, proof of trip, and billing readiness.
  • Kept tenant boundaries and operational rules explicit while the product and its integrations continued to grow.

work / focus

  • NEMT
  • Dispatch
  • Billing readiness

technology

  • Laravel
  • React
  • PostgreSQL
  • Redis
  • Docker

healthcare saas

Oct 2022 — Mar 2026 · chapter 03/03

Software Architect

Integrated IT Solutions

Technical Team Lead through 2024 · promoted in 2025

engagement
Full-time · team lead → software architect
team
5–8 developers · 2 QA · designer
working with
CTO and CEO

Thrive: four portals, one permission model.

A healthcare operations platform spanning agency administration, caregiver work, family access, and platform governance on a shared API.

  • Designed row-scoped tenancy plus a permission matrix guarding routes, actions, and individual fields.
  • Connected care plans, scheduling, clock-in, daily logs, exceptions, alerts, and timesheet approval into one auditable workflow.

work / focus

  • Thrive Independently
  • Multi-portal SaaS
  • Care operations

technology

  • Laravel 12
  • Vue 3
  • Quasar
  • Pinia
  • JWT
  • stancl/tenancy

performance and stability

Sep 2021 — Sep 2022 · chapter 01/01

Senior Software Engineer

Turing

Remote product engineering on a high-volume platform

engagement
Full-time · distributed product team
scope
Performance · stability · modernization

Make a high-volume platform boring under load.

Performance and production-stability work on AcquireCrowd, followed by a safer modernization path for its legacy Laravel application.

  • Introduced Redis clustering and removed costly N+1 query paths from high-traffic workflows.
  • Modernized the application through framework upgrades, Inertia.js, and clearer modular boundaries without betting delivery on a rewrite.

work / focus

  • AcquireCrowd
  • Redis
  • Legacy modernization

technology

  • Laravel
  • Redis
  • Inertia.js
  • MySQL
  • Lucid architecture

full stack products

May 2020 — Aug 2021 · chapter 01/01

Senior Full Stack Engineer

Integrated IT Solutions

Returned later as Technical Team Lead

engagement
Full-time · end-to-end product delivery
scope
Frontend modernization · backend domains · integrations

Rework live products without freezing delivery.

Frontend modernization and backend domain work across healthcare and media products, including the first versions of systems that remained in active use.

  • Rebuilt The Key Clinic around Vue 3, Quasar, and cleaner Laravel boundaries, with Xero, Twilio, Cliniko, and payment integrations.
  • Delivered the initial Rasenfunk platform with Nuxt and Laravel, then returned in the later role to improve its structure and performance.

work / focus

  • The Key Clinic
  • Rasenfunk
  • Laravel + Vue

technology

  • Laravel
  • Vue 3
  • Quasar
  • Nuxt
  • Xero
  • Twilio
  • Cliniko

delivery foundations

Jul 2016 — Mar 2020 · chapter 01/01

Software Engineer

Seven Koncepts

The foundation years

engagement
Full-time · client product delivery
scope
APIs · commerce · payments · operations tooling

Learn the whole product surface.

Four years moving from individual features to complete Laravel, Vue, and WordPress products across APIs, commerce, payments, and operations tooling.

  • Worked across backend, browser UI, deployment, third-party APIs, and the operational edges that decide whether a feature survives production.
  • Integrated Cybersource and PayPal while building the delivery range that later made architecture ownership practical rather than theoretical.

work / focus

  • Laravel
  • Vue
  • E-commerce

technology

  • Laravel
  • Vue
  • WordPress
  • MySQL
  • Cybersource
  • PayPal

ls engagements

Three ways teams bring me in.

For founders and CTOs

"It works, but nobody wants to touch it."

Platform audit & recovery

I enter an unfamiliar SaaS platform and assess it end to end: architecture, codebase, multi-tenancy and authorization, API and webhook security, credential handling, performance, technical debt and release safety.

  • Tenant isolation and authorization review
  • API, webhook and credential handling
  • Performance and reliability assessment
  • Production readiness and release safety

You get
A prioritized remediation roadmap, ordered by risk and effort — then I lead or personally execute the fixes.

read more

For early-stage teams

"We need this shipped, and we need it to hold."

Zero to one delivery

Sole or lead engineer on a new product, from architecture through production. Frontend, backend, payments, integrations, localization, infrastructure and release engineering — without waiting for a team to be hired first.

  • Architecture chosen for the next 18 months, not the demo
  • Payment and integration flows designed to recover
  • Automated tests written alongside, not after
  • Atomic releases with health checks and rollback

You get
A production-grade product with tests, runbooks and a deployment path someone else can operate.

read more

For teams carrying legacy

"Every release is a gamble."

Modernization & delivery repair

Incremental modernization of systems that cannot be paused: retiring dead surfaces, consolidating fragmented frontends, restructuring domains, and rebuilding the pipeline that ships them.

  • Dead code and obsolete surfaces retired safely
  • Domain boundaries restructured incrementally
  • CI cut from ~10 minutes to under 2
  • Atomic, self-verifying releases with automatic rollback

You get
A measurably faster, safer platform and a delivery process the team trusts — achieved without a rewrite.

read more

cat how-i-operate

Technical leadership from inside the work.

I'm most useful as a hands-on technical authority: owning architecture, carrying the highest-risk implementation personally, and raising a team's output through review, standards, and reusable foundations — not through headcount or ceremonies.

Direction ships as code

Decisions are moved by evidence, prototypes, and pull requests — not slide decks. The hardest problem on the board is mine: payments, tenancy, integrations, release safety.

Teams get leverage

Code review, mentoring through real implementation, unblocking, and standards that outlive the sprint. One team led day to day; a second mentored as needed.

Executives get straight answers

On feasibility, risk, cost, and whether a feature should be built at all — reporting to founders, CTOs, and CEOs while remaining a practitioner.

I take full technical accountability — architecture, delivery risk, production. I don't take people administration as a primary function; my leverage is engineering, not management.

ls -la ~/projects

Four builds worth walking through.

01 / 04 ~/projects/elityx/saaml

SAAML

Multi-tenant logistics platform. Commerce channels in, external carriers out, with pricing, compliance and money movement in between.

  1. rules engine — Evaluates contracts, zones, districts, service levels and SLA before selecting a carrier.
  2. carrier layer — Provider-neutral drivers, so a partner is added without touching shipment code.
  3. lifecycle — Request, accept, dispatch, reconcile — idempotent at every hop.
  4. settlement — Rate cards, COD handover, ledgers and payouts reconciled against the platform.
  • Laravel
  • PostgreSQL
  • Redis
  • Horizon
  • Reverb
  • AWS
forwarding engine evaluating

SHP-40219 · Riyadh → Jeddah · 18.4 kg

  • zone RUH-central → JED-north
  • service level next-day
  • sla ≤ 24h remaining
  • contract slab 10–25 kg · SAR 24.50
carrier selected provider-neutral driver · idempotency key set
requested accepted dispatched reconciled
02 / 04 ~/projects/personal/jelly

JellyJar

A Chrome extension records the tab, console and network; a queue turns the archive into a reviewable session with video and evidence.

  1. capture — MV3 service worker and offscreen recorder write a local draft before anything uploads.
  2. pipeline — Queue workers and ffmpeg turn the archive into video plus queryable console and network records.
  3. review — Triage, comments, activity history and signed external shares.
  4. limits — Archive size, retention and seats enforced server-side, not in pricing copy.
  • NestJS
  • Prisma
  • BullMQ
  • ffmpeg
  • S3
  • React 19
  • Chrome MV3
tab recording console + network captured
local draft archive 12.4 MB · nothing uploaded yet
queue worker ffmpeg transcode · records extracted
session console network

checkout fails on step 3 · 00:42

TypeError: cannot read property 'total' of undefined

POST /api/cart/confirm → 500

retention, archive size and seats enforced server-side signed external share
03 / 04 ~/projects/elityx/sakani

Sakani

Move-request platform for a Saudi public-sector housing initiative, built end to end from address capture through contracts, staged payments and fulfilment.

  1. wizard — Addresses, inventory, services and media captured across a guided multi-step flow.
  2. rtl — Arabic-first layout mirroring, not translated strings inside a left-to-right shell.
  3. payments — Staged deposit and balance over mada and Apple Pay, confirmed server-side.
  4. recovery — Uncertain gateway outcomes resolve without double-charging or losing traceability.
  • React 19
  • TypeScript
  • TanStack
  • Zod
  • Laravel
  • Sanctum
ltr move request
  1. 1. address
  2. 2. inventory
  3. 3. services
  4. 4. review

pickup

short address RRRD2929 · resolved via national address

items

14 items · assembly on 3 · 2 photos

deposit

captured

balance

on completion

uncertain gateway outcome → reconciled, never double-charged
04 / 04 ~/projects/integrated-it/thrive-independently

Thrive Independently

Multi-portal healthcare operations platform covering agency operations, caregiver workflows, a family-facing portal and platform governance, with a permission matrix guarding every route, action and field.

  1. multi-portal — Four distinct surfaces on one API, row-scoped per agency.
  2. permissions — Role and permission matrix guards every route, action and field, giving fine-grained control over access.
  3. care plans — Draft, approve, revise and clone, with a full audit trail.
  4. execution — Caregiver clock-in, shift exceptions, daily logs, alerts and timesheet approval.
  • Laravel 12
  • stancl/tenancy
  • JWT
  • Vue 3
  • Quasar
  • Pinia

Operations

admin · supervisor

Family

scoped visibility

Governance

tenants · plans

permission matrix
ability admin supervisor caregiver family
care-plan.approve
shift.clock-in
timesheet.approve
patient.view
every plan revision recorded with actor, timestamp and diff

audit acme-admin

What inherited software looks like on the way out.

The same screen at both ends of a modernization. Scroll it, or scrub the toggle — the interesting frame is the middle, where both design systems are live at once.

acme-admin.internal/reports.php?id=4
ACME Administration System v2.1 Welcome, admin  |  Help  |  Log out

Operations Dashboard

Last refresh: 09:31:04
Runtime Error: ReportScheduler.aspx failed to load. Object reference not set to an instance of an object.
Today 1,284
Failed jobs 17
Pending 246
Requests by hour

06:00   12:00   18:00

Batch queue
ID Process Started Status
1041 Monthly export 09:28 Running
1042 Reconcile batch 08:54 ERROR
1043 Ledger snapshot 08:51 Timeout
1044 Archive cleanup 07:10 Waiting
A Acme Operations production 3 FA

Operations overview

Live platform health and processing activity

Last 24 hours Export

Throughput

12.4k +18%

Success rate

99.98% +0.7%

p95 latency

1.2s -42%

Queue depth

24 normal

Requests processed

Successful and retried jobs

+18.4%

Recent runs

View all 38
Monthly export Completed 1.2s
Reconcile batch Recovered 3.8s
Ledger snapshot Completed 0.4s
lighthouse
34
bundle
1900kb
errors
12
coverage
0%

ls ~/projects --all

Also built.

cat stack

What I reach for.

Backend
PHP Laravel NestJS Node.js Domain-Driven Design
Frontend
TypeScript React 19 Vue 3 Nuxt Quasar Tailwind TanStack
Data & infra
PostgreSQL MySQL Redis Horizon BullMQ AWS GCP Terraform Docker
Practice
Architecture audits Multi-tenancy CI/CD Pest Vitest Playwright Agentic delivery

cv --list

Four CVs, one set of facts.

cat contact

Hiring for something that needs owning?

Based in Islamabad, working with teams across KSA and the GCC. Email is the fastest route.