I spent the first few months at my job wondering why I kept getting pulled into conversations I hadn’t been hired for. My official role is on the analytics side, but I’d find myself in rooms where someone needed a thing explained, a memo drafted, a framework made human enough to actually use. I assumed this was temporary, a gap being plugged while they found someone else. It took longer than I’d like to admit to understand that I was the someone else, and that this was the job.
The thing I’ve been trying to articulate since then is something I don’t think gets said clearly enough about how stacking actually works in practice. The essay I wrote a few months ago argued that the value in combining two skill sets is the friction between them, the interference, not the addition. That’s still true. But there’s a more specific claim inside that one that I want to sit with here: the second skill in your stack is most powerful not when it makes you more versatile, but when it makes your primary skill more visible to the people who need to hire or deploy it.
Let me try to say this more precisely. Analytics, on its own, produces outputs: models, dashboards, numbers with confidence intervals. These outputs are useful. They are also, frequently, inert. A finding that can’t be explained to a non-technical decision-maker doesn’t move anything. It sits in a spreadsheet. Someone with the ability to translate that finding, to build the argument around it, to make the implication feel urgent rather than abstract, is not doing supplementary work. They’re the reason the primary work lands at all.
I’m not describing communication skills as a nice soft complement to a hard skill. I’m describing something more structural. There are fields, and finance is one of them, where the bottleneck isn’t analysis. The analysis is being done. The bottleneck is interpretation, the move from what the numbers say to what anyone should actually do about it. A person who can do both doesn’t just have two things going for them. They eliminate the bottleneck. The value proposition is different in kind, not just in degree.
This matters especially for people coming out of humanities degrees, because the skill most humanities training actually builds is precisely the one that eliminates that bottleneck. Close reading, argument structure, the ability to hold a complicated claim and follow its implications through: these are not decorative additions to a quantitative toolkit. They’re the mechanism by which quantitative work gets used. The frustrating irony of the current moment is that humanities graduates are often told to apologize for or minimize the thing that would most differentiate them, to lead with the Excel skills and mention the writing almost as an afterthought, as if the writing were the liability rather than the asset.
I want to be careful here because I don’t think this argument applies to every combination of skills, and I’d rather be honest about where it holds than oversell it. The condition for the second skill to do this kind of work is that it has to address a genuine constraint in the field you’re entering. Communication capacity eliminates a real bottleneck in finance and consulting and policy work and a lot of technical domains because those fields have been producing analytical outputs that sit unused for decades. The second skill that makes a surgeon’s primary skill more visible is probably not essay writing. The question worth asking is where the work you’re trying to do actually gets stuck, and whether you have something that unsticks it.
For most people reading this, the honest answer is probably yes, and they haven’t framed it that way because nobody told them they could. The writing, the ability to argue, the training in how ideas relate to each other: these aren’t things you do despite having a non-linear path. They’re what your non-linear path was quietly building the whole time.
I think about this when I look at how I ended up in the rooms I mentioned at the start. I wasn’t pulled in because I was a generalist or because I was flexible or because I happened to have a couple of things on my resume that covered a gap. I was pulled in because the gap was real and structural, and the combination of skills I’d stumbled into was the specific shape that fit it. That’s a different thing to believe about yourself than “I can do a few different things.” It asks you to look at the field you’re entering, find where its work actually gets stuck, and make the case that what you can do is why it moves.
That case is harder to make in a cover letter than “proficient in Python.” It requires knowing the field well enough to name its bottleneck out loud. But it’s also, when it works, the case that’s genuinely hard to argue with, because you’re not asking someone to take a chance on an unusual background. You’re showing them the mechanism by which the unusual background solves a problem they already have.