Candidate reports on Mars software engineering interviews describe an HR screen, a CTO conversation, domain-focused questions and a video-only internship screen, with slow or missing follow-up.
$95K
Avg. Base Comp
$105K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Mars software engineering reports describe conversations more than coding tests. A Software Engineer candidate had an HR screen followed by a call with the CTO, which centered on past projects, problem-solving approach and how the candidate works with teams. The recruiter spent most of the screen explaining the process and asked only briefly about salary expectations and experience. The CTO round was the substantive one, and the candidate left feeling it had covered the role and the company's regulatory compliance challenges.
A Senior Software Engineer candidate, in a separate loop, said the technical questions were about domain background more than coding. They were asked directly about classification and sanctions experience, and why they wanted to leave their current job. After the first interview they were moved toward a final stage, which was cancelled a few days beforehand with an explanation about their experience that they felt did not match what they had said.
The Software Engineer internship report looks different. The whole process ran through HireView, an automated video platform, with questions on motivation, strengths and weaknesses, how the candidate compared to peers and future technology trends. Nothing technical was asked.
To prepare, have two or three project stories you can explain in depth, and be ready with specific examples for any domain you list on your resume. Keep notes on what you said in each conversation. All three reports mention slow or absent communication afterward, from a four-week wait to months of silence, so set your own follow-up schedule. With only three reports, confirm the format with your recruiter.
Synthesized from 6 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 Mars process.
I went through Mars's internship interview process, which started with an online HireVue video submission. I had to answer a couple of open-ended questions on video about my motivation and career goals—nothing too technical at that stage, just trying to get a sense of who I was and why I was interested in the role. The vibe was pretty relaxed, which helped ease some of the initial nerves.
After that came a Zoom call with the hiring team. They were genuinely friendly and laid-back, which made the conversation flow naturally. We talked about my background and experience, and they were curious about my problem-solving approach and willingness to learn. They threw in a few technical questions tailored to the specific area I'd applied for—in my case, data—asking me to walk through how I'd solved a particular technical problem and how I'd explain something technical to someone without that background. The interview had a real emphasis on collaboration and communication skills, not just raw technical ability.
There was also a group dynamic component where candidates worked together, and the team was evaluating how well we communicated and collaborated under that structure. Throughout the whole process, HR stayed in touch via text, which kept things feeling organized and transparent. The team made it clear they valued eagerness to learn and independent thinking alongside teamwork. They also asked logistical questions like whether I could work hybrid from the office, since that was part of the role setup.
Prep tip from this candidate
Be ready to explain technical solutions you've actually worked on in simple, non-technical terms—Mars specifically tests this ability. Also prepare for group dynamics or collaborative problem-solving components alongside one-on-one interviews.
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 Mars
Strategically resolving misaligned expectations with stakeholders for a successful project outcome
| Question | |
|---|---|
| Employee Salaries | |
| Cumulative Distribution | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Cumulative Reset | |
| Client Solution Pushback | |
| Restaurant Recommender | |
| Your Strengths and Weaknesses | |
| Area Under the ROC Curve | |
| Meta in an Emerging Market | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Flight Records | |
| Prime to N | |
| Largest Salary by Department | |
| Upsell Transactions |
Synthesized from candidate reports. Individual experiences may vary.
A Software Engineer candidate describes a bare-bones HR screen in which the recruiter spent most of the time explaining the interview process. Questions about salary expectations and current experience were brief and not deep. Have a short background summary and a salary expectation ready.
The same candidate's second round was with the CTO, who asked about their background and specific projects, their approach to problem-solving and how they work with teams. The conversation also touched on the company's challenges around regulatory compliance. Be ready to explain past work in detail.
A separate Senior Software Engineer candidate was asked directly about classification and sanctions experience and why they wanted to leave their current job. The questions were about domain background rather than coding. A final round was later cancelled days before it was due, so keep your own record of what you discussed.
A Software Engineer internship candidate completed the process entirely on HireView, an automated video platform. Questions covered motivation, strengths and weaknesses, comparison to peers and future technology trends. The candidate had a minute to prepare, could retake answers, and waited about four weeks for a response.
