Candidates describe Chase software engineer interviews as a recruiter or phone screen, an approachable coding round, and a system design discussion, with one report of a long wait between rounds.
$126K
Avg. Base Comp
$152K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Candidate reports on Chase software engineering interviews point to a fairly approachable coding bar paired with a design conversation where communication matters. One candidate who received an offer described a phone screen, then a coding round with easy-to-medium LeetCode-style problems (balancing parentheses was one), then a system design round on a check depositing system. That candidate said interviewers wanted the approach explained before coding and cared more about trade-off reasoning than a perfect architecture.
Another candidate, who was rejected, reported three rounds over about two months, most of it waiting. The screen was simple string parsing into a map. The second round asked for an undirected graph with addNode, addEdge and traverse, where addEdge had to reject edges that create a cycle. That candidate ran out of time on the cycle check. The design round asked for a CRUD service for personal details plus an external background-check call. The candidate felt questions about scale were brushed aside, so stating assumptions early is sensible.
Two reports come from adjacent roles, so treat them as context. A lead-level candidate faced Java fundamentals, SQL group-by and having questions, then a panel with about twenty minutes of coding on a longest-consecutive-sequence problem with a wrap-around twist. An internship applicant passed a HackerRank assessment but was not advanced, suggesting that resume fit also matters.
For preparation, practice easy-to-medium graph and array problems aloud, rehearse a cycle check with DFS or union-find, and prepare to design a payments-style or CRUD service while naming your assumptions.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Chase process.
The process kicked off with a phone screen where they dug into my background and experience. Then came two technical rounds that were pretty demanding. The coding round had a couple of LeetCode-style problems ranging from easy to medium difficulty — I remember one was about balancing parentheses. The key thing they emphasized was to talk through my approach in detail before diving into the code. They wanted to see my thinking, not just the final solution.
The second round was a system design interview. I got asked to design a check depositing system, which required me to think through the architecture, trade-offs, and scalability considerations. They didn't want a perfect answer so much as a thoughtful approach and the ability to reason through different design choices. Throughout both rounds, the interviewers were technical but the bar seemed to be on clear communication and problem-solving methodology rather than flawless execution. It was intense but felt fair — they were testing whether I could think like an engineer, not just whether I'd memorized solutions.
Prep tip from this candidate
Be ready to verbalize your approach before coding — they care about your thinking process. For system design, focus on reasoning through trade-offs (scalability, fault tolerance, latency) rather than having a perfect architecture. Brush up on LeetCode medium problems and be prepared to discuss real-world design scenarios like payment or financial systems.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Chase
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| Google Maps Improvement | |
| Rectangle Overlap | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects | |
| Sum to N | |
| Over 100 Dollars |
Synthesized from candidate reports. Individual experiences may vary.
One candidate who received an offer reports an initial phone screen covering background and experience before the technical rounds. Another candidate mainly noted that the recruiter handled scheduling, and described an easy string-parsing screening round. Expect to summarize your experience clearly, though the exact content may vary by team.
An internship applicant reports a HackerRank assessment with two easy-to-medium coding problems, one resembling FizzBuzz. They solved both and still did not advance, which they attributed to resume screening. This step was reported only for an internship, so full-time applicants may not see it.
Candidates report easy-to-medium algorithm problems: balancing parentheses in one account, and a graph with cycle-rejecting edges in another. The offer recipient said interviewers wanted the approach talked through before coding. One candidate ran out of time, so pacing and verbal explanation of unfinished logic may help.
Reported prompts include a check depositing system and a CRUD service for personal details with an external background-check call. The offer recipient described an emphasis on architecture, trade-offs and scalability rather than a perfect answer. One rejected candidate felt scale questions were dismissed, so stating assumptions up front is a reasonable precaution.
Outcomes in the reports differ: one offer and rejections in the other accounts. One candidate said three rounds took about two months, mostly waiting. Other candidates did not report total timelines, so pacing may vary by team and role level.
