AZEEM // SRC.INDX

HYDERABAD, IN // 20:40 GMT+5:30

BACKEND // RUST // WEB3 SYSTEMS

I'm Azeem —
Engineering
resilient, low-
latency systems
for Web3.

Backend engineer building reliable systems for crypto infrastructure and realtime products.

Illustration of Azeem Shaik Illustration of Azeem Shaik

Current Direction

I’m most interested in backend and protocol-facing work where reliability is a product feature, not cleanup work after the fact.

Rust services for performance-sensitive paths

Passkey and auth flows for user-facing products

Crypto infrastructure, solver logic, and systems tooling

Selected Systems

Project Archive

A mix of backend-heavy product work, systems experiments, and infrastructure-oriented builds. The common thread is simple: make the core path dependable, then make it fast.

Pulse Poll Backend

A Rust and Actix-web backend for a realtime polling product. It handles passkey authentication, JWT-protected routes, SSE-powered live updates, and MongoDB-backed poll state in a single service designed for clear boundaries and predictable behavior.

Rust · Actix-web · MongoDB · SSE · WebAuthn

GitHub

Backend
Authentication
Realtime

Pulse Poll

A Next.js frontend for creating, sharing, and participating in polls with instant feedback loops. The implementation centers on a clean interaction model around passkey sign-in and realtime result delivery without overcomplicating the client.

Next.js · TypeScript · Tailwind · Passkeys · Product UI

GitHub

Frontend
Realtime UX
Product

Bloom Filters and Systems Explorations

A lower-level track of work around probabilistic data structures and performance-conscious system design. Projects like this are where I sharpen intuition for memory tradeoffs, lookup-heavy workloads, and the implementation details that shape real production constraints.

Rust · Data Structures · Performance · Systems Thinking

GitHub

Exploration
Algorithms
Foundations

Build the dependable path first.

I like backend and infrastructure work where correctness, latency, and product clarity all matter at the same time.

01

Reliable By Default

I keep the critical path understandable and remove failure-prone complexity early.

02

Measure Before Optimizing

I care about performance, but I trust instrumentation and bottlenecks more than instinct.

03

Ship The Sharpest Slice

I prefer the smallest complete version that proves the product and earns the next iteration.