Engineering Velocity at Ramp
summary
Ramp claims it ships new finance products rapidly—five major product areas in 4.5 years—and cites concrete practices: small single‑threaded pods, embedding platform engineers in product teams, and hiring for growth slope. Metrics include 15,000 customers and >$10B payments volume. Engineering examples: a unified spend event model for cross‑payment reporting, a payments platform powering reimbursements and bill pay, and a receipt matcher that starts with an OCR API + heuristics then migrates to ML; each solution emphasizes speed that actually worked.
AI-written summary · about
chapters (12)
- 0:00Engineering velocity at Ramp
- 1:48Ramp’s mission
- 3:16Engineering’s customer value
- 5:25Team structure and pods
- 6:30Right abstractions
- 9:18Platform investments
- 11:26Product stage awareness
- 15:3410x value with AI
- 18:23Velocity versus quality
- 19:48Vendor utilization strategy
- 20:50Hiring philosophy
- 22:35Q&A
related talks
26mReaching Innovation Velocity
18mEngineering owns velocity
36mDoubling Engineering Productivity at eBay Through DevOps
37mDebugging Engineering Velocity
51mImproving Ebay's Development Velocity
45mImproving eBay's Development Velocity
01h 03mMoving Fast - without crashing
29mNavigating regulated scale: How Fiserv hones golden paths for 7,500 developers