Loadsmart Software Engineer interviews, as five candidates describe them, combine a HackerRank assessment, live coding on data structures and graphs, OOP class design, and some C++ depth. Behavioral questions also appear.
$143K
Avg. Base Comp
$175K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Five candidates describe Loadsmart's software engineering interviews, and the technical bar is the common theme. Some are internship candidates and one is a full software engineer candidate, so treat the details as a range of experiences rather than one fixed process. All five report not receiving an offer.
The online assessment on HackerRank comes up in several accounts. One candidate describes two LeetCode-hard-style algorithm problems in about an hour. Another describes a medium-to-hard set of two questions. A third describes two coding questions mixed with system design, with a 10-day expiry window. Another reports nothing harder than medium. Difficulty therefore varies by account, so practice under a timer.
Live rounds lean on data structures, graphs, and optimization. One candidate was pushed past naive solutions toward better complexity. Another was asked to build a directed graph and also faced a hard LeetCode question with a follow-up.
Class design and OOP recur too. Two candidates describe class design problems, including a Python OOP design round, and one reports being asked about binary search trees and design patterns. One candidate believes searching for answers during the round hurt their candidacy.
Language depth may matter. A full-time candidate reports a C++14-17 screen that probed how features work internally, followed later by a round on data structure internals such as how std::unordered_map works. Another mentions C++ internals questions. Behavioral questions appear in several accounts, usually alongside coding. Interviewer style reportedly varies, so be ready to narrate your reasoning without much feedback.
Synthesized from 5 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 Loadsmart process.
The process started with an online assessment of standard coding questions—nothing harder than medium difficulty. I passed that and moved into the technical interview rounds, which consisted of three separate interviews, each about 45 minutes to an hour long.
The first technical round opened with behavioral questions: they asked about a time I'd worked on a team project and a time I'd fixed a bug. Then came the coding question, a medium-difficulty problem, which I solved. The second round was purely behavioral. The third round was a Python OOP class design question where I had to think through object-oriented principles and design a class from scratch, and it took up most of the 50-minute slot, leaving only about 10 minutes for me to ask questions. The interviewers were pretty thorough, asking follow-up questions on my code and design choices, clearly caring about how I structured my solution and reasoned through trade-offs.
During that OOP round, I tried to search things up while working through the problem, and in hindsight I think that probably hurt my candidacy. I didn't advance past that round. One of the earlier rounds also included broader theory questions spanning OOP, design patterns, operating systems, and data structures—one interviewer asked me to explain how a binary search tree works—followed by about 30 minutes to complete a live coding problem.
Prep tip from this candidate
Brush up on OOP and class design before your rounds—this appeared in multiple interview formats and seemed to be a key evaluation area. Also, don't attempt to look things up during the interview; interviewers are watching your problem-solving approach, not just your final answer.
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 Loadsmart
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Top 3 Users | |
| Minimum Change | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Raining in Seattle | |
| String Shift | |
| Flight Records | |
| Download Facts | |
| Prime to N | |
| Bagging vs Boosting | |
| Upsell Transactions | |
| Daily Retention Summary | |
| Level Of Rain Water In 2D Terrain | |
| P-value to a Layman | |
| Size of Joins | |
| Recurring Character | |
| First Touch Attribution | |
| Google Maps Improvement | |
| Job Recommendation | |
| Find Bigrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a non-assessment screen that varies by role. One software engineer candidate describes an opening rapid-fire C++14-17 knowledge check that probed internals. An internship candidate describes a conversational phone interview after the online assessment, with a self-introduction, CS basics, and resume discussion. Prepare for either style.
Several candidates report a HackerRank assessment with two questions. Reported difficulty ranges from medium to LeetCode-hard, and one account mixes coding with system design. One candidate describes about an hour and another a 10-day completion window. Practice graph and optimization problems under time pressure.
Candidates report live coding rounds on graphs, data structure internals, class design, and follow-up questions on code choices. One full-time candidate describes three technical rounds; others describe fewer. Interviewers may push for better complexity and may offer little feedback, so explain your reasoning clearly aloud.
Behavioral questions appear in several accounts. Candidates mention team projects, fixing a bug, and past experience, sometimes as a warm-up before coding or as a separate round. One full-time candidate reports a behavioral round at the end of a block of interviews. Prepare concrete examples from your own work.
