A HireVue-style video interview is an asynchronous screening where a candidate records timed answers to set prompts, usually without a live interviewer. In investment banking recruiting, it sits ahead of first-round calls as a high-volume filter that produces a replayable record of what you said and how you said it.
Treat it like a written memo you happen to deliver on camera. The platform is the pipe. The bank owns the rubric, the reviewers, and the decision.
Why HireVue matters in investment banking recruiting
Banks use asynchronous video for three practical reasons: speed, comparability, and auditability. First, it removes calendar friction when they have thousands of candidates and a narrow hiring window, so speed matters. Second, it puts every candidate under the same prompt and the same clock, which makes comparisons cleaner and reduces internal debate. Third, it creates an artifact that can be re-reviewed, re-scored, and audited if a decision is questioned later.
Your incentives are different because you want to stand out and signal fit. However, the format limits personality as a differentiator, so the edge comes from avoiding errors, using tight structure, and proving you understand the job as it is, not as it is marketed.
Investment banking rewards concise reasoning, steady energy, and basic technical hygiene. Creativity is welcome later, but the first gate is simple: can this person communicate under constraint and ship work without creating extra cost?
What banks actually score (even if they never say it out loud)
Most banks don’t publish a scoring model, so you should assume a practical rubric. In practice, the first pass is a rubric exercise run by junior bankers, recruiters, or trained screeners. They are not hunting for hidden genius. Instead, they are sorting for signal and filtering out avoidable risk.
The four buckets reviewers return to
Communication under constraint comes first because it is the closest proxy for day-to-day execution. A clear thesis, a controlled pace, and a logical sequence matter more than fancy language. If you can’t structure a two-minute answer, you probably won’t structure a client email at 1:00 a.m. when an associate wants two bullet points and a recommendation.
Motivation and role realism comes next because banks want low flight risk. Specificity beats enthusiasm. “I like finance” tells the reviewer nothing. “I want sell-side M&A because I’ve supported diligence and built valuation outputs under a deadline, and I validated the hours by speaking with two analysts and shadowing a live process” reads as lower risk.
Judgment and professionalism is the quiet gatekeeper because regulated firms screen for controllability. Conservative language, respect for confidentiality, and an instinct for compliance signal you can represent the franchise without drama.
Technical foundation matters where tested, but it’s usually a fragility check. Basic accounting linkages, enterprise value logic, and valuation method awareness get you through the gate. Deep modeling typically comes later, when they can probe in a live setting (and when you may be asked to complete a test like a clean DCF model or quick comps page).
A common mistake is treating the screen like a speech contest. Banking is an output business. On video, that translates to answers a reviewer can summarize cleanly in two bullets without squinting.
Why the medium is unforgiving (and how to use that to your advantage)
The clock forces prioritization, which is exactly what bankers do under deadlines. The one-sided format removes conversational repair, so you cannot clarify and adjust midstream. As a result, if you ramble or leave ambiguity, the reviewer has no reason to rescue you.
Production quality has more impact than candidates expect because it signals operating discipline. Reviewers are not film critics, but sloppiness on camera looks like sloppiness on a deck, and sloppiness is expensive.
Setup: make it a controlled production
Your setup should reduce randomness and preserve energy for content. Use a stable laptop or desktop, not a handheld phone. A basic 1080p webcam is enough. Audio matters more than video, so a cheap wired microphone or wired earbuds often beats a fancy camera with poor sound. If Bluetooth introduces dropouts, it will cost you quietly and permanently.
Lighting should make you easy to read. Face a soft light source. A window in front of you works if it isn’t harsh. Avoid backlighting, which turns you into a silhouette and drains presence.
Framing should look intentional. Frame head and upper torso, keep your eyes near the top third of the screen, and set the camera at eye level. A low angle reads as careless and can distort facial cues.
Your background should be neutral and scrubbed. Keep it uncluttered and remove anything sensitive such as client materials, whiteboards with notes, or documents with personal data. A messy background tells the reviewer you don’t control your workspace, which is not the message you want in an execution job.
Connection and notifications should be locked down. Use wired internet if you can. Close bandwidth-heavy apps, disable notifications, and silence your phone. A pop-up alert in the middle of an answer is a self-inflicted credibility hit.
Your wardrobe should be visually non-controversial. Dress one notch more formal than you think you need. For most IB screens, that means a conservative jacket, solid shirt, and minimal pattern so the reviewer can focus on your content.
Finally, practice in the exact setup you’ll use. Rehearsing casually and recording formally is like practicing a model on paper and building it in Excel for the first time during a client review. If you want a useful parallel, think of this like building an “audit-ready” workflow where inputs and outputs behave predictably, similar to an audit-ready inputs tab.
Mechanics that change how you answer
Most platforms follow a simple sequence: read time, record time, submit. Some allow retakes, others don’t. Therefore, know the rules before you start so you don’t waste mental bandwidth during the recording.
During read time, often 15 to 30 seconds, outline a three-part answer. Don’t memorize sentences because memorization increases the odds you freeze if you lose a phrase.
During record time, win the first 20 seconds. Reviewers form an early impression and then look for confirmation. Lead with a thesis so the rest of your answer is interpreted through a favorable frame.
If you have retakes, use them for execution errors, not for chasing perfect. Multiple retakes tend to produce a flat, scripted cadence that sounds less believable.
Some platforms show the question while you speak, while others hide it. If it hides, you need a structure you can hold in your head: thesis, two proofs, tie-back.
If you need accommodations, request them early and in writing. Large financial institutions have formal processes. Waiting until the last day increases timing risk and creates avoidable stress.
A structure that holds up under a timer
A reliable format for most investment banking video prompts is Thesis, Evidence, Transfer. This mirrors how bankers communicate: conclusion first, support second, relevance always.
- Thesis: Answer the question directly in one sentence.
- Evidence: Give two specific facts, examples, or metrics that support the thesis.
- Transfer: Link your evidence to the analyst or associate role in one sentence.
A disciplined behavioral framework: STAR with reflection
For behavioral questions, use a disciplined STAR variant because it prevents wandering. Keep Situation and Task to one sentence each, then spend most of your time on Action and Result. Add a reflection line because junior performance is feedback-driven and people who adjust quickly save teams time.
- Situation/Task: Set context in two short sentences total.
- Action: State what you personally did in two sentences.
- Result: Use one measurable outcome or a concrete deliverable.
- Reflection: Say what you would repeat or change next time.
Core scripts that cover most HireVue question banks
You’re not memorizing paragraphs, so aim for modular building blocks you can recombine under a timer. If your recruiting process includes broader prep, it also helps to understand the larger timeline and expectations in IB recruiting timelines.
Walk me through your resume (90–120 seconds)
The goal is coherence and forward motion, not a list. Start with a one-sentence throughline, choose two proof points, and end with why IB now.
“I’ve been building toward investment banking through finance exposure, execution-heavy roles, and evidence I can perform under deadlines. I started with [foundation: major/coursework/leadership] that built [skill]. Then in [internship/project], I did [two concrete tasks] and learned [one lesson about quality control or client service]. Most recently, [role] confirmed I want IB because I like [specific workflow: diligence, valuation, process management] and the iteration cycle under time pressure. That’s why I’m targeting [group] and why I can contribute quickly as an analyst.”
Why investment banking? (60–90 seconds)
Role realism is the point of the question, so show you understand the workflow and the trade-offs.
“I want IB because I like transaction execution where the work product affects capital allocation decisions, and I’ve validated the workflow through [specific exposure]. In [deal/project], I enjoyed [diligence/valuation/process management], especially tightening outputs through revisions under deadline. I understand the job is detail-heavy and repetitive at times, and I’m comfortable with long hours because I’ve done [similar cadence] and stayed consistent. I’m focused on [group] because [industry interest + skill fit + credible reason tied to the bank].”
Why this bank? (45–75 seconds)
Use three anchors: platform, people, and fit. Keep it verifiable and avoid marketing language.
“One reason is the platform: [one verifiable fact about the franchise relevant to your target group]. Second is the people: after speaking with [person/team] I learned [specific detail about how they work]. Third is fit: my background in [X] maps to [Y], and I want to deepen [specific skill] here.”
Influence without authority (90 seconds)
Execution leadership matters more than charisma, so show you reduced friction and moved work forward.
“I influenced without authority by aligning stakeholders on a concrete deliverable and reducing execution friction. The deliverable was [what], with constraints [time/quality]. I clarified ownership, set a timeline, and produced a first draft so people could react to something real. The result was [time saved / errors reduced / decision speed improved]. It taught me to lead with the work product, not with opinions.”
Describe a failure (60–90 seconds)
Controlled damage and durable fix is the pattern. Pick something real but not disqualifying, then show how your process changed.
“I missed an assumption mismatch, it caused rework, and I changed my process. I built a checklist and added a peer-review step before sending versions. On the next [projects], outputs went out with fewer revisions and faster turnaround.”
Pressure and long hours (45–75 seconds)
Don’t claim you love pressure, so show a repeatable operating system instead. “In [example], I managed a sustained workload with competing deadlines. I triaged tasks, kept version control tight, and communicated early when timing or scope shifted. My escalation rule is simple: if a risk threatens the deadline, I flag it early with options. That keeps surprises out of the process.”
Light technicals worth scripting (fragility check topics)
If technical questions appear, they are usually there to catch fragility, so keep answers clean and consistent. If you want deeper practice on the basics, it helps to review common three-statement pitfalls like the ones covered in three-statement model errors.
Three statements (60–90 seconds)
Linkage first: “The income statement runs from revenue to net income. The cash flow statement reconciles net income to cash through operating, investing, and financing sections. The balance sheet shows assets equal liabilities plus equity, and cash ties across all three. For example, depreciation lowers net income, gets added back in operating cash flow, and reduces PP&E on the balance sheet.”
Enterprise value vs equity value (45–60 seconds)
“Equity value is the market value of the company’s common equity. Enterprise value is the value of the operations available to all capital providers. A common bridge is EV equals equity value plus net debt plus preferred and minority interests, and you adjust for non-operating cash based on your convention. The key is consistency and knowing what each metric represents.”
DCF vs comps (45–75 seconds)
“A DCF reflects expected cash flows and assumptions on growth, margins, and the discount rate. Comps reflect where the market is pricing similar assets, including sentiment and cycle expectations. Differences often come from near-term cycle views, terminal value assumptions, or capital structure.”
Delivery: sound natural while staying structured
Delivery should make your structure easy to score. Speak slightly slower than you think you should because under a timer people speed up and lose clarity. Use brief pauses between sections because a short pause reads as control.
Eye contact should be with the camera, not your own image. If you use notes, keep them as keywords near the lens because reading full sentences is easy to spot and reduces credibility.
End sentences decisively because upward inflection turns statements into questions. If you misspeak, correct once and move on because over-apologizing burns time and makes the error bigger than it is.
Recorded answers create real compliance exposure
Recorded answers are not private in the way candidates assume, so treat them like a bank work product. Avoid sharing proprietary information from internships such as client names, deal terms, or non-public performance. Instead, describe work at a high level and focus on your role and deliverables.
Avoid discussing material non-public information or implying access. If you were around sensitive data, say you followed information barriers and compliance protocols because that signals maturity.
Don’t volunteer protected personal information. Even if your intent is innocent, it complicates the process.
Don’t inflate your role because HireVue answers can be replayed and compared to later technical probing. “I built the model” is a claim that gets tested. If you supported the model, say exactly what you did: “I updated assumptions, audited outputs, and built sensitivity tables.” Accuracy beats bravado.
Don’t take shots at prior employers or teammates. Banks screen for people who can take pressure without blaming others.
A preparation plan that respects diminishing returns
Prep should look like a short production sprint, not an endless grind. Build a story inventory of six to eight stories covering leadership, conflict, failure, pressure, teamwork, initiative, and ethics. Each story needs a concrete result such as time saved, errors reduced, a process improved, or a deliverable shipped.
Script in bullets only: thesis and two proof points. Full scripts usually create a rehearsed tone. Then record and review for overruns, filler words, missing thesis, unclear ownership (“we” when you mean “I”), and weak results.
Stress test with random prompts because the real skill is structure under surprise. Have a friend read questions you didn’t pre-select so you practice thinking, not reciting.
Lock your setup 24 hours early. Do a full mock in the exact environment so nothing on the day is new.
Fresh angle: treat HireVue like a “two-bullet reviewer test”
One non-obvious way to improve answers fast is to optimize for how reviewers actually write notes. After each practice recording, force yourself to produce the two bullets a reviewer would type in an internal tracker: one bullet for “answer quality” and one for “risk.”
- Answer quality: Can you summarize your thesis and evidence in two clean lines without losing meaning?
- Risk: Did you introduce any reason to say no, such as rambling, confidentiality slips, inflated claims, or vague motivation?
- Decision rule: If you can’t write the two bullets, the reviewer probably can’t either, so tighten the structure and re-record.
This method works because it aligns your practice with the bank’s real bottleneck: fast, defensible screening decisions under time pressure.
What knocks candidates out fast
The quickest eliminators are execution errors, not philosophical disagreements. An incoherent “Why IB” signals low commitment. Inability to explain your current role signals weak self-awareness. Obvious exaggeration signals future reputational cost. Poor professionalism signals preventable risk. Failure to answer the question asked signals you won’t follow instructions on a live deal. Time mismanagement that cuts off your conclusion signals you can’t land the plane.
Banks don’t need perfection. They need confidence you won’t create avoidable downstream cost.
Closing Thoughts
HireVue is not a vibe check, so treat it like a timed work product: lead with a thesis, support it with specific evidence, and transfer it back to the job. If you control setup, structure, and compliance risk, you turn a one-sided recording into a clear signal that you can execute under constraint.