Backend engineering · selected practice

Systems built to hold up in the real world.

I’m Purushottam Kunwar, a senior backend engineer designing identity, data, and real-time platforms for teams with serious operational stakes.

Practice
2019—present
Systems
8+ in production
Based
Kathmandu · UTC+5:45
Portrait of Purushottam Kunwar
Purushottam KunwarSenior Backend Engineer

For hiring teams

Find the evidence you need.

Filter the practice here, then continue into the full work index without losing your place.

Preparing the filters…

Selected work

Four systems, closely observed.

Architecture, constraints, and outcomes from production work.

01Security / Enterprise

Enterprise SSO Gateway

Federated Identity & Access Platform

Design a gateway that speaks both OAuth 2.0 (PKCE) and SAML 2.0 on the IdP side, while presenting a clean OAuth 2.0 interface to all client applications — with zero downtime across auth flows.

Enterprise Clients
15+
Auth Events/Mo
100K+
OAuth 2.0SAML 2.0JWTPKCE
02Logistics / IoT

FleetPro

Real-Time Logistics Fleet Management

Ingest GPS telemetry from 200+ devices simultaneously over WebSocket, process and store 50K+ location records per day, and render live vehicle positions on a map without melting the database.

Fuel Savings
40%
Vehicles Live
200+
LaravelWebSocketPostgreSQLMapbox
03GovTech / Enterprise

PIMS

Government Pension Information System

Digitize the entire pension lifecycle (enrollment → calculation → disbursement → audit) within strict government security requirements, with data encryption at rest and a complete audit trail.

Faster Processing
70%
Pensioners
10K+
FastAPIPythonMySQLDocker
04Maritime / Marketplace

Yacht Cloud

Maritime Fleet Management Platform

Build a marketplace platform that handles 10TB+ of yacht media (photos/videos/documents), delivers sub-second full-text search across complex yacht specifications, and manages multi-currency transactions.

Yacht Listings
500+
Media Stored
10TB+
GrailsElasticsearchPostgreSQLAWS S3

Showing 4 of 8 documented systems.

Open the complete work index

Working principles

Three rules for durable software.

The habits behind the architecture, from first sketch to quiet operation.

  1. 01

    Clarity before complexity

    Begin with the boundary, the failure mode, and the person who must operate the system.

  2. 02

    Evidence over adjectives

    A useful case study names the constraint, the decision, and the measurable result.

  3. 03

    Built for the handover

    Architecture is only durable when the next engineer can understand, test, and change it.

For founders & product teams

Have a consequential system taking shape?

I help turn ambiguous backend problems into legible architecture, production software, and a path your team can own.

Enter the collaboration page