Macquarie Group Software Engineer Interview Experiences 2026
Macquarie GroupSoftware Engineer
Updated May 25, 2026
Macquarie Group Software Engineer Interview Experiences 2026
Real, anonymous reports from people who interviewed for Software Engineer at Macquarie Group, newest first and distilled into what to expect across the loop.
Get your personalized Macquarie Group 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 went through a pretty typical early pipeline: a resume screen, then psychometric testing, followed by a recruiter phone interview, and later an assessment centre. Across the conversations, the tone was generally friendly and professional, and the questions skewed mostly behavioural with at least one group task as part of the assessment centre. I remember the whole thing moving at a steady pace—under two months end to end.
Even though my overall experience felt okay, the process still carried the usual uncertainty around timing. I had a few rounds scheduled—technical and psychometric, then a final in-person discussion at their office—but I also had to chase for updates when feedback wasn’t coming back quickly. One week after I’d been waiting, I got confirmation that things had been positive, but the role I’d applied for later went on hold, and there wasn’t a clear timeline for when it would restart. Even with courteous interviewers, the silence afterward really stood out, and I left feeling like the process was longer and less conclusive than it needed to be.
2 months ago
Difficult Negative Australia
My process felt like it was trying to get to the right fit, but the evaluation style ended up working against me. I started with a resume/experience discussion, then moved into a system-design and API-design style round. That second stage was harder than the first, and it also felt a bit like the interviewer wasn’t weighing my background—rather than building from my experience, the conversation stayed focused on what they’d do day to day.
I ran into similar disconnects elsewhere in the pipeline. In a separate attempt, I did a recruiter phone screen and then an in-person set of tests: one algorithm coding problem on a whiteboard and a system design discussion. Even when the interview content seemed fair on paper, the feedback wasn’t specific afterward, and it left me unsure what exactly I needed to improve. I also encountered an older aptitude-style screening approach that used numeric and verbal reasoning and made logic puzzles feel unnecessarily high-stakes. Across these experiences, the technical topics were there, but the criteria and the communication weren’t clear enough for me to feel confident about what was being assessed.
3 months ago
Average Positive Philippines
My experience was built like a progression of checks: a straightforward behavioural recruiter call first, then an online psychometric and cognitive as…
4 months ago
Average Neutral Houston, TX
I went through a smaller, more direct process that leaned heavily on coding under pressure. It was a contractual-position style interview with two mai…
8 months ago
Average Positive India
My interview setup matched a pretty common pattern at Macquarie: a recruiter touchpoint first, followed by an online assessment, and then technical an…
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
Interview Structure & Timeline
The interview process typically follows a structured pipeline, starting with a recruiter call, followed by technical assessments, and often includes psychometric testing, with a timeline generally under two months. Candidates noted that while the process was organized, communication about timing and updates could be lacking, leading to uncertainty.
Candidates experienced a mix of technical interviews focusing on coding, system design, and problem-solving under pressure, with formats varying from live coding sessions to algorithm challenges. While technical topics were prevalent, some candidates felt the assessments did not align well with their prior experience, leading to confusion about expectations.
Live codingSystem designAlgorithm challenges
Behavioral & Cultural Fit
Behavioral interviews were common, often exploring themes of collaboration, ownership, and fit within the team, with interviewers emphasizing communication and professional behavior. Candidates appreciated when interviewers were engaging and supportive, which helped create a more relaxed atmosphere.
CollaborationOwnershipProfessional behavior
Psychometric Testing
Psychometric assessments were noted as a challenging component of the process, often perceived as high-stakes and time-pressured, which added to the overall stress of the interviews. Candidates expressed that preparation for this segment was crucial, as it could significantly impact their progression.
Psychometric assessmentsTime pressureHigh-stakes
Communication & Feedback
Candidates reported mixed experiences with communication throughout the interview process, with some feeling well-informed while others encountered periods of silence and uncertainty regarding their status. Clear feedback post-interview was often lacking, leaving candidates unsure of their performance and areas for improvement.
CommunicationFeedbackUncertainty
Overall Experience & Reflection
While many candidates found the interview process to be professional and structured, there were common reflections on the need for clearer alignment between the interview content and the roles being assessed. Candidates often left the process feeling that their experiences did not fully match the expectations set during the interviews.