Backend engineering
Designing clear, tested APIs and services that remain understandable as the product grows.
Python · Django · FastAPI · Rust · AxumAbout
Most of my work lives behind the interface: APIs, queues, databases, and pipelines that need to keep working after the demo is over.
I spent five years at Intensel building backend and data infrastructure for climate-risk products. I worked across architecture, delivery, production support, code review, mentoring, and the investigations that begin with “why is this suddenly slow?”
These days I'm writing benchmark-driven notes and continuing to explore databases, vector search, and practical systems work.
Expertise
Designing clear, tested APIs and services that remain understandable as the product grows.
Python · Django · FastAPI · Rust · AxumMaking large geospatial and analytical datasets practical to ingest, index, query, and maintain.
PostgreSQL · PostGIS · Redis · DuckDB · SQLBuilding queues and worker pipelines with deliberate retry, scheduling, and failure-recovery behavior.
AWS SQS · Dask · workers · job orchestrationTaking work from an ambiguous requirement through delivery, observability, incident investigation, and support.
AWS · Docker · Kubernetes · CI/CD · CloudWatchSelected work
Owned backend architecture and data infrastructure for a climate-risk product used by enterprise customers across 10+ countries, from technical design through rollout and production support.
Backend architecture · product infrastructureBuilt ingestion, validation, indexing, and query workflows that balanced large batch workloads with low-latency spatial access.
2.3B+ records · 1.8 TB PostGISBuilt and operated GPM IMERG ingestion with a 10-minute availability buffer and Amazon S3 delivery for risk monitoring and alerts.
Half-hourly source data · near-real-time deliveryBuilt an asynchronous HTTP API around Redis to explore connection pooling, low-latency request handling, and explicit backend resource management.
Rust · Axum · Tokio · RedisExperience
Software Engineer · Backend & Data Infrastructure
I owned backend architecture and data infrastructure across APIs, distributed workers, queues, databases, and deployments. The role grew from implementation into technical design, production ownership, code review, and mentoring engineers.
Bachelor of Computer Science · University of Mumbai · 2020
Writing
A benchmark-driven look at how one PgBouncer process became a CPU bottleneck, how multiple processes scaled it, and where the next limit appeared.
A benchmark-driven look at what happens when vector compression moves from 10M scale to 100M scale.
A benchmark-driven look at how much the PostgreSQL write path matters when loading large datasets.
Contact
I'm always happy to compare notes. Reach me at karan@jadhav.dev.