Skip to content
faizan/ahmad
Available for Senior / Staff / Tech Lead roles

Faizan Ahmad.
Senior Software Engineer & Technical Lead.

I design and ship real-time web systems at scale — from telemetry platforms streaming off 1,000+ vehicles to production-grade SvelteKit and React architectures that don't buckle under load.

Real-time systemsScalable frontend architectureProduct-driven engineering
View WorkDownload CVContact
Islamabad, Pakistan — Remote
01 · Impact

What I've actually shipped.

Metrics first, narrative second. Every number below comes from production systems I architected, owned, or led.

  • 1,000+
    Vehicles streaming live

    Architected a SvelteKit operator UI that absorbs sustained high-frequency MQTT telemetry — live positions, geofences, clustered markers — without dropped frames.

  • 2,000+
    Vehicles tracked in production

    Shipped React + NestJS frontends for Turing Insights, serving 200+ concurrent operators across Kafka and RabbitMQ pipelines.

  • 9+ yrs
    Remote engineering across EU / US / ZA

    Senior and Tech Lead roles in distributed teams — owning features end-to-end from RFC to production debugging.

  • RFC-led
    Architecture without rework

    Introduced a structured RFC process across a 6-engineer team that measurably reduced architecture-related rework and aligned senior engineers around shared design language.

  • E2E typed
    Zero client/server drift

    Wired PostgreSQL → tRPC → Zod → SvelteKit-superforms → UI, eliminating hand-rolled API clients and validation drift at the boundary.

  • 13
    Clinical modules inside one EHR

    Architected and led a 597-file, 75K+ line TypeScript EHR platform — patient records, multi-provider scheduling, insurance claims, denial management, compliance PDF generation, and MIPS reporting — across a multi-tenant practice environment.

02 · Experience

Roles, owned end-to-end.

Not a timeline — a record of ownership. What the product was, what I ran, the technical bar, and the outcomes that moved the business.

  1. Senior Software Engineer · Operanex

    Kimax Digital — real-time fleet & mining telemetry

    Oct 2024 — Present
    Belgium · Remote
    Owned
    The entire SvelteKit frontend, the MapLibre GL live fleet map, and the typed tRPC ↔ Postgres data layer.
    Challenges
    • Sustained high-frequency MQTT updates feeding a single interactive map without frame drops.
    • End-to-end type safety from Postgres through the UI with zero hand-written API clients.
    • Scaling engineering practice across a distributed 6-engineer team.
    Impact
    • 1,000+ vehicles streaming live into one operator UI.
    • Introduced a structured RFC process that reduced architecture-related rework.
    • Drove a new fleet-operations visibility feature from telemetry analysis → discovery → production.
    Stack
    SvelteKittRPCZodMapLibre GLMQTTKafkaPostgreSQLRedisKubernetes

  2. Technical Lead (Contract) · Aquila EHR

    Multi-practice Electronic Health Record platform

    Jan 2022 — Present
    United States · Remote
    Owned
    Technical direction across a 597-file TypeScript EHR platform — 13 clinical modules covering patient records, scheduling, billing, claims, compliance, and reporting for multi-tenant US medical practices.
    Challenges
    • Modelling complex patient-record relationships — medications, vitals, authorizations, referrals, and billing — without letting the data model drift into a monolith.
    • Insurance claims and denial management with automated reconciliation across multiple payers.
    • Compliance PDF generation (superbills, patient statements, MIPS reports) that has to be exactly right in a regulated domain.
    • FullCalendar-based multi-provider scheduling with resource views, recurrence rules, and real-time appointment state.
    Impact
    • 13 production clinical modules shipped: patient management, scheduling, billing, claims, reports, MIPS, orders, fax inbox, and more.
    • Multi-tenant architecture supporting multiple independent practices from a single deployment.
    • Process and tooling improvements that measurably reduced operational overhead and raised team throughput.
    Stack
    ReactTypeScriptAnt DesignFullCalendarNode.jsPostgreSQLRedispdfmake

  3. Senior Software Engineer · glasc.io

    Turing Insights — fleet tracking & weight analytics

    Jan 2022 — Oct 2024
    South Africa · Remote
    Owned
    Full-stack React + Node features across fleet tracking and weight analytics products.
    Challenges
    • Real-time event detection and alerting over Kafka / RabbitMQ pipelines.
    • Visualizing large operational datasets at interactive latencies.
    • Establishing engineering standards across a growing remote team.
    Impact
    • 2,000+ vehicles tracked in real time, 200+ active operator users.
    • Authored team-wide coding standards, design patterns, and Git workflow conventions.
    • Shipped a stakeholder-approved PoC that advanced into a full production product line.
    Stack
    ReactNestJSKafkaRabbitMQRedisPostgreSQL

  4. Software Engineer · glasc.io

    Real-time event detection & fleet alerts

    Jan 2019 — Dec 2021
    South Africa · Remote
    Owned
    Frontend workflows for high-frequency event detection and large-dataset visualization.
    Challenges
    • High-throughput UI updates sourced from Kafka and RabbitMQ.
    • Driving the full SDLC inside a distributed remote team.
    Impact
    • Owned features from requirements → system design → QA → production debugging.
    Stack
    ReactNode.jsKafkaRabbitMQ

  5. Full-Stack Developer · CreditFix

    CreditPer — data-driven lending platform

    Apr 2017 — Dec 2018
    Islamabad, Pakistan
    Owned
    Responsive React UI translating financial-domain requirements into modular components.
    Challenges
    • Pixel-accurate implementations against evolving design specs.
    • Surfacing technical risk early in a fast-moving sprint cadence.
    Impact
    • Shipped core product surfaces for consumer and SME lending with automated credit decisioning.
    Stack
    ReactNode.jsPostgreSQL
03 · Projects

Case studies, not screenshots.

Each one framed as problem → system design → contribution → outcome. The interesting part is the architecture, not the CSS.

Kimax Digital

Real-time mining & fleet telemetry platform

Oct 2024 — Present
Problem
Mining operators needed a single pane of glass over 1,000+ vehicles streaming live GPS, payload, and state data — with geofence logic and alerting — at frame rates the UI could actually render.
System design
Event-driven ingest (MQTT → Kafka) fans telemetry into Postgres and Redis. A SvelteKit BFF exposes a typed tRPC surface; the operator UI uses MapLibre GL with clustering and binary-encoded position streams so sustained high-frequency updates don't dirty the main thread.
My contribution
Architected and shipped the entire frontend, the live map, and the end-to-end typed data layer. Introduced the RFC process and mentored senior and mid-level engineers through design reviews.
Outcome
A real-time operator UI that holds frame rate under load, plus a visibility feature I drove from telemetry analysis to production.
Scale · 1,000+ vehicles · sustained high-frequency MQTT
SvelteKitshadcn-sveltetRPCZodMapLibre GLMQTTKafkaPostgresRedisKubernetes

Turing Insights

Fleet tracking & payload analytics at scale

Jan 2019 — Oct 2024
Problem
Fleet operators needed real-time location, weight analytics, and alert workflows across thousands of vehicles — with concurrent operator sessions watching different slices of the same event stream.
System design
NestJS services consume Kafka and RabbitMQ streams, persist to Postgres, and cache hot slices in Redis. React frontends subscribe via a thin socket layer and virtualize large lists to keep the UI responsive.
My contribution
Senior full-stack engineer across the product; authored the team's coding standards, design-pattern guidelines, and Git workflow conventions. Mentored juniors to mid-level through pairing and code review.
Outcome
A live-tracking product trusted by operations teams, with a stakeholder-approved PoC that graduated into a new product line.
Scale · 2,000+ vehicles · 200+ active operators
ReactNestJSKafkaRabbitMQRedisPostgres

Aquila EHR

Multi-practice electronic health record platform

Jan 2022 — Present
Problem
US medical practices needed a single platform covering the full care cycle — patient intake, clinical documentation, multi-provider scheduling, insurance billing, denial management, and compliance reporting — without any of those domains bleeding into each other.
System design
597 TypeScript files across 13 feature modules, each with isolated routing and data concerns. Custom REST abstraction (Robin) for consistent API contracts. FullCalendar with resource and recurrence views drives scheduling. pdfmake handles compliance document generation (superbills, MIPS reports, patient statements). Multi-tenant by design — practiceId scopes every query.
My contribution
Technical lead owning the full architecture: data modelling, module boundaries, billing and claims flows, scheduling implementation, PDF generation utilities, and the team's engineering process.
Outcome
A production EHR serving multi-practice environments with insurance claims automation, compliance PDF generation, and a scheduling system built to handle provider-level resource conflicts.
Scale · 13 clinical modules · 597 files · multi-tenant US practices
ReactTypeScriptAnt DesignFullCalendarNode.jsPostgreSQLRedispdfmake

Cossel

B2B ATS & recruitment workflow automation

Oct 2024 — Present
Problem
Recruitment teams needed a scalable ATS that could automate candidate sourcing and hiring workflows without brittle integrations or type drift across the stack.
System design
SvelteKit app with a tRPC surface over Postgres; Zod-first schema contracts so validation lives in one place. shadcn/ui for a fast, consistent design system.
My contribution
Building frontend architecture and the typed API surface.
Outcome
A recruitment platform designed for workflow automation rather than data entry.
Scale · B2B · multi-tenant workflows
SvelteKitshadcn/uitRPCPostgres

CreditPer

Data-driven consumer & SME lending

Apr 2017 — Dec 2018
Problem
Lending platform needed a responsive, modular React UI that could absorb changing credit-decisioning rules without rewriting the frontend every quarter.
System design
Component-driven React architecture over a Node + Postgres backend; financial-domain requirements modeled as composable UI primitives.
My contribution
Built the React UI end-to-end; integrated third-party libraries and delivered pixel-accurate implementations from design mock-ups.
Outcome
A maintainable frontend that survived repeated decisioning-logic changes.
Scale · Consumer + SME lending
ReactNode.jsPostgres
04 · Technical

The stack I reach for.

Grouped by concern, not by recency. Everything here has shipped to production under load.

Frontend Architecture

  • SvelteKit
  • React
  • Next.js (App Router)
  • TypeScript
  • Redux
  • shadcn-svelte
  • shadcn/ui
  • Tailwind CSS
  • MapLibre GL

Backend & APIs

  • Node.js
  • tRPC
  • NestJS
  • Express
  • REST
  • Zod
  • PostgreSQL
  • Redis

Real-Time Systems

  • MQTT
  • Kafka
  • RabbitMQ
  • Event-driven architecture
  • WebSockets
  • High-frequency UI updates

DevOps & Infra

  • Docker
  • Kubernetes
  • CI/CD pipelines
  • Git workflows

Tools & Practices

  • System design
  • RFC process
  • Code review
  • Technical mentorship
  • Agile / Scrum
  • Sprint planning

AI Tooling

  • Claude API
  • GitHub Copilot
  • Cursor
  • AI-assisted code review
  • Prompt engineering
05 · Approach

How I think about systems and teams.

Architecture is a communication problem first. The code is the artifact, not the goal.

  • 01

    RFC-driven architecture

    Introduced and ran a structured RFC process across a distributed 6-engineer team — reducing architecture-related rework and giving senior engineers a shared language for design decisions.

  • 02

    Mentorship that compounds

    Multiple direct mentees have progressed from junior → mid-level under my review. I prefer pairing and written design reviews over one-off feedback because the artifacts outlive the conversation.

  • 03

    Product-shaped engineering

    I use telemetry and usage data to find product gaps, not just to measure them. At Operanex I drove a fleet-operations visibility feature from data analysis through to production.

  • 04

    System design & code review

    I review for the invariants, the failure modes, and the rollback path — not for style. Design critiques run against explicit trade-offs, not preference.

The best architecture decisions are the ones you can reverse cheaply. My job isn't to be right the first time — it's to keep the team fast when we're not.
— System Thinking, in one line
06 · Contact

Building something real-time,
at scale, that has to work?

I take on Senior, Staff, and Tech Lead roles — full-time remote, or focused contracts where ownership matters more than hours.

Email
faizann.ahmad1@gmail.com
GitHub
@iamfaizanahmad
LinkedIn
iamfaizanahmad