Real, anonymous reports from people who interviewed for Software Engineer at Mercor, newest first and distilled into what to expect across the loop.
After I spoke with a recruiter, about a week later I joined a technical screen that ran for roughly half an hour. The format was interactive: I was asked to read short code snippets, explain what was happening, and then debug or reason through specific lines. The discussion didn’t stay purely on syntax either—it moved into data structures and algorithms, including complexity analysis.
My interview started with an AI agent conducting it remotely—either by phone or on my computer. The first part felt pretty straightforward, but the second section was more restrictive and caught me off guard: it was a compatibility check specifically for Apple Silicon Macs.
The interview process is heavily automated, with multiple rounds conducted by AI, which can feel mechanical and may lack the warmth of human interaction. Candidates reported mixed feelings about the AI's ability to engage meaningfully, with some experiencing interruptions and awkward flows.
Candidates undergo a technical screen that includes coding challenges and discussions on data structures, algorithms, and system design, often requiring justification of decisions and trade-offs. The difficulty is generally challenging but manageable, with a focus on practical problem-solving.
During technical assessments, candidates must share their screens and adhere to strict rules, including prohibitions on using AI tools. This setup aims to create an authentic troubleshooting environment but can add pressure and complexity to the assessment.
Candidates often report a lack of feedback after assessments, which can leave them uncertain about their performance and the reasons for their application status. This absence of communication can contribute to a feeling of incompleteness in the interview experience.
The interview process typically follows a clear sequence, starting with an AI round, followed by technical assessments and coding tasks. The overall timeline from application to decision is generally around two weeks, but experiences vary widely based on the specific rounds encountered.
Some candidates experienced intense, full-day coding interviews that required switching contexts between system design and coding tasks, leading to a demanding and sometimes overwhelming experience. The difficulty level can be high, with substantial problems to solve.