Three candidates describe UBS Product Manager interviews that open with an assessment or recruiter screen, then move to conversational, CV-based talks with a hiring manager or team, with uneven communication afterward.
$138K
Avg. Base Comp
$200K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
UBS Product Manager candidates describe a conversational process that leans on your own background more than on a case exercise. The three reports differ in shape, so read the sequence below as a range of experiences rather than a fixed pipeline.
One candidate began with an online assessment on cultural fit and cognitive skills, then had three calls with a hiring manager, a team member and HR. That person said each interviewer asked similar experience-led questions, including "What is something about yourself that's not on your resume?" and how they would use their work experience to drive impact. They also got situational prompts on stakeholder conflict and ambiguity. A second candidate had a recruiter phone screen followed by an in-person hiring-manager conversation at the New York headquarters. It covered "Tell me about yourself," "Why UBS?", strengths and weaknesses, how their experience matched the job description, and programming experience. A third described a competence test on technical tools, roadmap development and cross-functional leadership, then a meeting with a team leader and two colleagues.
The most useful preparation is specific examples of products you owned, how you prioritized a roadmap and how you led across functions, plus a clear, personal answer to why you want UBS.
Outcomes were mixed: one offer and two rejections. The offer came about three to four weeks after applying. The New York candidate reported more than two months and an automated-feeling rejection, and the third heard nothing after following up with the talent team. Timelines clearly varied, so follow up politely and don't read silence as a signal either way.
Synthesized from 3 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 Ubs process.
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 Ubs
Which model would perform better and why?
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Lasso vs Ridge | |
| Data Preparation for Imbalanced Data | |
| Stakeholder Communication | |
| Company Acquisition Choice | |
| Decision Tree Evaluation | |
| Martingale Strategy | |
| Your Strengths and Weaknesses | |
| Student Tests | |
| Statistically Significant Test | |
| Adam Optimizer | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Size of Joins | |
| WAU vs Open Rates | |
| Bagging vs Boosting | |
| Random SQL Sample | |
| P-value to a Layman | |
| Cyclic Detection | |
| Success Measurement | |
| Target Indices | |
| Fine-Tuning VS RAG | |
| Random Forest Explanation | |
| Type-ahead Search | |
| Missing Housing Data | |
| Precision and Recall | |
| Assumptions of Linear Regression | |
| Classification and Regression | |
| The Longest Journey |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe different openings. One took an online assessment on cultural fit and cognitive skills, another a competence test touching on technical tools, roadmap development and cross-functional leadership, and a third had a recruiter phone screen about their background and fit for the role.
One candidate met the hiring manager in person at the New York headquarters and was asked about their resume, fit with the job description, "Why UBS?", strengths and weaknesses, and programming experience. Another met a team leader and two colleagues, who described the team's structure across several locations in a friendly setting.
The candidate who had three calls with a hiring manager, a team member and HR said the questions were similar across interviewers and centered on their CV. They included what was not on the resume and how to drive impact in the role, plus stakeholder-conflict and ambiguity scenarios. One round had somewhat more technical depth for a tech-leaning role.
The candidate who received an offer finished with an HR round on fit and compensation expectations, with a decision about three to four weeks after applying. Two others describe poor communication: one got an automated-feeling rejection after more than a month of silence, and one received no reply after following up with the talent team.
