Jasmine Chabbra (She/Her)

An AI-assisted credit underwriting engine. A regulator can ask two years later why an applicant was declined, and the answer has to come out the same every time it is asked.

• Five ordered policy rules with hard stops. Every outcome is stored per application, passing rules included, so an audit shows what was considered and not only what failed.
• Idempotency-Key is a unique column, so a client retry replays the original decision instead of underwriting a second time.
• A missing bureau score is treated as risk rather than as neutral, which is how thin-file applications get caught instead of waved through.
• 13 tests covering decision boundaries, determinism and idempotent replay.

Fraud detection for card and UPI payments, split along the line that decides the architecture: what has to be fast, and what is allowed to be slow.

• Five risk signals scored over a single batch of context queries, so adding a signal never adds a query to the hot path.
• Weights are additive and capped at 100, and no single signal can reach the block threshold alone. One bad signal costs precision instead of declining every customer at once.
• An agent works held cases through an allow-list of three read-only tools. It recommends, and its recommendation is stored next to the analyst's verdict rather than replacing it, so the two can be compared later.
• 34 tests across signals, banding boundaries, the agent loop and the full pipeline on a real database.

A payout orchestration engine with exactly-once transfers across four bank APIs. A payout that fails halfway has to resume, not restart, so idempotency keys live in both Redis and the database and every step records its own completion.

• Config-driven integrations for four bank APIs across API key, OAuth2 and HMAC authentication.
• Step-level resume, retries and a dead-letter queue, so a failed payout never repeats a step that already went through.
• Zero duplicate payouts under a 25% injected failure rate.

A full-stack AI background-removal product, and the one project here where I owned the frontend too: Spring Boot REST APIs over MySQL, a React 18 interface built with Vite and Tailwind, and authentication handled through Clerk instead of rolled by hand.

A small Spring Boot REST API that shortens URLs and redirects to the original link.