Mroads Software Engineer candidates describe a Panna-based online assessment mixing aptitude, coding and logic, followed by technical interviews. Reports stress complexity optimization, data structures and Java fundamentals.
$97K
Avg. Base Comp
$106K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for Mroads Software Engineer roles describe a process that runs largely on the company's Panna platform, starting with an online assessment rather than a conversation. One candidate reports about ten questions mixing coding, puzzles and logic. Another describes multiple-choice questions, aptitude problems and three coding challenges, and a third describes a webcam-proctored test covering aptitude, programming and visual reasoning.
The coding topics named are fairly concrete: removing duplicates from an array, formatting output as JSON, postfix conversion, sorting with complexity analysis, a binary tree problem, a binary search tree diameter question, and finding the longest balanced substring in a string of parentheses. One candidate says interviewers asked for a working solution and then pushed for a better time or space complexity, so practice explaining trade-offs aloud.
Fundamentals also appear. Candidates mention linked lists, Java method overriding and overloading, polymorphism and inheritance, SQL joins, and design patterns in a later technical round. Behavioral prompts such as "Tell me about yourself" and "Why should we hire you?" were reported in the first stage.
Experiences vary. One candidate describes a campus drive with a final CEO round, and another reports no formal follow-up after the test. Expect the format to differ by hiring channel, and ask the recruiter what each stage will cover. Based on three accounts, none ended in an offer that the candidate accepted.
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 Mroads process.
My interview at Mroads was challenging and multi-faceted. The entire process ran on their Panna platform, starting with an initial round that mixed technical and quantitative questions. I faced about ten questions total in that first phase, including some coding problems alongside puzzles and logic questions. The coding portion was the most rigorous part—they gave me problems like removing duplicates from an array and formatting output in JSON, but the real test came when they asked me to optimize my solutions further. I had to think through complexity and explain my logic as I went.
Beyond the coding, they probed my fundamentals hard: linked lists, data structures, basic Java concepts like method overriding and method overloading, and SQL queries including joins. There was even a behavioral element—they asked standard questions like "Tell me about yourself" and "Why should I hire you?" The second round moved to face-to-face technical interviews, again on Panna, with more coding problems. One that stuck with me was finding the longest balanced substring in a sequence like "()()(()))"—that required careful parsing and tracking. Throughout, confidence mattered; they seemed to value how I approached problems as much as whether I got them right the first time.
I didn't receive an offer, but the experience taught me that Mroads values depth across both algorithmic thinking and foundational knowledge. They want to see you handle optimization and explain your choices under pressure.
Prep tip from this candidate
Focus heavily on data structure optimization—they will ask you to code a solution, then immediately push you to improve its complexity. Practice linked lists, array manipulation problems, and balanced parentheses problems. Be ready to justify your approach verbally and handle follow-ups on time and space complexity.
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 Mroads
How would you build and justify the components of a Transformer encoder layer in PyTorch for large-scale text data?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Find the Missing Number | |
| Size of Joins | |
| Retailer Data Warehouse | |
| Over-Budget Projects | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| First Touch Attribution | |
| Employee Project Budgets | |
| The Brackets Problem | |
| Minimum Change | |
| Real-Time Transaction Streaming | |
| Repeated Category Purchase | |
| Get Top N Frequent Words | |
| SELECTive Wine Connoisseur | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report the first stage ran on Mroads' Panna platform. Accounts describe aptitude and logic questions, multiple-choice items, visual reasoning and coding problems, with one candidate counting about ten questions and another three coding challenges. One test was webcam-monitored and taken from home. Details may vary by hiring drive.
One campus-drive candidate reports uploading a resume and personal details and recording a self-introduction video before the assessment. Behavioral questions such as "Tell me about yourself" and "Why should we hire you?" were also reported by candidates in the first stage, so a short, clear pitch is worth preparing.
Reported problems include removing duplicates from an array, JSON-formatted output, postfix conversion, sorting with complexity analysis, binary tree and BST diameter questions, and longest balanced parentheses substring. One candidate says interviewers asked them to improve their first solution, so you may need to justify time and space complexity.
One candidate describes face-to-face technical interviews on Panna with further coding problems. Another reports a technical round covering data structures, timed coding and design patterns. Topics mentioned include linked lists, Java overriding, overloading, polymorphism, inheritance and SQL joins. Expect to explain your reasoning as you work.
One candidate describes a three-round campus pipeline that ended with a CEO round, though they did not progress far enough for it to matter. Another reports hearing nothing after the assessment. Outcomes and communication appear to vary, so confirm next steps with the recruiter.
