VC & PE / FinTech · Technical Due Diligence Platform · 2026
- Role
- Design Lead
- Surface
- Technical-DD platform · VC + PE
- Cycle
- 3 wks → 4 days
- Status
- Shipped · under NDA
Dossier · Company K
Technical verdict: proceed with conditions
Core modules read clean; test coverage thins around the billing paths.
source: repo scan · static analysis pass 02
A single job queue becomes the chokepoint well before the growth plan needs it to hold.
source: design-doc review · infra audit 01
Merge cadence is steady, but two contributors carry most of the commit history.
source: repo scan · commit log 12 mo
Claims in the deck match the demo; one benchmark could not be reproduced.
source: repo scan · interview note 04
review all four signals first
Partners bet millions on a startup's technology in days, on claims they will never personally check. The model extracted the evidence. The design made partners willing to stand on it. Diligence cycles ran 3 weeks to 4 days. Confidential — I'll walk the framework on a call.
Want the part I can't host here?
Hiring? In an interview I'll walk you through the decisions, the artifacts I can't host publicly, and the numbers — under mutual NDA.
Send me the roleDesign Patterns Demonstrated
- Confidence Score Patterns: Per-signal and per-document confidence, each one mapping to a next step a partner can take.
- ML Explainability Patterns: Provenance on every claim — a clean drill from the summary down to the source signal and code-quality measure behind it.
- Human-in-Loop Patterns: Analyst overrides fed back to the model; partner sign-off as real workflow, not a rubber stamp.
I write about this on The Trust Layer ↗