What Goes in the Skills Section of an IB Resume

Most students treat the Skills section like a trophy case. They cram it with every tool they've ever opened, every framework they half-remember, and a confident line that reads "Financial Modelling." It feels productive. It feels like you're proving something. It's also the section interviewers care about least, and the one place where trying too hard quietly works against you.

Here's the truth that reframes the whole thing: the Skills line is more or less table stakes, and it is never explicitly asked about in an interview. No one is going to sit you down and quiz you on whether you really know PowerBI. Which means your job here isn't to impress. It's to be accurate, be brief, and avoid the small mistakes that make a sharp reader raise an eyebrow.

And there's a payoff that surprises people: done right, you may not need a Skills section at all.

Let me walk you through exactly what belongs in it, what doesn't, and how to tell whether you should keep the line or drop it entirely.

Where Skills Actually Sits, and Why That Matters

Skills lives inside "Additional Information," which sits at the very bottom of your resume. That placement isn't an accident, and it isn't a flaw. A resume is designed to increase in specificity as you read from top to bottom, with the most general, lowest-stakes material at the bottom. The label "Additional Information" tells you everything: this is an addition to the core of your resume, the least relevant tier.

So when you're deciding how much energy to pour into your Skills line, calibrate to that reality. This is not where you win the interview. It's where you avoid losing a sliver of credibility through carelessness. Get it clean, get it accurate, and move your real effort up the page to your experience bullets, where candidacy is actually decided.

What Actually Goes in the Skills Line: Software, and Only Software

There are two buckets to draw from, and the order matters. Lead with the financial platforms, because those are what signal you've spent real time in the tools of the trade. A few non-financial tools can follow.

Non-Financial | Microsoft Office Suite, Python, PowerBI, SQL, etc.

Financial | Bloomberg, Capital IQ, Refinitiv Eikon, Preqin, Pitchbook, FactSet, etc.

A clean Skills line pulls from these two lists and stops there. List the platforms you genuinely know, the ones you could open and navigate if an interviewer handed you a terminal. The financial names are the heart of it. Microsoft Office, Python, PowerBI, and SQL round out the non-financial side and show you can handle data, but they're supporting cast. The Bloomberg, Capital IQ, Refinitiv Eikon, Preqin, Pitchbook, and FactSet end of the spectrum is what makes the line worth having.

One quiet bonus: the software you list also reads as keywords. Applicant Tracking Systems scan for terms that match the job description, and these platform names are exactly the kind of relevant vocabulary that helps your resume clear the algorithmic filter. For the full mechanics of how ATS scanning works and how to write for it, see our guide on how to get an investment banking resume past the ATS. Here, just know that naming real tools quietly works in your favor on two fronts at once.

What Does NOT Go in It: "Hard" Skills Like Financial Modelling

This is where most students stumble. They write something like "Financial Modelling" or "Valuation" or "DCF Analysis" in their Skills section, thinking it broadcasts competence.

Here's the reasoning, and it's worth sitting with. Whatever you currently understand to be "financial modelling" is baby food to the investment professionals and bankers reading your resume. To them, modelling isn't a skill you list, it's the ambient air of the job, the thing everyone does all day without remarking on it. When a student announces "Financial Modelling" as a credential, it reads the way "proficient in email" would read on an analyst's resume. It signals that you think a baseline expectation is a distinguishing achievement, which tells the reader you don't yet understand the standard you're being measured against.

There's a deeper principle underneath this. Listing a hard skill as a bare label is a claim with no evidence. Anyone can type "Financial Modelling." It costs nothing and proves nothing. Software names, by contrast, are checkable and specific: either you've used Capital IQ or you haven't. That's why software belongs in the Skills line and competencies don't. The line is for verifiable tools, not for self-assessments.

So where do your modelling abilities actually live? In your experience bullets, where you show them in action rather than assert them in a vacuum. Which brings us to the most useful move in this entire section.

The Advanced Move: When to Drop the Skills Line Entirely

Here's the contrarian payoff I promised. A standalone Skills line is unnecessary if you've already woven your financial software and your financial models into the bullet points across your resume.

Think about why. The Skills line exists to communicate two things: the platforms you can use and the analytical work you can do. But if your experience bullets already say "assessed valuation multiple evolution using Capital IQ" or "built a NAV valuation model in a 15-page investment memo," then you've demonstrated both, in context, with evidence attached. Restating "Bloomberg, Capital IQ; Financial Modelling" at the bottom is redundant at best and, in the case of the modelling label, actively harmful.

Showing beats telling every time. A tool named inside a real deliverable proves you used it. The same tool sitting in an isolated list proves only that you can spell it.

So how do you know if you've cleared the bar? There's a concrete threshold:

A standalone "Skills" line is unnecessary if you've woven at least 3 financial software platforms and 3 financial / valuation models into your bullet points. The models that count: DCF, LBO, Comps, Precedents, 3-statement, Operating, and M&A.

If your bullets already reference three or more of those platforms and three or more of those model types, you've covered everything a Skills line would have said, and you've said it with proof. Drop the line. Use the recovered space for something that actually builds your candidacy.

If you haven't hit that threshold, if your software and modelling exposure is thin or doesn't appear naturally in your experiences, then keep "Skills" as a standalone line in your Additional Information section. It's the floor that ensures the information is on the page somewhere. Just remember it's a floor, not a flex.

Keep It in Proportion

Because Skills is low-stakes, don't let it sprawl. Your entire Additional Information section should run no more than four lines. In practice, just "Skills" and "Interests" will usually do. If you've got nothing meaningful to add beyond that, don't feel compelled to manufacture filler to fill space.

And here's the contrast that puts Skills in its proper place. The Skills line is table stakes and never explicitly asked about. The line right below it, Interests, is the opposite: almost every interviewer will ask about it, certainly in superdays and commonly at the end of first rounds, right before they invite your questions. So spend your thought accordingly. Get Skills clean and accurate in thirty seconds, then put real care into the line that interviewers actually engage with. For how to make that line build rapport before you've said a word, see our guide on writing the interests section of an IB resume.

That's the whole discipline of the Skills section. Software only. No hard skills. And if your bullets already do the work, no Skills line at all. It's one of the few places on your resume where the most sophisticated move is to do less.