Building backend infrastructure, concurrent systems, developer tooling, and security-focused software.
Backend Infrastructure Engineer focused on systems where correctness, concurrency, reliability, and security actually matter.
I work primarily with Node.js, TypeScript, Java, PostgreSQL, Redis, and Docker, and I enjoy going below the API layer to understand how systems behave under concurrency, failure, partial state, and adversarial inputs.
Currently contributing to Reticle, InsForge, and Apicurio Registry, while building real-time and systems-oriented projects of my own.
"Don't just fix the symptom. Understand the system, validate the assumption, and then implement the smallest architecture that makes the behavior correct."
Reticle Repository • TypeScript • Node.js • MCP • Playwright
As an active contributor, I work on the benchmark, verification, and browser-state infrastructure behind Reticle.
| Contribution | Engineering Work |
|---|---|
| #439 | Fixed Windows benchmark process orchestration, including pnpm.cmd, platform-aware process teardown, and Windows-safe child-process handling. |
| #570 | Built the MCP tool profiler harness with dynamic tools/list discovery, fixture orchestration, safe tool execution, and latency/error/payload telemetry. Shipped with Reticle v2.12.0. |
| #580 | Built regression enforcement around benchmark invariants, detecting errors, timeouts, protocol crashes, missing tools, and payload regressions while treating latency as advisory. |
| #735 | Designed opt-in seedStorage for reticle_lease, supporting pre-navigation cookies, localStorage, and sessionStorage with origin isolation, one-time injection, and concurrent acquisition protection. |
| #865 | Fixed a causal verification flaw by evaluating STATE predicates before actions, preventing pre-existing state from being falsely attributed to an action. |
- Validated 30/30 advertised MCP tools through the benchmark harness.
- Added deterministic regression checks for errors, timeouts, protocol crashes, missing tools, and payload regressions.
- Added pre-navigation browser state injection while preserving origin and context isolation.
- Added regression coverage for causal verification correctness.
- Validated 15/15 targeted, 72/72 parity, and 288/288 honesty tests for the STATE verification fix.
Apicurio Registry • Java • Quarkus • JSON Schema • Maven
My contribution focused on correctness in the MCP tool backward-compatibility checker.
| Issue / PR | Engineering Work |
|---|---|
| #9178 | Identified a correctness gap where schema-breaking MCP tool changes could pass silently due to incomplete type/null handling. |
| #9181 | Developed the direct fix with 19 targeted tests, iterating through maintainer review on union types, property-type removal, and untyped-to-typed transitions. |
| #9301 | Filed the architectural follow-up after maintainer feedback identified the existing JsonSchemaDiffLibrary as the better abstraction for JSON Schema compatibility. |
| #9368 | Developed the redirected implementation across Maven modules, replacing approximately 170 lines of shallow comparison logic with delegation to JsonSchemaDiffLibrary and adding regression coverage for JSON Schema compatibility semantics. |
The work evolved from a direct correctness fix into a deeper architectural implementation after maintainer review. The final PR was closed because the implementation scope was reserved for the LFX mentorship term.
InsForge • YC-Backed • TypeScript • Node.js • PostgreSQL
My work spans backend infrastructure, security hardening, database performance, configuration architecture, and reliability.
| PR | Contribution |
|---|---|
| #1795 | Built Phase 1 of a PostgreSQL-native durable messaging queue with outbox/DLQ persistence, LISTEN/NOTIFY + polling fallback, atomic SKIP LOCKED claims, lease recovery, retries/backoff, idempotency, and duplicate-delivery safeguards. |
| #1626 | Hardened file uploads against stored XSS using magic-byte content detection, unsafe MIME handling, nosniff, forced downloads, and upload content-type pinning; added 22 regression tests. |
| #1660 | Fixed a timing side-channel in admin authentication using pre-hashing and crypto.timingSafeEqual(). |
| #1807 | Restricted internal PostgreSQL, PostgREST, and Deno service ports to 127.0.0.1 to prevent unintended public exposure. |
| #1811 | Hardened canonical cloud deployment Compose configurations by restricting PostgreSQL, PostgREST, Deno, and auth ports to loopback. |
| #1494 | Reduced repeated database metadata scans using a 60-second in-memory table-count cache with batched exact-count fallback. |
| #1519 | Bounded table-count caching to prevent unbounded memory growth. |
| #1526 | Added AI token-cost safeguards and promise-based cache stampede prevention for concurrent model requests. |
| #1541 | Externalized AI token limits and added upstream failure protection with circuit-breaker behavior and stale-cache fallback. |
| #1351 | Centralized 55+ environment-variable reads across 21 files into a typed AppConfig, with 49 tests covering configuration behavior and regressions. |
| #1443 | Improved backend type safety, standardized OAuth errors, and introduced OpenAPI deprecation/sunset metadata. |
The messaging project started from a feature request I proposed after investigating the existing infrastructure and identifying the lack of a durable background-job system.
The architecture was developed collaboratively with the maintainers:
Application
│
▼
Transactional Enqueue
│
▼
PostgreSQL Durable Queue
│
├──────────────► LISTEN / NOTIFY ───────► Worker
│ │
│ ▼
│ Atomic Claim
│ + Lease
│ │
│ ▼
│ EmailService
│ │
│ ┌────────────┴────────────┐
│ ▼ ▼
│ Sent Retry / Backoff
│ │
│ ▼
│ Dead Letter
│
└──────────────► Polling / Reconciliation
The Phase 1 implementation intentionally focuses on infrastructure rather than adding SMS, Push, or a new public messaging SDK. PR
- PostgreSQL-backed durable jobs.
- Transactional enqueue.
- LISTEN/NOTIFY for low-latency wake-up.
- Polling fallback for missed notifications.
- FOR UPDATE SKIP LOCKED for concurrent workers.
- Claim tokens and lease-based recovery.
- Retry scheduling with exponential backoff.
- Dead-letter handling.
- Idempotency and duplicate-delivery safeguards.
- Reconciliation for expired/orphaned jobs.
- Graceful worker lifecycle handling.
- Existing EmailService as the first delivery handler.
Contributed a small refactor to a shared discrete-calculation module used by the molecular simulation force-field implementation, replacing direct private-field access with a public accessor.
Node.js • TypeScript • Redis • PostgreSQL • Socket.IO • Docker
A real-time concurrent auction system focused on race-condition-safe bidding, server-authoritative state, crash recovery, and synchronization across clients.
Clients
│
▼
Socket.IO
│
▼
Auction Server
│
├──────────────► Redis
│ ├── SETNX Mutex
│ ├── Lock Token
│ ├── Lua Release
│ ├── Pub/Sub
│ └── Auction State
│
└──────────────► PostgreSQL
└── Durable Bid / Audit State
Key Engineering
- Designed a concurrency-safe bidding engine using Redis SETNX mutexes.
- Used token-validated Lua release to prevent incorrect lock ownership release.
- Used PostgreSQL for durable bid and audit state.
- Used Redis Pub/Sub for live auction state propagation.
- Implemented server-authoritative epoch timers.
- Added Redis-backed state recovery and state-sync hydration.
- Added 13 integration suites covering 61 tests across bidding, mutexes, transactions, recovery, and host controls.
- Stress-tested concurrent bidding behavior.
🔗 Source Code 🔗 Live at
Python • TCP • PostgreSQL • Docker • MetaTrader 5
An event-driven backend system bridging MetaTrader 5 with a stateful Python processing engine for high-frequency market telemetry.
ArchitectureMetaTrader 5
│
│ TCP
▼
Python TCP Bridge
│
│ newline-delimited framing
▼
Async Processing Engine
│
├──────────► Sliding Window / Signals
│
└──────────► PostgreSQL
│
└── 2s timeout
│
▼
Local CSV Fallback
Key Engineering
- Built a native TCP bridge between MetaTrader 5 and Python.
- Used newline-delimited framing to safely reconstruct TCP stream messages.
- Handles 3,000+ packets/minute under the designed workload.
- Uses asynchronous PostgreSQL persistence with connection pooling.
- Automatically degrades to local CSV persistence after database timeout.
- Maintains a separate processing layer from network and persistence I/O.
- Includes MT5 position reconciliation and state synchronization.
- Uses statistical regime detection and risk-gating logic for market telemetry.
Scaler School of Technology — Computer Science & AI
2025 – 2029 • Bengaluru, India
BITS Pilani — B.Sc. (Hons.), Computer Science
2025 – 2029 • Online / Distance Learning
10 merged pull requests into InsForge • Active Contributor to Apicurio Registry • Selected Contributor — GirlScript Summer of Code 2026
Open to backend engineering internships, systems work, and meaningful open-source collaborations.
Backend Infrastructure • Distributed Systems • Concurrent Systems • Security • Open Source