Workbench/resume/projects/proj_d15b844118768e700ab96668
Event-Driven Fraud Platform
One project stays anchored as the deep-dive unit: context on the left, session history on the right, and explicit project prompts ready to practice.
- project_id
- proj_d15b844118768e700ab96668
- sessions
- 1
- highlights
- 2
- tech_stack
- 4
Project context
Project context stays visible because the deep-dive flow should practice storytelling, not generic chatting.
Built a real-time fraud scoring pipeline for checkout risk decisions.
Highlights
Highlights give the deep-dive session concrete material to probe.
Led the async rules engine rollout across payment services.
Reduced p95 decision latency by 38% after stream redesign.
Suggested deep-dive questions
Suggested prompts come from the structured project entity and seed the first session turns.
What problem was Event-Driven Fraud Platform solving, and what part did you personally own?
Why did you choose Java and Kafka for Event-Driven Fraud Platform?
Walk through the hardest part of Event-Driven Fraud Platform and how you delivered "Led the async rules engine rollout across payment services.".
What outcome, metric, or business impact proves Event-Driven Fraud Platform worked well?
Tech stack
The stack is visible before the user starts answering follow-ups.
JavaKafkaRedisMySQL
Session history
Session history stays beside the project, not hidden behind the generic QA route.