
Two candidates describe Quest Global Product Manager interviews. One centered on ITIL, Service Catalog work and project management scenarios. The other covered past projects and team management before a final round was cancelled. Both reported no offer.
$110K
Avg. Base Comp
$130K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The two Quest Global Product Manager reports we have point toward process discipline more than classic product strategy. One candidate said the interview opened with whether they had built a Service Catalog using ITIL frameworks, with little time spent on culture or the broader company vision. Questions in that account included how to resolve project conflicts, how to build a Service Catalog from scratch under ITIL principles, and the three hardest challenges of their career. One round reportedly ran a full hour on project management fundamentals, including what the first 90 days would look like when engaging a new client on a massive project.
A second candidate described a different experience: a standard recruiter screen, then a second interview with someone from the project team covering past projects, challenges, team management and retention of top performers. A third interview with the hiring manager and two project managers was cancelled shortly beforehand because the job specification had changed. Both candidates reported no offer.
If you are applying, prepare concrete stories on stakeholder management, conflict resolution and early-stage client engagement, and be ready to describe any ITIL or Service Catalog work you have done. It is also reasonable to ask the recruiter in writing which team the role supports and what the current job specification emphasizes, since the second account described that changing mid-process. With only two reports, treat the ITIL emphasis as a signal for some teams rather than a guarantee for every role.
Synthesized from 2 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 Quest Global process.
The process started with a recruiter screening call, which felt pretty standard. But things got messy after that. I had a second interview scheduled with someone from the project team, and that's where I started noticing issues. The questions themselves weren't problematic—they asked about my previous projects, what challenges I'd faced, how I'd handle team management and retention of top performers. Nothing I wasn't prepared for as a PM. But the vibe was off. There was an abrupt email exchange with their recruiting team, and then, fifteen minutes before my third interview—which was supposed to be with the hiring manager and two project managers—they cancelled. The reason? They'd changed the job specification and said they didn't want to waste my time. Which was ironic, because they'd already wasted it. The whole process felt disorganized and like they didn't have a clear picture of what they actually needed in the role. One of the project managers came across as genuinely rude, and I got the sense that interpersonal dynamics on their team might be a red flag. By the end, I wasn't surprised when the rejection came through.
Prep tip from this candidate
Be prepared for inconsistency and miscommunication in this interview process—the job spec may shift mid-way, so clarify role expectations early and in writing. If a project manager seems unprofessional or dismissive during initial calls, that's a legitimate signal about team culture.
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 Quest Global
How would you diagnose and speed up a slow SQL query when system metrics look healthy?
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Offer Matching API Design | |
| Azure Kubernetes Infrastructure | |
| Repository Policy Enforcement | |
| 2nd Highest Salary | |
| Top 3 Users | |
| Size of Joins | |
| Over-Budget Projects | |
| Google Maps Improvement | |
| Loan Model | |
| WAU vs Open Rates | |
| Uniform Car Maker | |
| Singly Linked List | |
| Merchant Acquisition | |
| Lasso vs Ridge | |
| Time Difference | |
| Duplicate Rows | |
| Bank Fraud Model | |
| k-Means from Scratch | |
| Boarding Times Bias | |
| Weighted Average Sales | |
| Docs Metrics | |
| Retailer Data Warehouse | |
| International e-Commerce Warehouse | |
| Testing Constraints | |
| Minimize Wrong Orders | |
| Rejection Reason | |
| Unified Inbox | |
| Client Solution Pushback |
Synthesized from candidate reports. Individual experiences may vary.
One candidate describes a standard recruiter screening call as the first step. Candidates may want to confirm the role's focus and the current job specification at this stage, since one report says the spec later changed.
One candidate describes a second interview with someone from the project team covering previous projects, challenges faced, and managing teams and retaining top performers. Another candidate described ITIL and Service Catalog questions, conflict resolution scenarios, and the three hardest career challenges. Expect experience-based questions.
One candidate reports a full hour on project management fundamentals, including a scenario about the first 90 days with a new client on a massive project. It required thinking through stakeholder management, scope definition and early relationship building. Whether every candidate gets this round is not established.
One candidate was scheduled to meet the hiring manager and two project managers, but the interview was cancelled about fifteen minutes beforehand because the job specification had changed. Both reported candidates ultimately received no offer, so this stage may not be reached in every process.