12 candidates
Sort by
Rank
Candidate
Overall
Rationale
Status
- 0192/100Deep payments background; ran a team that owned the same surface area you're hiring for.NewPer-dimension scores
- Backend depth×0.2594
- System design×0.2092
- Python×0.1588
- Distributed systems×0.1590
- Ownership signals×0.1095
- Fintech domain×0.1096
- Communication×0.0585
Verbatim evidence from CV- Backend depth
- “Led the payments-core team of 9 backend engineers for 3 years”
- “owned the gateway abstraction processing 4M+ tx/day”
- System design
- “Re-architected the settlement pipeline from a monolith to 6 bounded services”
- “Designed an idempotent retry layer using Redis Streams”
- Python
- “Primary stack: Python 3.11 (FastAPI, asyncio) and Go”
- “Authored internal Python style guide adopted org-wide”
- Distributed systems
- “Built a Kafka-based event bus handling 12k events/sec at p99 80ms”
- Ownership signals
- “Hired and managed a team of 9; ran weekly architecture review”
- Fintech domain
- “Six years across UPI rails, card acquiring, and reconciliation”
- Communication
- “Speaker at PyCon India 2023 on async payment workflows”
- 0287/100Strong fintech + distributed systems; Python is a secondary language for them.New
- 0384/100World-class fintech background but Python is a weak match — flagged for hold.Hold
- 0483/100Amazon Payments pedigree; Java-first engineer who codes Python.New
- 0681/100Excellent Python and team signals; fintech domain is adjacent rather than core.AcceptedView call
- 0975/100Strong fintech-and-Python combo; team-lead signals are still nascent.New
- 1070/100Decent engineer but adjacent domain and limited ownership — rejected by recruiter.Rejected
- 1160/100Capable Python engineer but limited scale and fintech depth.New
- —Arjun NairBackend Engineer · (CV partially parsed)failedPDF appears to be image-only; text layer not extractable.
Scores rerun deterministically — open a row to see verbatim CV evidence behind each dimension.