How many rounds is the Manulife Financial Full Stack Engineer interview process?

Candidates report 2 stages: Recruiter Call and Technical Interviews. The interview process section above breaks down what each stage covers.

How much does a Full Stack Engineer at Manulife Financial make?

Reported compensation for Full Stack Engineer roles at Manulife Financial ranges from roughly $53k base to $863k total per year, varying by level, team, and location.

What topics come up in the Manulife Financial Full Stack Engineer interview?

Manulife Financial Full Stack Engineer interviews most often cover Azure, React, Node.js, SQL, and AI Solution Development, based on topics extracted from real candidate reports.

What questions does Manulife Financial ask Full Stack Engineer candidates?

Recent candidates report questions like "Optimizing Time and Space Complexity" and "Pivoting Under Changing Requirements". The question bank above tracks 3 questions for this role, ranked by how often they come up in Manulife Financial interviews.

Manulife FinancialFull Stack Engineer

Updated Mar 31, 2026

Manulife Financial Full Stack Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Full Stack Engineer at Manulife Financial, newest first and distilled into what to expect across the loop.

Get your personalized Manulife Financial Full Stack Engineer prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

5 months ago

Average Positive Toronto, ON

After a recruiter call to confirm my background and that I was a fit for the role, I moved into a two-round process. The first round was with HR, where we went through my understanding of the position, my experience, and the basics of what I’d done before.

The second round was technical. It felt fair, not overly difficult, and the questions were tied closely to the skills the team seemed to be working with—React, Node, and SQL. I also got a basic real-time challenge. Even though the job description emphasized .NET and C#, I’d spent extra time preparing for that, so some parts of the technical conversation didn’t line up with what I expected. Still, the overall experience felt constructive, and I walked away reminded of how important it is to match preparation to the actual tech stack the team is using.

7 months ago

Average Positive Makati City

I had two calls before the actual interview. The first was an initial screening to confirm the role I applied for and the details on my CV, and the second call was to confirm the technical interview time and scheduling.

When the technical interview finally happened, it began with questions about me and a walkthrough of my past projects. I discussed the technical background behind what I’d built and covered some technical terms that mapped to the role. Overall it felt like the interviewers were testing whether my project stories connected clearly to the concepts they cared about.

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.