Wellsfargo: Senior Software Engineer
August 14, 2026 · 0 reads
Summary
I interviewed for a Senior Software Engineer position at Wells Fargo, completed three rounds (screening, technical, and managerial), but received no response after the final round.
Full Experience
1. Screening Test: (Solved Both)
- Two questions regarding SQL and SpringBoot Rest API problems from hackerrank - 1hr 10 mins
- SQL problem was bit complex involving sub queries
- hard to write without AI assistance
- SpringBoot Rest API problem was regarding creating endpoints for POST, PUT and GET operations
- Need to memorize annotations and DataTypes a bit, but solvable
2. Technical: (Mostly in a drive - virtual) (30 mins) (Highly Positive)
- Simple scenario based questions on Kafka, paginated APIs
- Kafka questions are based on understanding of concepts like consumer groups, partitions, topics (eg: what if 5 instances but only 3 partitions; ans: 2 pods will be idle)
- Design an API that fetches records from DB and displays on UI
- Paginate the API
- Use cursor(lastRecord) instead of OFFSET if the DB size is really large
- Add indexes
- Use of AI and what LLM for what task
3. Managerial: (Same day) (20-30 mins) (again Very much Positive)
- Just asked what all tools we use regarding AI, Cloud
- Project Description a bit
- Kept telling what all tools his team uses
Final Verdict
- No calls after 3rd round, and neither HR nor the Hiring Manager responded to calls.
Interview Questions (2)
1.
Kafka Consumer Group and Partition Allocation
Other·Medium
Explain what happens when there are 5 consumer instances but only 3 partitions in a Kafka topic. How are the partitions assigned to the consumers?
2.
Design Paginated API with Cursor-based Pagination
System Design·Medium
Design an API that fetches records from a database and displays them on a UI with pagination. The pagination should use a cursor (e.g., the last record's identifier) instead of OFFSET for large tables, and appropriate indexes should be added to support the query efficiently.