
One candidate for an Angular Engineer role at Edward Jones describes a HireVue recording followed by a conversational video interview with a small team panel. The focus was step-by-step reasoning and a work-mistake story.
$110K
Avg. Base Comp
$130K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
A candidate who interviewed for an Angular Engineer role at Edward Jones described an interview built around how you think, not a heavy technical drill. The first stage was a HireVue recording with a set of prompts. The candidate could take as much time as they wanted to prepare each answer, so specific, concrete responses matter.
The second stage was a video interview with two or three people from the team. Most of the time went to the candidate's experience and problem-solving approach. Interviewers wanted each step of the reasoning walked through instead of a final answer alone. The candidate called this more draining than a whiteboard session. One question they remember was about a significant mistake at work, how they fixed it and what they learned. The interviewers were friendly and joked around, which eased the nerves. The candidate did not receive an offer and, looking back, wished they had rehearsed talking through their reasoning out loud.
To prepare, pick a real mistake story with a clear fix and lesson. Practice narrating technical decisions in your own words, including trade-offs. This is a single account, so treat it as one data point and not a fixed format for every Edward Jones engineering team.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Edward Jones process.
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 Edward Jones
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Size of Joins | |
| Payments Received | |
| Total Spent on Products | |
| P-value to a Layman | |
| Find the First Non-Repeating Character in a String | |
| Get Top N Frequent Words | |
| Top 3 Users | |
| Maximum Profit | |
| Bagging vs Boosting | |
| Duplicate Rows | |
| String Shift | |
| Scrambled Tickets | |
| Google Maps Improvement | |
| Prime to N | |
| Comments Histogram | |
| Employees Before Managers | |
| Last Transaction | |
| LRU Cache 1 | |
| Slacking Employees Salaries |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports the first stage was a HireVue recording with a set of prompts. They could take as much time as they wanted to prepare each answer. Concrete, specific answers are the safer approach, since there is no live interviewer to react to.
The candidate was then invited to a video interview with two or three people from the team. Most of the time went to their experience and how they approach problems. Interviewers asked them to walk through each step of their reasoning. The tone was friendly and conversational.
One question the candidate remembers asked about a significant mistake at work, how they fixed it and what they learned. They tried to show the thinking behind each decision, not only the outcome. Applicants may want a real story ready, with a clear fix and lesson.
This candidate did not receive an offer. They felt the interviewers were mainly evaluating how they work through a problem, and they suggested rehearsing that reasoning out loud beforehand. Other candidates' timelines and outcomes may differ.