Senior full-stack engineer building calm systems that ship.

Systems that stay calm when the room gets loud.

I build Java and Spring Boot backends that keep payroll, compensation, and market data moving; then I give them React and Next.js surfaces people can actually operate without a map and a prayer.

25% throughput gain 4x SQL speedup 10K+ events/hour

Email me See projects

Open the system sketch Optional visual map

signal-map.canvas

Workbench note Follow the lines: data in, decisions out, fewer mysteries in the middle.

Experience

Production systems I have built, improved, and kept moving.

Jan 2024 - Present

oracle/hcm/payroll

Senior Software Engineer - Oracle India Pvt. Ltd.

Redesigned Java thread-pool and batch-processing logic for a payroll event engine, improving throughput by 25% across 10K+ events per hour.
Built Spring REST APIs for payroll, absence, and compensation modules with versioning, pagination, and idempotent behavior.
Tuned PL/SQL paths with EXPLAIN PLAN, AWR reports, indexing changes, and query rewrites to cut execution time by 4x.

Nov 2021 - Dec 2023

oracle/hcm/modernization

Software Engineer II - Oracle India Pvt. Ltd.

Built resilient processors for effective-dated HR changes, retro payroll calculations, and compensation workflows.
Improved Oracle JET and VBCS performance through lazy loading and asynchronous validation flows.
Containerized backend services and automated releases through Helium CI/CD pipelines.

Jan 2019 - Nov 2021

samsung/android/power

Software Engineer - Samsung Research Institute

Engineered kernel-level Android charging features, including the Time-To-Full algorithm for flagship device lines.
Created Python and Java log automation that removed 3+ hours of daily manual hardware debugging work.
Extended Charging Log Analyzer support for emerging charging IC datasets and cross-device diagnosis.

How I work Performance, ownership, and usable interfaces. Short operating principles behind the work.

How I work

I care about performance, clear ownership, and interfaces people can use under pressure.

01 Backend first does not mean user last.

Latency, retries, pagination, and idempotency are product decisions wearing infrastructure clothes.

02 Modernization is archaeology with a deploy button.

Respect the old system enough to understand it. Then make the next person need less courage.

03 Dashboards should not be apology letters.

If a screen needs a meeting to explain, the system is leaking complexity into the room.

Projects Two shipped projects, explained simply. Market Narrative and The Win List, with live links.

live archive / source available

Project 01 / Market Narrative

Market Narrative Storyboard Engine

A financial media engine that turns overnight market signals, news stories, and technical setups into deterministic daily briefing packages.

Open live archive Read source

Problem: Daily market content usually arrives as scattered quotes, headlines, and chart notes. The useful narrative has to be assembled quickly, repeatably, and with fewer manual judgment leaks.
How I built it: Java 17 and Spring Boot run the modular backend; Next.js publishes the public archive; React powers the admin studio; PostgreSQL monthly partitions and Redis keep time-series reads practical.
Design choice: Kept it as a modular monolith instead of premature microservices, and used deterministic clustering plus risk-reward rules where auditability mattered more than theatrical AI magic.
Result: A live market archive with SEO-aware digests, repeatable reel-script generation, prompt packages, and a cleaner operating path from raw signal to publishable narrative.
Open it: marketnarrative.in is live, with the monorepo source available on GitHub for review.

Optional: view system map

public reader

MarketNews platform

market feeds

news stories

admin studio

live product / receipts included

Project 02 / The Win List

A daily wins product that treats consistency like a ledger, not a motivational poster.

Habit Ledger became The Win List: a production Next.js app for tracking today's must-do wins, reviewing monthly momentum, and syncing only when the user explicitly asks for the cloud to remember.

Open product Read branch

Problem: Most habit tools turn a simple day into a ceremony. The product needed to make the next win obvious, keep reflection lightweight, and avoid punishing missed days.
How I built it: Next.js 15, React 19, and TypeScript drive the app; browser storage keeps the first interaction instant; Supabase handles optional auth, Postgres backup, RLS, and launch metrics.
Design choice: Chose local-first data with explicit cloud sync instead of always-online persistence, and separated analytics choices from personal notes so growth metrics do not eat user trust.
Result: A live planning product with fast daily entry, monthly momentum review, export paths, optional backup and restore, and onboarding tests that keep personalization honest.
Open it: mywinlist.com is live, with the active onboarding branch linked for implementation review.

Optional: view operating model

Operating model

The product keeps its promise by making the default path local and fast, then treating the cloud as a deliberate capability instead of a silent dependency.

Next.js 15 React 19 TypeScript Tailwind CSS Supabase Render

today's wins track, note, export

browser ledger fast local source

Supabase sync Auth, Postgres, RLS

admin metrics aggregate launch view

Notes A few engineering beliefs, kept short. Optional personality, not required reading.

query plan margin note

When a report is slow, the database is not being dramatic. It is telling you where the story bends.

admin UI margin note

The best internal tools feel like someone stayed late and removed three future Slack threads.

architecture margin note

Boxes are cheap. Boundaries are expensive. Draw fewer and mean them.

deployment margin note

A release that is boring at 6 PM is a design achievement.

Skills Tools and systems I use often. Backend, frontend, data, and delivery stack.

Skills

Tools and systems I use often.

Backend: Java 17, Spring Boot, Spring MVC, REST APIs, microservices, event-driven architecture, Kafka, concurrency, SOLID.
Frontend: React, Next.js, Oracle JET, VBCS, TypeScript, JavaScript ES6+, HTML5, CSS3, responsive UI systems.
Data: Oracle DB, PostgreSQL partitioning, Redis, PL/SQL, SQL optimization, indexing, AWR reports, execution plans.
Delivery: Docker, OCI, GitHub monorepos, Maven, Node.js, Helium CI/CD, JUnit, Mockito, TDD, Agile/Scrum.

Optional console A small corner for easter eggs. Safe to ignore during normal browsing.

optional console

A small hidden corner for easter eggs. Safe to ignore.

Contact Open to senior full-stack and backend-heavy product roles. Email, LinkedIn, and GitHub.

Available for the right hard problem

Senior full-stack, backend-heavy product engineering, enterprise modernization, and systems with a pulse.

Based in India and open to relocation. Especially interested in teams that care about performance, product craft, and codebases people can still understand on a Thursday evening.

Email LinkedIn GitHub