United Wholesale Mortgage's Software Engineer interviews typically run 2-3 rounds: a recruiter screen followed by a technical phone or onsite round. Candidates report a wide mix of difficulty, from easy coding checks to OOP deep-dives and a group brain teaser.
$108K
Avg. Base Comp
$135K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
United Wholesale Mortgage's software engineering process typically starts with a short recruiter or HR screen, roughly fifteen to forty-five minutes. It covers your background, why UWM, why you're leaving your current role, and the projects on your resume, and some recruiters add a few preliminary technical or OOP questions. From there, the process branches. Some candidates move into a technical phone or video interview focused on core object-oriented programming fundamentals — the single responsibility principle, interface versus class, constant versus readonly, overloading versus overriding, the singleton pattern, and MVC architecture. Others go to an onsite round that mixes behavioral questions with a lighter coding exercise.
Technical difficulty varies notably by report. One candidate described an easy LeetCode-style problem and basic programming questions during an onsite visit that included an office tour. Another faced two LeetCode-style problems per round across three total rounds, plus a question on preventing SQL injection in a .NET application. A third was asked about handling database calling issues in .NET applications. A candidate who received an offer worked through a couple of LeetCode-style problems, OOP trivia, and a group brain teaser resembling the classic river-crossing logic puzzle.
Two candidates who felt their technical conversations went well still reported long silences afterward. One noted the full process from first call to a final rejection took about six weeks despite being told to expect a response within 48 hours. Because individual reports describe meaningfully different interview content, prepare broadly across fundamentals, resume talking points, and a genuine answer for why UWM rather than assuming one fixed format.
Synthesized from 9 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 United Wholesale Mortgage process.
The process was pretty relaxed overall, but it wasn’t completely non-technical. I started with a short phone call with a recruiter, which was mostly a screening conversation, and then I was sent a survey about my technical skills and projects. After that, I came in onsite for an interview that included a tour of the office and a casual conversation with tech team leaders. The office itself was very nice, and the vibe was friendly rather than intimidating.
What stood out most was how much they focused on my resume and past experience. I was asked to walk through specific projects in detail, explain why I wanted to work at UWM, and talk about a time I worked on a team. In my case, there was also a more technical onsite round that lasted about an hour and felt like an easy LeetCode-style coding question, but it was still pretty light compared with a typical software engineer interview. Another person on the team asked very basic programming questions, including what language I was most familiar with. Overall, it felt like they cared more about whether I could communicate clearly, show interest in the company, and talk through my experience than about grinding through hard algorithms. I ended up getting the offer, and my main takeaway is to be ready to discuss your projects in depth and to come in with a genuine answer for why UWM.
Prep tip from this candidate
Be ready to walk through the projects on your resume in detail and explain your role, since that came up repeatedly. Also prepare for a very easy coding question or basic programming fundamentals, plus a clear answer for why you want UWM specifically.
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 United Wholesale Mortgage
How would you investigate why users on VLAN 2 can't access the internet while other VLANs work?
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Total Spent on Products | |
| P-value to a Layman | |
| Maximum Profit | |
| Prime to N | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Google Maps Improvement | |
| Hurdles In Data Projects | |
| Over 100 Dollars | |
| Minimum Change | |
| Find the Missing Number | |
| Scrambled Tickets |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter or HR call lasting roughly 15 to 45 minutes. Recruiters typically ask about your background, why you want to work at UWM, why you're looking to leave your current role, and projects on your resume, and some add a few preliminary technical or OOP questions.
Several candidates describe a technical round of up to about an hour covering object-oriented fundamentals. Reported topics include the single responsibility principle, interface versus class usage, constant versus readonly, overloading versus overriding, the singleton pattern, and MVC architecture. .NET topics came up in two reports: preventing SQL injection and handling database calling issues. One report included two LeetCode-style coding problems per round, with difficulty described as standard rather than unusually hard.
Onsite rounds, when reported, include a detailed walk-through of projects on your resume and a lighter coding or OOP question, and one candidate's visit also included an office tour. One candidate was asked an easy LeetCode-style problem and basic language-familiarity questions, another described a group brain teaser similar to the classic river-crossing logic puzzle, and interviewers may ask directly why you want to join UWM specifically.
Outcomes and timing differ sharply across reports. Two candidates received offers, while others describe technical conversations that felt positive but were followed by weeks of silence. In one case it took about six weeks from first call to a final rejection, despite the candidate being told to expect a response within 48 hours.
