Skip to content
Arjit Kulkarni

● Backend & systems engineer — Bengaluru, India

Systems thathold their shapeunder load.

I build storage engines in C++ and production APIs in Python. Currently shipping backend services as an SDE intern at Reskilll.

Based in
Bengaluru, India
Status
Open to roles
01  Introduction

I care about the parts of a system that only show up under pressure.

I'm a computer science undergraduate at Dayananda Sagar University in Bengaluru, currently shipping backend services as an SDE intern at Reskilll. Most of what I work on sits somewhere between an API and a disk.
The work I'm proudest of is rarely the feature. It's the reconciliation script that retired a manual audit, the index that took 30% off a query, the fault-injection harness that proves a write survives a crash. Correctness under concurrency and failure is the interesting half of the problem, and it's the half that gets skipped.
More about me
C++17PythonFastAPIPostgreSQLTypeScriptNext.jsDockerLinuxGitHub ActionsPyTorchPrometheusCMake
02Selected work
Four systems: one shipped to production, one storage engine, one controlled study, one retrieval service.
All work
03  By the numbers
Developers served by the portal I ship backend for
0+Developers served by the portal I ship backend forReskilll
Average query latency removed from production endpoints
0%Average query latency removed from production endpointsPostgreSQL
Test accuracy from fine-tuning at 5% of CIFAR-10 labels
0.0%Test accuracy from fine-tuning at 5% of CIFAR-10 labelsvs 50.9% scratch
National hackathons won, first place both times
0National hackathons won, first place both timesTeam builds
04What I do
Backend and systems work, with the measurement and delivery practice that makes it stick.
01

Backend Services

REST APIs designed before they are written — clear resources, honest error states, and a data model that still makes sense six months in.

  • FastAPI, Node.js, NestJS
  • REST API design
  • Authentication
  • PostgreSQL schema design
  • Query optimisation
02

Systems Programming

Work close to the machine: storage engines, concurrency, and the memory and I/O behaviour that decides whether a system holds under load.

  • C++17, RAII, ownership
  • Concurrency & multithreading
  • Caching, indexing, persistence
  • File I/O and durability
  • Storage-engine internals
03

Performance & Debugging

Measure, then change. Profiles and query plans decide what gets optimised — never a hunch about where the time is going.

  • Linux perf, profiling
  • PostgreSQL query plans
  • Benchmarking
  • Root-cause analysis
  • ThreadSanitizer, fault injection
All capabilities