Background & Engineering Principles
I am a product-minded senior backend engineer who cares about failure modes, observability, and data integrity. I have spent the last six years building systems across regulated fintech, high-volume B2B logistics, and restaurant edge infrastructure.
01 // Professional Narrative & Focus
SEC. 5.1I graduated in Computer Science from the FAST National University of Computer and Emerging Sciences in Islamabad. My professional focus evolved from application engineering to distributed backend systems, event streaming, and transactional data modeling.
I am typically brought in when systems transition from early validation into high-concurrency production load — where network disconnects, duplicate payments, hardware failures, or database write locks threaten the stability of the business.
Recently, as founder and solo architect of NoreOS, I designed and shipped an offline-first retail operating system supporting 10 script-correct locales and schema-per-tenant PostgreSQL isolation, protected by a rigid 80% coverage gate across 535 tests and 396 E2E integration flows.
02 // Core Operating Principles
5 INVARIANTS| No. | Core Invariant | Operational Application |
|---|---|---|
| 01 | Correctness over cleverness | Boring, deterministic transaction boundaries always outperform exotic abstractions that fail unpredictably under load. If an edge case is possible, production traffic will trigger it in week one. |
| 02 | Observe everything; recover automatically | Telemetry without automated backoff and self-healing is just a spectator log. Systems must be engineered with explicit retry budgets, dead-letter routes, and automatic state convergence. |
| 03 | Make boundaries explicit | Explicit schema contracts, tenant separation, and bounded contexts prevent cascading failures across services. Never let private internal models leak across service seams. |
| 04 | Prefer boring, measurable systems | Proven primitives (PostgreSQL, BullMQ, Redis, AWS SQS) configured correctly beat unverified trendy technology every time. Architecture is judged by uptime and correctness, not novelty. |
| 05 | Use AI as leverage, not a substitute | Harness code knowledge graphs, sub-agents, and autonomous loops for velocity and comprehensive test coverage, while keeping rigorous human judgment strictly on system architecture and failure modes. |
03 // Technical Competencies & Systems Matrix
STACK MATRIX| Engineering Domain | Technologies & Tooling | Application Scope |
|---|---|---|
| LANGUAGES | TypeScript, JavaScript (ESNext), Java, Go, Python, Dart, Bash / Shell | Core backend services & automation |
| BACKEND & MESSAGING | Node.js, NestJS, Spring Boot, Express, BullMQ, Redis Pub/Sub, Kafka, SSE, WebSockets | Event pipelines, streaming & APIs |
| DATA & STORAGE | PostgreSQL (Schema-per-tenant), DynamoDB, MySQL, MongoDB, Amazon RDS, Redis Caching | Transactional ledgers & document stores |
| CLOUD & INFRASTRUCTURE | AWS (SQS, Lambda, IoT Core, ElastiCache, EC2, S3), Docker, Grafana, Prometheus, Loki, CI/CD | Telemetry, containerization & deployment |
| CLIENT EDGE & UI | React, Flutter (Offline POS), Angular, React Native, Tailwind CSS | Edge point-of-sale & admin interfaces |
04 // Verified Credentials & Continuing Education
ACCREDITATION| Credential / Syllabus | Issuing Organization | Verification |
|---|---|---|
| Microservices: Design Patterns | LinkedIn Learning | Verify ↗ |
| Software Architecture: Domain-Driven Design (DDD) | LinkedIn Learning | Verify ↗ |
| Building Scalable Microservices with TypeScript and Node.js | LinkedIn Learning | Verify ↗ |
| Y Combinator Startup School | Y Combinator (26/26 Modules Complete) | Verify ↗ |