How to answer 'why TMT?'

Why the obvious answer fails

"I've always loved technology" is the single most common answer to this question, and it is also the weakest one, because every candidate sitting across from a TMT interviewer that day has said some version of it. The answer is not wrong so much as undifferentiated: it tells the interviewer nothing about whether you actually understand the group, and it invites exactly the kind of follow-up that exposes a candidate who has not gone past surface-level enthusiasm, like being asked to explain how a specific sub-sector actually makes money or why a particular deal pattern happens in TMT more than elsewhere.

The deeper problem with the generic answer is that it conflates being a consumer of technology with being interested in the businesses behind it. Liking your phone, using software products every day, or following technology news is a completely normal starting point, but it is not, by itself, evidence that you understand or care about the things a TMT banker actually spends their day on: coverage relationships, sector-specific valuation mechanics, and deal structures. An interviewer wants to see that gap closed.

What a strong answer actually contains

A strong "why TMT" answer has three components, in roughly this order: a specific reason you are drawn to the industry that goes beyond being a consumer of its products, a concrete demonstration that you have engaged with the sector's business mechanics rather than just its headlines, and a forward-looking connection to what you want to do in the seat, not just why you find the sector interesting in the abstract.

The first component should name something real and personal, but it should be about the business dynamics, not the products. Maybe you find the sub-sector diversity itself compelling, the fact that a single coverage group spans businesses as different as high-growth software and capital-intensive telecom, and you like the intellectual range that requires. Maybe you have a specific sub-sector you gravitate toward, software, semiconductors, media, and a genuine reason tied to how that business works, not just that you like the products it makes. Vague passion for "innovation" or "disruption" reads as filler; specificity about a business model or a dynamic within the sector reads as real interest.

The second component is where most of the actual preparation work in this guide pays off directly. Reference something concrete: the reason revenue multiples replace EBITDA multiples for high-growth software, discussed in how software companies are valued, or the mean-reversion logic in semiconductor valuation, discussed in semiconductors: the cycle and the value chain, or a deal pattern like the software take-private, discussed in the TMT deal structures article. You do not need to recite a textbook definition; you need to demonstrate, briefly and naturally, that you have actually spent time with the mechanics rather than only the narrative.

The third component connects your interest to the actual job, described in what TMT investment bankers actually do: the origination work, the client relationships, the pace of sector-specific news you would need to track. This is the part that separates a candidate who wants to work in TMT from one who simply likes technology as a topic, and it is worth being specific about which parts of the actual role you are looking forward to, not just the sector label.

Weak signal versus strong signal

It helps to see the contrast laid out directly, since the difference between a weak and a strong answer is often more about specificity than content.

Tailoring the answer, and a common overcorrection

Tailoring the answer to the seat

The right level of specificity also depends on who is asking. Recall from the sub-sector map discussion that some banks run a unified TMT group while sector-focused boutiques concentrate on one or two sub-sectors, usually software and internet. Interviewing with a boutique that lives and breathes software all day calls for a sharper, more specific answer about that sub-sector than interviewing with a bulge bracket group that covers everything from semiconductors to telecom; at a generalist shop, demonstrating comfort across the sector's breadth is itself part of a strong answer, while at a specialist shop, a broad answer that never commits to a specific sub-sector can read as less differentiated than it would elsewhere. Adjust which parts of your answer you lean on, but keep the same underlying structure regardless of audience.

A common mistake: reasoning versus reciting

A subtler failure mode than pure generic enthusiasm is over-correcting into reciting definitions without connecting them to anything personal. A candidate who has clearly memorized this guide's explanation of why revenue multiples replace EBITDA multiples for software, but delivers it as a flat definition rather than in service of explaining a genuine interest or observation, has fixed the specificity problem but created a new one: the answer now sounds rehearsed rather than reasoned. The fix is the same in both directions: use the mechanics to support a point you actually believe, rather than treating the mechanics as the point itself. An interviewer can tell the difference between a candidate explaining a concept because it illustrates something they find genuinely interesting and a candidate reciting a concept because they know it will sound impressive.

Traps interviewers set on purpose

A few follow-ups come up often enough that you should expect them rather than be surprised by them. The first is a request to name a specific sub-sector you find most interesting and explain why, which is designed to catch candidates whose "why TMT" answer was actually only about one narrow slice of the group dressed up as broader enthusiasm; being ready to go one level deeper on at least one sub-sector, using the sub-sector map as your outline, closes this gap. The second is asking you to name a recent-enough-to-be-relevant but not current-events-dependent deal or company dynamic that illustrates your interest, which tests whether your knowledge is actually current in the sense of understanding ongoing dynamics, not memorized from a single article. The third, more subtle trap is asking why you want TMT specifically rather than another group with similarly high deal volume, which is really asking whether you understand what makes TMT's coverage economics genuinely different from, say, healthcare or industrials, not just similarly busy. A good response to this version of the question leans on the breadth argument directly: few other coverage groups ask a banker to hold as many genuinely different valuation frameworks in their head at once, and that breadth, not just the deal count, is the actual differentiator worth naming.

A model answer structure

Here is how the three components fit together in practice, adaptable to your own specific interests rather than copied verbatim: state a specific reason tied to business dynamics, not products; demonstrate real engagement with one piece of sector mechanics; connect it to the actual coverage role. For example, a candidate could open with genuine interest in how differently software and telecom get valued despite sitting in the same coverage group, use that as a bridge to explain the reinvestment logic behind software's revenue multiples in one or two sentences, and close by connecting that interest to wanting to build the kind of sector fluency a coverage banker needs to have a credible point of view across such a wide range of business models. The specific content should be yours and should reflect what you have actually engaged with, not a script, but the shape, personal reason, demonstrated mechanics, connection to the role, holds regardless of which sub-sector or dynamic you choose to lead with.

Why specificity matters more than passion

Interviewers are not grading how much you love technology; they are grading whether you have done the work to understand a genuinely difficult, heterogeneous coverage group well enough to be useful in it quickly. A candidate who answers with real specificity about business mechanics, even modest specificity, reads as someone who will ramp up faster and need less hand-holding than a candidate who answers with pure enthusiasm and no substance behind it. This is also, not coincidentally, exactly the quality that determines success in the actual seat once you have it, described fully in what TMT investment bankers actually do and in exit opportunities from TMT, since the ability to hold multiple valuation frameworks in your head and reason from business fundamentals rather than surface-level familiarity is the same skill the fit question is quietly testing for.

Practice question

Why TMT specifically, rather than a generalist group or another coverage sector?

What draws me to TMT is the range it actually requires. It's the one coverage group where I'd need real fluency in genuinely different valuation logics, revenue multiples and retention metrics for a software company, cycle-adjusted EV/EBITDA for a semiconductor company, leverage capacity built on stable, contractual cash flow for a telecom carrier, all inside the same group. I find that intellectually more interesting than a coverage sector where the businesses resemble each other more closely, because it means the job never really lets you coast on one mental model. Concretely, what pulled me in was understanding why EBITDA multiples break down for a fast-growing software company: the business is often intentionally suppressing earnings by reinvesting gross profit into customer acquisition, so the market prices it on revenue or ARR instead, adjusted for growth. Once I understood that, I started noticing the same kind of logic everywhere else in the sector, why semiconductor multiples compress right when earnings peak, why telecom can carry so much more leverage than software with the same EBITDA, and that pattern, valuation following the actual economics of the business rather than a fixed formula, is what makes me want to build a career on this group specifically. On the day-to-day side, I like that TMT coverage work means staying genuinely current on a fast-moving set of businesses and being ready to have a real point of view when something happens in the sector, not just executing a static process.

What the interviewer is listening for: Specific, business-model-level reasoning rather than product enthusiasm, evidence that you have actually engaged with sector mechanics beyond headlines, and a clear connection between that interest and the actual coverage role.