4) Technical and Professional Questions (the ones that decide offers)
This is where US interviews get very practical. You’ll be asked to do finance in real time: build a bridge, defend a multiple, explain why your DCF isn’t lying to you, and show that you understand the rules of the game (especially around public markets and compliance). If you’re interviewing as an Equity Analyst or Securities Analyst, expect even more pressure on valuation mechanics and catalysts.
Q: Walk me through a DCF you built—what are your key value drivers and why?
Why they ask it: They’re testing whether you understand what actually moves intrinsic value, not just Excel mechanics.
Answer framework: Driver-first DCF. Start with revenue drivers, margin structure, reinvestment, then discount rate.
Example answer: In my DCF, I anchor revenue to volume and pricing rather than a flat growth rate, because the business is capacity-constrained in the near term. I model margins with explicit fixed-versus-variable costs and a realistic ramp in operating leverage. Reinvestment is tied to working capital and capex as a percent of incremental sales, not a historical average. For the discount rate, I explain my beta choice, capital structure, and how I think about size and cyclicality, then I show a sensitivity table so the discussion is about ranges, not false precision.
Common mistake: Treating the terminal value as a plug and ignoring reinvestment needs.
Q: How do you pick comparable companies and valuation multiples for a relative valuation?
Why they ask it: They want to see if you can avoid lazy comps and explain “why this multiple.”
Answer framework: Business model–Unit economics–Cycle position–Accounting. Then pick the multiple that matches value driver.
Example answer: I start with business model similarity—revenue type, customer, and margin structure—then I check unit economics and growth durability. I adjust for cycle position because peak margins can make EV/EBITDA look artificially cheap. If accounting differs materially, I normalize or choose a metric less sensitive to it. Then I pick the multiple that matches the story: EV/Sales for early margin expansion, EV/EBITDA for stable cash generators, or P/E when capital structure is comparable.
Common mistake: Choosing comps by industry label alone and ignoring growth, margins, and cyclicality.
Q: Explain WACC like you’re talking to a PM who hates theory.
Why they ask it: They’re testing whether you can translate finance into decision language.
Answer framework: Intuition–Components–So what. Define it, break it down, then tie to valuation impact.
Example answer: WACC is the return the business has to earn to justify its price, given how it’s financed. It’s basically a blend of what equity holders demand and what lenders charge, weighted by the capital structure. In practice, if rates rise or the business gets riskier, WACC goes up and the present value of future cash flows drops—especially for long-duration growth names. That’s why I always show valuation sensitivity to WACC and terminal assumptions.
Common mistake: Reciting formulas without connecting to duration, rates, and risk.
Q: What’s the difference between GAAP earnings and free cash flow, and why do investors care?
Why they ask it: They want to see if you can spot earnings quality issues.
Answer framework: Bridge framework. Start at net income, adjust non-cash, working capital, capex.
Example answer: GAAP earnings include non-cash items and accounting timing, while free cash flow reflects cash generated after operating needs and capex. Investors care because cash pays down debt, funds buybacks, and supports dividends—earnings don’t. I bridge net income to operating cash flow by adjusting for depreciation, stock-based comp, and working capital swings, then subtract capex to get to free cash flow. If earnings are up but cash is down, I immediately ask what’s happening with receivables, inventory, or capitalized costs.
Common mistake: Saying “cash flow is harder to manipulate” without showing you know the actual bridge.
Q: How do you model stock-based compensation (SBC) and dilution in a valuation?
Why they ask it: This is a classic “real analyst” question—SBC can quietly wreck per-share value.
Answer framework: Accounting–Economics–Per-share. Treat SBC as expense (economics) and model dilution explicitly.
Example answer: I treat SBC as a real cost because it’s compensation paid in equity, even if it’s non-cash. In the P&L, I keep it in operating expenses to reflect true margins, and in the share count I model dilution using treasury stock method assumptions or management guidance. If the company buys back shares, I check whether buybacks offset dilution or just mask it. Ultimately, I care about per-share free cash flow and per-share intrinsic value, not just enterprise value.
Common mistake: Adding back SBC “because it’s non-cash” and forgetting dilution.
Q: You’re covering a bank/insurer/REIT—how does your valuation approach change?
Why they ask it: They’re testing whether you know when standard DCF/EV metrics break.
Answer framework: Business-specific valuation. Explain why cash flow definitions and leverage differ.
Example answer: For banks, debt is more like raw material than financing, so EV-based metrics are less meaningful and I focus on P/TBV, ROE, credit quality, and NIM drivers. For insurers, I care about underwriting discipline, reserve adequacy, and investment portfolio risk, often using P/B and ROE with stress scenarios. For REITs, I shift to AFFO/FFO, cap rates, same-store NOI, and balance-sheet maturity ladders. The common thread is matching the valuation tool to how the business creates value.
Common mistake: Forcing EV/EBITDA onto sectors where it doesn’t fit.
Q: What regulations or standards affect how you communicate investment views in the US?
Why they ask it: They’re screening for compliance awareness—especially in public markets.
Answer framework: Name–Implication–Behavior. Mention the rule, what it means, and how you operate.
Example answer: If I’m on the sell-side, I’m mindful of FINRA research rules and Reg AC certification requirements around research integrity and disclosures, and I’m careful about conflicts and selective disclosure. More broadly, Reg FD matters when interacting with issuers—no trading on material nonpublic information, and no “wink-wink” channel checks that cross the line. In practice, I document sources, separate facts from opinions in my write-ups, and escalate anything that smells like MNPI.
Common mistake: Saying “I follow compliance” without naming what you actually do differently day-to-day.
Q: Which tools do you use for research and modeling, and how do you keep your work auditable?
Why they ask it: They want to know if you can operate in a professional stack and leave a clean trail.
Answer framework: Tool–Use case–Controls. Mention Excel, data terminals, and documentation habits.
Example answer: I build models in Excel with consistent structure—inputs, calculations, outputs—and I use version control conventions so I can roll back changes. For market and fundamentals, I’ve used Bloomberg and FactSet-style workflows, plus filings directly from SEC EDGAR when I need the source of truth. I keep an assumptions tab with dates and links, and I write a short change log after major updates so someone else can audit what moved and why.
Common mistake: Flexing tool names while ignoring model hygiene and traceability.
Q: Tell me about a time your model was wrong. What broke—assumptions, data, or logic?
Why they ask it: They’re testing intellectual honesty and whether you run post-mortems like a pro.
Answer framework: Post-mortem: Hypothesis–Failure point–Fix. Be specific and technical.
Example answer: I once underestimated working capital drag in a hardware name because I assumed inventory turns would normalize faster after a supply shock. The logic was fine, but the assumption was too optimistic and I didn’t stress-test a slower normalization path. After the miss, I added a working-capital sensitivity grid tied to lead times and channel inventory, and I started tracking distributor data as an early warning indicator. It improved my downside cases materially.
Common mistake: Blaming “the market” instead of identifying the broken link.
Q: If Bloomberg/FactSet is down on a volatile day, how do you keep coverage running?
Why they ask it: They want operational resilience—markets don’t pause for outages.
Answer framework: Prioritize–Fallback sources–Communicate. Keep it practical.
Example answer: First I’d prioritize what’s time-critical: price moves, news catalysts, and any positions with near-term risk. For data, I’d use exchange feeds and reputable public sources, pull filings and press releases directly from company IR pages and SEC EDGAR, and use broker emails or recorded calls if available. I’d communicate to the PM what’s confirmed versus pending and avoid making precision calls off partial data. Once systems are back, I’d reconcile and document any interim assumptions.
Common mistake: Freezing—or worse, guessing numbers and presenting them as facts.
Q: Build a quick sensitivity: what happens to valuation if rates move +100 bps?
Why they ask it: They want to see if you understand duration and can translate macro to a name.
Answer framework: Mechanism–Model impact–Narrative. Explain discount rate and fundamentals.
Example answer: A +100 bps move typically raises the risk-free rate component of WACC and can also widen credit spreads if risk-off, so the discount rate increases. In the model, that compresses the DCF value, with bigger impact on long-duration cash flows. I’d also check second-order effects: demand sensitivity, refinancing risk, and whether the company has pricing power to protect margins. Then I’d show a table: WACC up 50/100/150 bps with implied upside/downside.
Common mistake: Only changing WACC and ignoring fundamental impacts like refinancing and demand.