The scenario
The AI interviewer describes a client: 52 years old, planning to retire at 62, moderate risk tolerance, with most of their savings sitting in company stock from decades at one employer. You're asked to reason through a rebalancing recommendation out loud, then defend it against a follow-up: what if the client resists selling any of the company stock for tax and sentimental reasons.
The right answer isn't a single number, it's whether your reasoning holds up once the client pushes back, which is exactly how a real suitability conversation plays out.
What gets covered
Expect a portfolio scenario grounded in a specific client age, goal, and risk profile, a suitability check where you flag whether a recommendation actually fits that client or just a generic model, and a follow-up that pressure-tests your first answer the way a real client conversation would.
Expect the interviewer to also ask about the tax and behavioral side of a recommendation, why a client holding concentrated stock resists diversifying even when the math clearly favors it, since that resistance is a real part of the job, not just a modeling exercise.
A written challenge format is also available for drafting a client-facing explanation of a recommendation, closer to how you'd actually send one than describing your reasoning out loud.
Scoring
How scoring applies here
Calibration floors and caps matter more in this session than almost anywhere else in the role's practice options, since portfolio reasoning has a checkable logic underneath it.
A confident explanation that skips the actual suitability check, whether the recommendation fits this client's stated risk tolerance rather than a firm's average client, won't score higher than a less polished answer that gets the reasoning right.
The Technical dimension carries the specific weight here, with written reasoning explaining what held up and what didn't in your recommendation, and Communication is graded alongside it since a correct recommendation that's explained in jargon a client couldn't follow still falls short of what the role actually needs.
Frequently asked questions
Is this a code editor or a spoken conversation?
A spoken conversation. The technical flow begins with a written challenge stage suited to advisory work, a suitability or portfolio-math exercise, and code never enters the picture for this role. A written challenge format is available separately for drafting a response instead of speaking it.
Will the client scenario include a specific age and risk profile?
Yes. The session grounds the recommendation in a specific client situation, since suitability reasoning depends on those details rather than a generic allocation.
How is a confident-sounding but wrong recommendation scored?
Lower than a less polished one that gets the suitability reasoning right. Calibration floors and caps mean tone alone can't push a score above what the actual reasoning supports.
Can I practice drafting a client explanation instead of speaking it?
Yes, through the written challenge format, which lets you write out a client-facing recommendation the way you'd actually send one.
Will it ask about client resistance, not just the math?
Often, yes. A recommendation that's numerically sound still has to survive a client who resists it for tax or sentimental reasons, and that follow-up is part of the reasoning being scored.
Related pages
Practice a financial advisor technical interview
Reason through a portfolio recommendation and defend a suitability judgment out loud, then see whether the logic actually held up.