Skip to main document
[ENGINEERING DOSSIER] · SERIES 2026 · REF: MS-BACKEND
CLASSIFICATION: PUBLIC · VERIFIED

MUSTAFA SHAIKH

Senior Backend Engineer — Distributed Systems, Event Architecture & Data Integrity

Islamabad, Pakistan · Remote (UTC+5) · Open to Relocation

// ABSTRACT

I build backend systems that stay correct when the network doesn't. Event-driven services, offline-first sync, and data models engineered to survive production partitions without financial drift. Six years across regulated fintech, B2B marketplaces, and offline retail infrastructure.

01 // Operational Status & Availability

TABLE 1.0
Parameter Specification Details
Engagement Target Senior Backend Engineer / Distributed Systems High-integrity transactional systems
Primary Architecture Event-driven dispatch, BullMQ, offline-first sync, PostgreSQL schemas TypeScript, Java, Go, AWS
Current Deployment NoreOS — Solo-architected offline-first retail operating system Live at noreos.com ↗
Work Mode & Terms Remote (async-aligned worldwide) or Relocation-ready Timezone: PKT (UTC+5)
Direct Channels [email protected] Download Résumé [PDF] ↓

02 // Selected Systems & Architectural Case Studies

Production backend systems engineered under real network partitions and strict data consistency gates.

INDEX 2.0
Ref System & Role Timeline Architectural Scope & Invariants State Dossier
01 NoreOS Founder & Solo Architect 2024 – Present Offline-first retail operating system. Local durable mutation queues, strict schema-per-tenant PostgreSQL isolation, 80% coverage gate (535 tests + 396 E2E flows), 10 script-correct locales. Live (noreos.com) Read →
02 AIO Dispatch Senior Backend Engineer 2025 – Present Real-time at-least-once order delivery across ~500 production devices. BullMQ persistence, Redis Pub/Sub routing, SSE device ACK, 6-hour auto-recovery backoff, 10K connection load test. In Production Read →
03 Fintech & B2B Software Engineer 2022 – 2024 Monolith to microservices migration at Small World Financial Services; centralized i18n platform; serverless PII chat masking and automated dispute resolution at Dastgyr. Production Shipped Read →
FIG. 01 // DISTRIBUTED SERVICE TOPOLOGY
TOPOLOGY MODEL: EVENT-DRIVEN BUS RENDER: STATIC BLUEPRINT
Figure 01: End-to-end event and telemetry topology. Client stations maintain append-only local mutation queues, disburdening the WAN during outages. Central ingress routes state transitions into BullMQ with Redis persistence; transactional reconciliation targets PostgreSQL tenant-isolated schemas with DynamoDB cold snapshots.

03 // Field Notes & Technical Specifications

Essays on failure handling, idempotency design, and offline data models.

View all notes →
Ref Title & Core Invariant Date Length Document
01 At-least-once delivery is easy; exactly-once is a product decision Idempotency Keys · Device ACK · Retry Budgets OCT 2025 6 min read Read →
02 Offline-first is a data-model problem, not a sync button Local Queues · Schema-per-Tenant · Tombstones AUG 2025 8 min read Read →
03 Designing for the six-hour outage Heartbeat Pipelines · AWS IoT · Exponential Backoff JUN 2025 7 min read Read →
// COMMUNICATION PROTOCOL

Have a hard distributed systems problem?

I am available for senior backend engineering roles focusing on reliability, data models, and high-load event dispatch.