Available for senior backend & platform roles

Shubham Divesh · Backend systems · Product engineering

Backend systems
built to scale,
recover and evolve.

Senior backend engineer with seven years of production experience across APIs, distributed workflows, search, caching, real-time systems, background processing and cloud delivery. I turn complex product requirements into reliable, maintainable platforms.

Explore selected work
GitHub LinkedIn
7 yearsproduction engineering
40%faster media processing
99.9%notification reliability
4 teamscareer progression

Professional experience

Seven years of measurable production work.

A career path from application engineering to ownership of performance-critical backend systems.

Independent work

Products built beyond the day job.

Supporting evidence of end-to-end ownership across product architecture, deterministic computation and reusable infrastructure.

01Production adventure intelligence platform

SagaVoya

A full-stack trek planning and preparation product spanning goals, training, GPX analysis, readiness, expeditions, progression and storytelling—designed and shipped from schema to deployment.

NestJS + CQRSEvent sourcingBullMQ queuesMeilisearchAI subsystemsLazpho protection
38BACKEND MODULES
57PRODUCT ROUTES
4CORE SERVICES
1END-TO-END OWNER

Architecture laboratory

See the decisions operate.

The technical depth is available when you want it—without forcing every visitor through a wall of implementation detail.

SagaVoya

CQRS, durable queues, search and AI subsystems connected through explicit boundaries.

Lumora

A deterministic Python core separated from networked product services.

Lazpho

A compact resilience library exploring bounded work, cancellation and observability.

Engineering judgment

Why, not only what.

Technology choices become useful evidence when the constraint, trade-off and resulting behavior are visible.

Decision 01

Durability before convenience

AI generation, recommendations, achievements and document exports leave the request lifecycle and run as observable jobs with retries and failure states.

Constraint → choice → trade-off → observable result

Capabilities

Production depth across the stack.

Grouped by the problems I solve—not an undifferentiated wall of technology badges.

Distributed systems

Concurrency control, backpressure, queues, events, failure recovery and service boundaries.

CQRSEvent sourcingBullMQWebRTC

Backend engineering

Production Node.js and Python services with secure, observable APIs.

Node.jsNestJSFastAPIRESTGraphQL

Data & discovery

Models and indexes chosen around product access patterns rather than fashion.

MongoDBPostgreSQLRedisElasticsearchMeilisearch

Delivery & operations

From local design to deployment, metrics, queues and failure diagnostics.

AWSDockerCI/CDPrometheusVercelRender

AI-native engineering

AI accelerates the work. Judgment stays accountable.

I use AI tools as part of a disciplined engineering loop—not as a substitute for architecture, validation or ownership.

HUMAN CONTROL PLANE
Scope · constraints · architecture · tests · release
01

Implementation accelerator

Codex

Repository-scale exploration, implementation, refactoring, test execution and verification—always against explicit acceptance criteria.

02

Design and review partner

Claude Code

Alternative analysis, architecture critique and a second perspective on complex changes before they become release decisions.

03

Production capability

LLM integrations

Grounded context, structured outputs, asynchronous execution, validation, observability and fallbacks around probabilistic behavior.

Delivery loop

A model is one component—not the system.

01Problem framing
02Context contract
03Assisted implementation
04Tests & review
05Observable release
Illustrated portrait of Shubham as a hiker working on a laptopENGINEER · EXPLORER

Beyond the terminal

Mountaineering
Trekking
Swimming
Badminton
Cycling

About the engineer

Calm systems begin with clear decisions.

I care about the choices that make software trustworthy after launch: explicit boundaries, bounded work, observable failure and data models that fit the product.

I use Codex and Claude Code as engineering accelerators for codebase exploration, implementation, refactoring and review. I keep ownership of problem framing, architecture, safety constraints, testing and every release decision.

I also integrate LLM capabilities into products through explicit contracts: structured outputs, grounded context, asynchronous jobs, observability, fallbacks and deterministic validation around probabilistic models.

The outdoor disciplines matter for the same reason engineering does: preparation, honest feedback and good judgment under changing conditions.

Let's build something durable

Looking for senior backend or platform engineering ownership?

I'm open to roles where system design, reliability and end-to-end product thinking matter.