Skip to content
available for backend roles

Ravi Sharma

Backend Engineer · Distributed Systems · Node.js · Kafka · Blockchain

I build backend systems that stay correct under load — event-driven pipelines, fault-tolerant ingestion, and the observability to prove it all works.

ravi@production — zsh
3+
years building backends
30K
RPS handled at the edge
99.9%
uptime across services
20K+
users served on-chain
01about

Backend engineer focused on the parts of a system that have to be right.

I'm a backend engineer with three years of experience building distributed systems that move real money and real-time data. Most of my work lives in the unglamorous layer: Kafka topics, idempotent consumers, reconciliation jobs, and the cert rotation nobody notices until it breaks.

Right now at USquare Technologies I work on blockchain ingestion — long-running BSC listeners that survive RPC flakiness, feeding a real-time pipeline that pushes on-chain events straight to 20K+ users without polling. Before that I built a Kafka KRaft cluster, an ELK observability stack, and the TLS infrastructure behind eight microservices at CoreShield.

I care about systems you can reason about at 3am: clear failure modes, replayable events, and audits that catch the gap before a user does.

currently at USquare Technologies, building blockchain ingestion and settlement systems.

01

Correctness over cleverness

Idempotent handlers, guarded state transitions, and reconciliation jobs that surface the gap before a user reports it.

02

Events over polling

Push pipelines from source to client. Fewer wasted requests, lower latency, and a system that scales with load instead of against it.

03

Observable by default

Structured logs, per-partition lag, and latency percentiles wired up before the first incident, not after it.

02experience

Three years shipping backend systems that carry real traffic and real money.

  1. Backend Engineer @ USquare Technologies

    Jan 2026 — Present

    Building event-driven blockchain infrastructure and the financial engines that sit on top of it.

    • Built fault-tolerant event-driven blockchain ingestion on BSC with Ethers.js, running long-lived listeners with RPC-safe execution for 20K+ active users.
    • Designed real-time chain → backend → client pipelines over Socket.io, replacing polling-heavy architectures with instant push updates.
    • Developed financial and compensation engines with cron-based batch processing, handling 1K+ records per batch at 250 ops per transaction.
    • Ensured correctness through reconciliation tooling — audits, gap detection, backfills — backed by idempotent job design.
    • Node.js
    • Ethers.js
    • BSC
    • Socket.io
    • MongoDB
    • Redis
  2. SDE 1 @ CoreShield Technologies

    Jun 2025 — Jan 2026

    Owned the messaging backbone, TLS infrastructure, and observability pipeline across a microservice fleet.

    • Built a Kafka (KRaft) cluster serving 10K+ users at sub-100ms latency with 99.9% uptime.
    • Established SSL/TLS infrastructure across 8+ microservices, earning an A+ SSL Labs rating with zero-downtime cert rotation.
    • Developed an ELK-based observability pipeline processing 1000+ logs/min while cutting storage costs by 70%.
    • Reduced deployment time from 4+ hours to 15 minutes with a Docker-based microservices setup.
    • Kafka
    • KRaft
    • Docker
    • ELK
    • Nginx
    • CI/CD
  3. Associate Backend Developer @ Zelta Labs

    Apr 2023 — May 2025

    Scaled search and data consistency for a high-traffic product on GCP.

    • Engineered backend services in Node.js, MongoDB, and Elasticsearch, cutting latency by 50% for 30K+ users.
    • Built a Kafka-based CQRS pipeline that resolved 95% of data inconsistencies.
    • Deployed microservices on GCP with CI/CD, sustaining 99.9% uptime.
    • Node.js
    • MongoDB
    • Elasticsearch
    • Kafka
    • GCP
03skills

The tools I reach for, grouped by where they sit in the stack.

core

  • Node.js
  • TypeScript
  • Kafka
  • Redis
  • MongoDB

backend

  • Express.js
  • Spring Boot
  • Socket.io
  • REST
  • CQRS

databases

  • MySQL
  • Elasticsearch
  • MongoDB
  • Redis

cloud & devops

  • Docker
  • GCP
  • CI/CD
  • ELK
  • Nginx

blockchain

  • Ethers.js
  • TronWeb
  • BSC
  • EVM
04projects

Things I built to answer a question I couldn't answer on paper.

API Gateway

Nov 2025 — Dec 2025

High-performance API gateway handling 30K RPS with JWT auth, Redis-backed rate limiting, caching, and circuit breaking.

  • Shared Redis state keeps rate limits and circuit breaker status consistent across instances.
  • Every middleware is instrumented with Prometheus metrics and OpenTelemetry traces.
  • TypeScript
  • Express.js
  • Redis
  • Prometheus
  • OpenTelemetry

Payment Settlement System

May 2025 — Jun 2025

Distributed payment system that processes payments, calculates revenue splits, and automates vendor payouts through an event-driven architecture.

  • Kafka + MySQL design guarantees ACID consistency across service boundaries.
  • Idempotent processing makes replays and retries safe by construction.
  • TypeScript
  • Kafka
  • MySQL
  • Node.js

Voice AI Agent

Real-time voice agent with a streaming Python backend and a low-latency web client for natural spoken conversation.

  • Streaming speech pipeline tuned for conversational turn-taking latency.
  • Deployed as separate frontend and backend services.
  • TypeScript
  • Python
  • WebRTC
  • LLM
05writing

Notes on the systems problems I keep running into.

06education

Where I learned the fundamentals, and a few things I'm proud of.

National Institute of Technology, Srinagar

2019 — 2023

B.Tech in Computer Science

Srinagar, India

Jawahar Navodaya Vidyalaya, Bhilwara

2016 — 2018

Senior Secondary Education

Bhilwara, India

achievements

  • Qualified JEE Advanced, a national-level engineering entrance exam.
  • Secured AIR 3 in the ResoSTEP National Talent Examination.
  • Led a team of 100+ students as House Captain at JNV.
  • Cleared the JNVST national selection exam.
07contact

Got a system that needs to scale, or a role you think fits? Let's talk.

I read every message. The fastest way to reach me is email — I usually reply within a day.