Workbench/resume/projects/proj_6b6ed765533e747c0d5acb0b
Event Pipeline Rebuild
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_6b6ed765533e747c0d5acb0b
- sessions
- 0
- highlights
- 2
- tech_stack
- 4
Project context
Project context stays visible because the deep-dive flow should practice storytelling, not generic chatting.
Rebuilt a synchronous order-processing flow into an event-driven pipeline for better throughput and resilience.
Highlights
Highlights give the deep-dive session concrete material to probe.
Cut p95 latency by 42 percent after decoupling hot-path calls.
Designed idempotent consumers, retry handling, and DLQ recovery.
Suggested deep-dive questions
Suggested prompts come from the structured project entity and seed the first session turns.
What problem was Event Pipeline Rebuild solving, and what part did you personally own?
Why did you choose Java and Kafka for Event Pipeline Rebuild?
Walk through the hardest part of Event Pipeline Rebuild and how you delivered "Cut p95 latency by 42 percent after decoupling hot-path calls.".
What outcome, metric, or business impact proves Event Pipeline Rebuild worked well?
Tech stack
The stack is visible before the user starts answering follow-ups.
JavaKafkaMySQLRedis
Session history
Session history stays beside the project, not hidden behind the generic QA route.
Empty state
No sessions yet
No deep-dive sessions exist for this project yet.
- Start a deep-dive session from this page.
- The first turn will seed from the project's suggested questions.