Shashank H RBackend Engineer
all systems operational--:--:-- IST

Portfolio · 2026 edition

Backend engineer at Engati, Bangalore. 2+ years full-time (after a 6-month internship) building Java & Spring Boot services for a high-volume B2B messaging platform.

Short on time? Read the 60-second summary
  1. 01About
  2. 02Stack
  3. 03Experience
  4. 04Work
  5. 05Incidents
  6. 06Playground
  7. 07Contact

I build reliable backends for high‑volume messaging.

~2M api triggers a day · 50k–100k retries. java · spring boot · kafka · redis · mongodb. 45% of failed deliveries saved on 1st retry. open to sde-2 roles · 2026

Skills: Java, Spring Boot, Apache Kafka, RabbitMQ, Redis, MongoDB, Spark, AWS S3, Microservices. Highlights: Open to SDE-2 roles, Employee of the Month ×2, MongoDB certified, CGPA 9.47, Bangalore.

(01) About

based_in
Bangalore, IN
engati
SDE · Jul 2024 → now (2y 3m)
intern · Jan → Jun 2024 (6m)
education
B.E. ISE · CGPA 9.47
awards
Employee of the Month ×2 · “Always at 110%”
status
● open to SDE-2 roles

I joined Engati as an intern in 2024, shipped a full-stack abandoned-cart flow within two sprints, and stayed to build its messaging backend: retry systems that ride out Meta delivery failures, Kafka pipelines that bill customers accurately, and an AI code reviewer my whole team now uses. I like queues, caches, clean APIs and boring deploys. Now I'm looking for my next team.

(02) Stack

8 groups · 26 skills

Stack

The tools I work with, grouped as on my résumé. Pick one to see where I used it.

Languages

Backend

Messaging & Caching

Data Engineering

Databases & Search

Cloud & Infrastructure

AI & LLM

Frontend

Pick a skill to see where I used it. marks those with work on this site.

(03) Experience

Experience

Two roles at Engati, and the degree before them. Each project links to its case study.

  1. Engati · Software Engineer

    Jul 2024 – now · 2y 3m

    Java & Spring Boot microservices for a high-volume messaging platform.

    What I built

    Employee of the Month ×2 · “Always at 110%”

  2. Engati · SDE intern

    Jan – Jun 2024 · 6m

    Shipped a full-stack abandoned-cart flow in 1–2 sprints.

    What I built

  3. B.E., Information Science

    Aug 2020 – Jul 2024 · 4y

    JSS STU, Mysuru · CGPA 9.47/10

(04) Selected work · Engati

5 systems · 4 case studies

Selected work

(05) Incidents

2 write-ups from production

Production incidents

Production problems I tracked down, written up the way a postmortem would be.

INC-01 · MongoDB M20 · production● resolved

Cluster running out of memory

Impact
Memory exhaustion on the production MongoDB cluster.
Cause
Hot queries had no supporting index: ~3,000 documents scanned for every 5 returned.
Fix
Indexed the high-frequency query fields; scan-to-return fell under 100:1.

−60%memory usage (cut by over 60%)

Before: 100%. After: <40%.

INC-02 · FastAPI · embeddings● resolved

A service quietly leaking memory

Impact
Peak memory climbing to 2.5 GB on a critical service.
Cause
String concatenation inside an embedding loop kept allocating new copies.
Fix
Refactored the loop to in-place operations.

2.5 → 1 GBpeak memory

Before: 2.5 GB. After: ~1 GB.

(06) Playground

interactive simulation · illustrative numbers

The retry flow, simulated

An interactive simulation of my Engati auto-retry framework; its numbers are illustrative, not production data. Triggers flow out to Meta; failures come back as webhooks, through the analytics pipeline, to trigger-mvc. Retryable ones wait in RabbitMQ with back-off, then go out again with their original payload, fetched from MongoDB by trackerId. Switch the framework off, or have Meta send a burst of error webhooks, and watch the failure rate.

The simulation needs JavaScript. Read how the framework works →

failure rate · simulated12.0%
in retry queue0
saved by retries0

(07) Contact · Got a role in mind?

Let’s talk