Skip to content
View shan305's full-sized avatar
🎯
Focusing
🎯
Focusing

Block or report shan305

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
shan305/README.md

Hi, I’m Zeeshan Ali 👋

Software Engineer with experience building reliable backend and distributed systems across different domains. I focus on designing software that behaves predictably under load, failure, and concurrency, and I value clarity, discipline, and correctness over hype.

I come from a high-responsibility operational background and bring that mindset into engineering: systems should be understandable, auditable, and resilient.


What I Work On

  • Backend & Distributed Systems

    • Designing services that handle concurrency and partial failure
    • Event-driven architectures and asynchronous processing
    • Data consistency, idempotency, and replayability
  • System Design & Infrastructure

    • API design and service boundaries
    • Databases, messaging systems, and caches
    • Containerized deployments and CI/CD pipelines
  • Security-Aware Engineering

    • Authorization and access-control flows
    • Defensive design against stale state and race conditions
    • Audit-friendly system behavior

Selected Projects & Work

  • Distributed System Prototypes

    • Event-based processing pipelines
    • State transition modeling
    • Failure-mode exploration and mitigation
  • Authorization & Consistency Tooling

    • Tools to surface correctness issues caused by caching, delays, or stale state
    • Focus on making hidden bugs observable
  • Production Backend Services

    • REST and message-driven services
    • Database-backed systems with strong data integrity requirements

(Fintech systems are part of my experience, not my entire identity.)


Technical Stack

Languages

  • Java, C++, Python, TypeScript

Backend & Data

  • Spring Boot, Node.js, Django
  • PostgreSQL, MongoDB, Redis
  • Kafka and message-driven systems

Infrastructure

  • Docker, GitHub Actions
  • Linux-based deployments
  • Cloud-hosted services

How I Think About Engineering

  • Prefer explicit state over hidden mutation
  • Make failure modes visible
  • Design for long-term maintainability
  • Build systems that can be reasoned about by other engineers

Connect


GitHub Overview

GitHub Stats

Open to backend, platform, or systems engineering roles across industries.

Pinned Loading

  1. trading-platform-architecture-and-verification trading-platform-architecture-and-verification Public

    Correctness-first trading backend architecture: deterministic execution, ledger invariants, outbox/CQRS, and formal verification artifacts.

  2. Face_Recognition- Face_Recognition- Public

    Building a face recognition system using deep learning with TensorFlow and Keras

    Python

  3. cyclops-ai cyclops-ai Public

    Fully local AI coding agent — plans, edits, verifies, and fixes code using only a local LLM. No cloud, no API keys, no rate limits. 89/100 on real-world benchmarks.

    Python 1

  4. streaming-data-pipeline-kafka- streaming-data-pipeline-kafka- Public

    Real-time market data streaming pipeline demonstrating durability, replay semantics, and correctness under failure using Kafka, Redis, and Postgres.

    Python 1

  5. distributed-transactions distributed-transactions Public

    Distributed transaction patterns in Java : 2PC, choreography saga, orchestrator saga, and outbox pattern.

    Java

  6. rate-limiter rate-limiter Public

    Rate limiter in Java 17. Implements token bucket and sliding window log algorithms with per-client isolation, concurrent load testing, and a zero-dependency HTTP gateway.

    Java