Design a Resilient Document Aggregation Service
One senior candidate described this question from a Wells Fargo loop in mid-2026. It came in a technical round run by two senior engineers. The design question arrived after a run of Java, Spring Security, Kafka and design-pattern questions. The candidate listed what the panel pushed on afterwards: circuit breakers, asynchronous calls through a central orchestrator, a dead letter queue, scaling, and CQRS or read replicas. Prepare for every item on it.
The prompt doesn't say what the documents are, so ask. If the panel leaves it open, pick something bank-shaped. Picture the documents page in a customer's online banking. Statements come from one system, tax forms from a second, and loan paperwork from a third. Each system has its own owners, its own outages and its own idea of how fast is fast enough. The scale is modest. A bank serves a lot of customers, but this is an integration problem, and the hard part is behaving well when one of three systems you don't own is slow or down. Say that early, so the panel knows you won't spend twenty minutes on sharding.
Wells FargoPremium lesson · System design round
The Wells Fargo design, worked end to end.
- Requirements and scopeSystem design
- The API and data model
- The design, drawn out1 diagram
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports · guide updated
Wells Fargo interview guideKnow what Wells Fargo asks before you walk in.
30 coding · 4 system design · 16 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.