Real, anonymous reports from people who interviewed for Software Engineer at MediaMath, newest first and distilled into what to expect across the loop.
Get your personalized MediaMath Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I was first reached out to through Hired.com, and I scheduled time with an internal recruiter. After that, I had a phone screen that went with the VP of Engineering, and it felt more like a conversation about the projects I’d worked on and the technologies I’d used than a rapid-fire interrogation. If I highlighted something I’d done before, we’d dig into it at a practical level, which made the call feel grounded.
From there, I moved into a technical interview led by engineers. The format ended up being a React-based session with two engineers, and it lasted about 45 minutes. Across the interviews, the vibe was that people were open to my ideas and weren’t trying to trick me; at one point I also remember there being design-pattern focus and even a short paper-based problem-solving segment. Overall, it felt like a normal technical evaluation for an engineering role—serious enough to test fundamentals, but not hostile.
> 1 year
Average Neutral Raleigh, NC
My process felt like it dragged across the Thanksgiving/Christmas stretch in the U.S., and that timing added awkward gaps that made everything harder to stay mentally focused on. After a pleasant recruiter phone screen, I spoke with the technical VP, and the emphasis was on how I’d approach solving problems—less about memorized details and more about reasoning through the kind of scenario they described.
If that went well, I had a coding homework assignment with a deadline of three days. After I submitted, it turned into a sequence of interviews with technical team members, plus a panel-style element where I discussed a project and talked through features, challenges, and bugs. There was also a more “around the office” presentation-style stage described as a multiple-stage flow, and by the time I got to the end I was also speaking with a hiring manager who separated technical management from people management.
> 1 year
Average Positive New York, NY
I got pulled in through the normal recruiter flow and the process moved at a steady pace. It took about three to four weeks total, and it was fairly s…
> 1 year
Difficult Negative New York, NY
This was one of those processes where everything felt normal until the timing fell apart. I was told I’d advance to the fourth stage, and I was notifi…
> 1 year
Average Negative United States
My onsite interview itself was fine, but the experience left me disappointed overall. The interviews didn’t feel like they had much engagement from th…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruiter & Initial Screening
The interview process typically begins with a recruiter screening that may involve scheduling challenges and varying levels of communication. Candidates noted that the recruiter’s responsiveness can significantly impact the overall experience, with some reporting a lack of follow-through after initial interactions.
RecruiterCommunicationScheduling
Technical Interviews
Candidates can expect multiple technical interviews that assess coding skills, problem-solving abilities, and system design knowledge. The format often includes coding assignments, practical problem-solving discussions, and sometimes a panel interview with team members, aiming to evaluate both technical proficiency and collaborative skills.
CodingSystem DesignTechnical Assessment
Behavioral & Cultural Fit
Behavioral interviews focus on candidates' past experiences and how they approach problem-solving, with an emphasis on reasoning over memorization. Interviewers are generally friendly and encourage open dialogue, but candidates should be prepared to discuss their fit within the company's culture and values.
BehavioralCultural FitProblem-Solving
Interview Structure & Flow
The interview process is often structured with a clear sequence of assessments, including online tests and in-person interviews, but candidates have reported occasional delays and communication gaps that disrupt the flow. Maintaining momentum throughout the process is crucial for a positive experience.
StructureFlowAssessment
Feedback & Closure
Candidates frequently express disappointment over the lack of feedback and closure after interviews, especially if they do not receive an offer. Clear communication regarding outcomes and constructive feedback is highlighted as an area needing improvement to enhance the candidate experience.
FeedbackClosureCommunication
Overall Experience & Outcome
The overall experience can vary significantly, with some candidates feeling positive about the thoroughness and professionalism of the process, while others report frustration due to poor communication or unclear outcomes. Candidates should be prepared for a potentially lengthy process and varying levels of engagement from interviewers.