Backend engineering, from the API to the filesystem.
I build backend systems and developer tools in Go and Rust. My work follows data through the less visible parts of software: persistence, retries, recovery, and expiry.
At Inquinion Labs, I work on backend services and AI workflows. I study computer science at Amrita Vishwa Vidyapeetham, graduating in 2028.
Résumé · Portfolio · LinkedIn · Email
Fade — Files with a deadline
A Linux filesystem in Rust that gives files a time-to-live. Applications use ordinary file operations. Fade enforces expiry at the mount boundary.
Inside a developer-mode mount, the directory specifies the lifetime:
cp report.json ./mnt/24h/
cp cache.tar ./mnt/7d/The design separates expiry from deletion. Expired paths stop resolving through the mount, while physical cleanup waits for a configurable recovery window. SQLite tracks the lifecycle. Startup reconciliation handles interrupted operations, and FUSE integration tests cover expiry, recovery, and remount behavior.
Rust · FUSE · SQLite · Developer preview Implementation · Lifecycle tests · Design and limits
RaftKV — Durability across a cluster
A distributed key-value store I built in Go to study consensus and persistence. It implements leader election, log replication, a checksummed write-ahead log, and snapshots. Reads confirm a quorum before returning data.
The implementation persists votes before replying, detects corrupt log records, and appends an entry in each new leader’s term. The repository includes focused tests and documented limits: fixed membership, no authentication or TLS, and a scope intended for learning.
Go · Raft · Write-ahead logging · Systems study Architecture · Persistence tests · Read guarantees
Paystable — Between payment and fulfillment
An open-source Go service I work on to verify payment evidence before an order moves to fulfillment. It persists webhooks, checks gateway status, and delivers signed callbacks through a PostgreSQL outbox.
A timeout leaves an awkward question: did the merchant process the callback, or never receive it? The delivery contract makes retries explicit and requires merchant-side deduplication. The Scout laboratory explores failure schedules, replays findings, and reduces them to smaller reproducible cases.
Go · PostgreSQL · Payment verification · Open source My contributions · Delivery contract · Failure tests
- The queue you already have PostgreSQL job claims, retries, and the limits of recovery after a worker fails.
- Why 0.1 + 0.2 is not 0.3 Binary representation, rounding, and choosing numeric types with care.
Chess PGN analysis — C++, bitboards, game trees, and alpha-beta pruning. The Art of ASCII — an image-to-character converter in C.
For backend and systems engineering opportunities: get in touch or read my résumé.