Reynolds and Reynolds software engineer candidates report online cognitive and personality assessments, a recruiter screen, and manager or director conversations. One candidate also describes coding, system design, SQL and debugging questions.
$65K
Avg. Base Comp
$75K
Avg. Total Comp
3-4 rounds
Typical Rounds
1-3 weeks
Process Length
Candidates for Reynolds and Reynolds software engineer roles describe a process in which pre-interview assessments carry real weight. Three Software Engineer reports mention cognitive or personality testing, including a Wonderlic-style test, word-math and pattern questions, and SAT-style vocabulary matching. One candidate did not move forward after the Wonderlic stage. Practicing timed aptitude and verbal reasoning questions is a sensible use of preparation time, alongside your technical work.
The human conversations are reported as resume-driven. One candidate describes a phone call and a Zoom interview focused on background, with a question about other offers. Another, who received an offer, describes a recruiter screen about hobbies, past jobs and languages, followed by a hiring manager. That manager asked conceptual questions such as object-oriented versus data-oriented design, and gave a simple coding problem on an online platform. A director interview then mixed technical and behavioral topics.
A separate report describes four rounds with an LRU cache, a URL shortener design, SQL optimization, a performance-debugging exercise and a behavioral round. That experience is a single report, and the other reports describe less technical depth. Prepare core data structures, clear explanations of your reasoning, and a concise career story covering what you liked and disliked in past roles. One candidate was also asked about willingness to relocate to the Dayton, Ohio office.
Synthesized from 8 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 Reynolds and reynolds 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 Reynolds and reynolds
How would you diagnose and speed up a slow SQL query when system metrics look healthy?
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Monthly Customer Report | |
| String Shift | |
| Prime to N | |
| Random SQL Sample | |
| Upsell Transactions | |
| Top 3 Users | |
| Find the First Non-Repeating Character in a String | |
| Minimum Change | |
| Customer Orders | |
| Scrambled Tickets | |
| Largest Salary by Department | |
| Comments Histogram | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| The Brackets Problem | |
| Size of Joins | |
| Flight Records | |
| Project Pairs | |
| Download Facts | |
| First Touch Attribution |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report tests before or alongside the interviews. These include a Wonderlic-style cognitive test, word math and pattern questions, SAT-style vocabulary, and a personality questionnaire. One candidate did not advance after the Wonderlic stage. Timed practice is likely worthwhile, though formats may vary.
Candidates report a phone or Zoom call centered on their resume, hobbies, past jobs and comfort with programming languages. One candidate was asked about other offers, and another reports a recruiter explaining company culture. Expect mostly background questions rather than technical depth, though this may differ by team.
One candidate who received an offer reports a manager who probed the resume. He asked about object-oriented versus data-oriented design, then had the candidate solve a simple problem on a coding platform. This is a single account, so the technical bar may vary.
One candidate describes a director interview that mixed technical questions with behavioral ones about past jobs, schooling and project roles. A separate four-round report describes an LRU cache, a URL shortener design, SQL optimization, a debugging exercise and behavioral questions about conflict and deadlines. These accounts differ, so prepare for both styles.
