An opinionated library of books on markets, deals, investing, product, software and decision making, with the lesson to take from each and who it is useful for. Nobody needs all of it. Two from the shelf closest to the seat you want will do more in February than twenty you started and did not finish.
72 books, on 13 shelves.
One book each for capital allocation, forensic accounting, decision quality, valuation and idea generation. Finish these and you have something to say in any finance interview you are likely to sit.
A chief executive is a capital allocator first and an operator second.
An edge usually starts as something you already understand better than the market.
Five to seven of these, in an order, for one kind of candidate. Faster than reading a shelf and better than guessing.
First and penultimate years going for a spring week or a summer analyst seat, with no finance background and a term to get ready in.
6 items, in order
Candidates in an on-cycle or off-cycle process who can already build an LBO and need something to say when the modelling stops.
6 items, in order
Anyone who will be asked to bring a stock to the room, on either the buy side or the sell side.
7 items, in order
Sales and trading, commodities and quant candidates, where the questions are about market structure rather than about a company.
6 items, in order
Product, associate product manager and technology strategy candidates, including people moving across from finance.
7 items, in order
Someone with a first interview in days, no finance background, and no time to read a book.
5 items, in order
All 72 entries, on 13 shelves.
Start here if you are aiming at a buy-side seat or you want a stock pitch that sounds like it came from someone who has held a position rather than modelled one.
What to notice. An edge usually starts as something you already understand better than the market.
The case for buying what you already understand, and the ancestor of every "tell me about a stock you like" answer that actually works.
It is the model for the stock you bring to the room: a business you can explain without notes and a reason the market is wrong.
What to notice. Price is what the market offers you today. Value is the separate question.
Margin of safety and Mr Market. Read chapters 8 and 20 first and take the rest slowly; much of it is a period piece and the two ideas are the point.
Margin of safety is the phrase every value fund is listening for, and chapter 8 is where you learn to use it without sounding like a quotation.
What to notice. Follow the fee before you follow the advice.
A 1940 book about fees and incentives that has not dated in a single respect. Short, funny and quietly the most cynical thing on this list.
Asked why active management is under pressure, the fee answer is the one that does not need a chart.
What to notice. A handful of outcomes carries a portfolio, and a career.
Why sensible people do unsensible things with money. The chapter on how a few outcomes carry an entire portfolio is worth the book on its own.
It gives you a non-technical answer to how you think about risk, which is what wealth and asset management interviews are actually probing.
What to notice. An analyst’s day is idea generation, evidence and sizing, in that order.
A hedge fund analyst’s working process, from idea generation through to position sizing. The closest thing in print to a job description for a research seat.
Asked how you would spend your first week as an analyst, this is the book that makes the answer specific.
What to notice. Traders who agree on nothing else all agree about risk control.
Interviews with traders who made money in incompatible ways, which is the point of it. Read across the volumes and the only factor left in common is risk control.
It stops you claiming there is one right way to trade, which is the answer a markets interviewer is hoping you will not give.
What to notice. Low risk and high uncertainty are not the same thing.
Low risk and high uncertainty are not the same thing, and the gap between them is where returns come from. A short book built entirely on that distinction.
The distinction gives you a precise answer when you are asked what makes a situation attractive rather than merely cheap.
What to notice. Each seat on the buy side is a different job, not a different asset.
Interviews across every asset class, conducted by someone who built one of them. The fastest way to learn what each seat on the buy side does all day.
It is the cheapest way to stop confusing private equity, growth and credit, which candidates do constantly.
What to notice. A commodity index does not return what the spot price did.
Contango, backwardation and why a commodity index does not return what the spot price did. Thinly covered elsewhere, which is what earns it a place.
What to notice. One person’s record is a story about survivorship until proven otherwise.
A 1960s account of trend following by a dancer reading cables on tour. Treat it as a document about discipline and survivorship rather than a method to copy.
What to notice. A setup without an exit rule is not a strategy.
Setups, stops and the machinery of short-term trading. Relevant if you are aiming at a markets desk rather than a deal team, and largely wasted effort if you are not.
Read one of these before any private equity, corporate development or growth interview. They are where the language of capital allocation actually comes from.
What to notice. An auction is won on certainty and speed as often as on price.
The RJR Nabisco buyout in full. Still the best account of how a competitive auction runs and what fee structures quietly do to advice.
Asked why a seller might not take the highest bid, this gives you three reasons that are not theoretical.
What to notice. A chief executive is a capital allocator first and an operator second.
Eight chief executives judged on capital allocation and nothing else. If you read one book before a private equity interview, make it this one.
It gives you the vocabulary for what a sponsor does after the close, which is exactly where most candidates run out of things to say.
What to notice. A fund is a fundraising business before it is an investing one.
A Blackstone founder on building the firm. Read it for the fundraising chapters and for how close the business came to ending in 1987.
Understanding where a fund’s capital comes from separates a candidate who has read about private equity from one who has thought about it.
What to notice. The buyer with liquidity when nobody else has any sets the price.
Real estate, distressed assets and a plain account of buying when nobody else will. The most direct voice on the list.
Distressed and special situations interviews want to hear that you understand who is forced to sell and why.
What to notice. A capital structure is a set of rights people will litigate over.
A restructuring fought from the creditor side. Dense, and the best introduction anywhere to covenants, fraudulent conveyance and how a capital structure gets torn apart.
Restructuring groups ask what a covenant actually does. This is the book where covenants stop being a bullet on a term sheet.
What to notice. Growth consumes cash, and a profitable company can still run out.
A memoir that is mostly about working capital. Nike nearly died of its own growth, repeatedly, and the book is honest about why.
Why a profitable company goes bust is a standard technical question, and this is the version of the answer you will remember.
What to notice. Most of the economy is businesses nobody writes about.
Founders in unglamorous industries. A corrective if your mental model of business has been built entirely from technology coverage.
What to notice. Most founding stories are a pivot nobody planned.
Founder origin stories drawn from the interview series. Light going, and a reliable source of examples when you are asked which business you admire.
The shelf that does the most work per page. Interviews test how you decide under uncertainty far more often than they test what you know.
What to notice. A good decision and a good outcome are separate things.
Separating decision quality from outcome quality. This is the single most useful idea on the whole list for an investing interview, and the cheapest to acquire.
Asked about an investment that went wrong, the answer that separates the process from the result is the one that gets a second round.
What to notice. Anchoring and base rate neglect are the two that cost money.
The research behind every behavioural question you will be asked. Anchoring and base rate neglect are the two to be able to explain with an example of your own.
Naming the bias you are most prone to, with a real example, answers a behavioural question that most candidates deflect.
What to notice. The market misprices what is hard to measure.
Where a statistical process beat a scouting one, told properly. The argument runs straight through quant investing and through how firms screen the people they hire.
It is the clearest available answer to what a systematic edge is and why it decays once everyone has it.
What to notice. Arguing one side at a time beats arguing all of them at once.
A structure for arguing a position from several sides in turn. Directly applicable to a group case, where the candidate who organises the discussion scores better than the one who talks most.
In a group case, offering a structure is worth more than offering an answer, and this is where you get one.
What to notice. Performance under pressure is a separate skill from competence.
A working model of the emotional brain, aimed at performance under pressure. Worth reading before an assessment centre if nerves are your binding constraint.
Nothing marks out a candidate faster than being able to place today against something that already happened. These four cover four centuries between them.
What to notice. Every bubble runs displacement, boom, euphoria, distress, revulsion.
The anatomy of a bubble, repeated across four hundred years. Once you have the sequence from displacement through to revulsion, you start seeing it in live markets.
Asked whether something is a bubble, naming which stage it is in beats yes or no by a distance.
What to notice. A bubble needs marketability, money and credit, and speculation together.
A newer and more data-led treatment of the same question. The fire triangle framing of fuel, oxygen and heat is genuinely usable in an interview answer.
The three-part framing gives you a structure for the bubble question rather than an opinion about it.
What to notice. Physical traders make money on logistics and access, not on a price view.
Commodity traders as the least visible and most consequential firms on earth. Read it before any physical commodities or trading house interview.
Commodity houses ask what they actually do. Arbitraging place and time, not direction, is the answer they are waiting for.
What to notice. Antitrust and securities law were written against specific people.
American industrial consolidation and the fortunes it created. Background for why antitrust and securities law are shaped the way they are.
Primary sources where they exist. A shareholder letter written in the year of the decision is worth more than a biography written twenty years after it.
What to notice. Goodwill, float and owner earnings, explained by the person using them.
Free, decades deep and better written than most books about him. Start with 1983 on goodwill and 2000 on the internet, then read backwards.
Quoting a letter by its year, and saying what you disagreed with, is the single cheapest way to sound like you read primary sources.
What to notice. A signal that works is small, short-lived and expensive to find.
How Renaissance built a systematic fund and what it cost the people who built it. The best account of quant investing available to someone who is not a quant.
It gives you a realistic picture of what a research pipeline looks like, which is what a quant interviewer is testing when they ask about overfitting.
What to notice. Weight an opinion by the record of the person holding it.
One firm’s operating system, set out at considerable length. Take the sections on decision making and believability weighting; be sceptical of the rest.
What to notice. A career change is a transferable skill looking for a new market.
Seven rules, plainly told, by someone who has built three unrelated careers. Short, and considerably better than the cover suggests.
The self-improvement shelf, and the one to be most selective on. Take a method from two of them and stop; reading about productivity is the most convincing way there is to avoid being productive.
What to notice. Preparation compounds in uninterrupted blocks and not otherwise.
The case for long uninterrupted blocks, and a method for protecting them. Directly relevant when you are preparing for interviews around a full degree.
It is the difference between four hours of technicals a week and four hours of looking at technicals a week.
What to notice. Attach a new habit to one that already happens.
Systems over goals. The practical value is the habit stacking chapter, applied to a daily hour on technicals rather than a weekend of panic before a Superday.
Nothing directly. It is here because the candidates who do an hour a day beat the ones who do a weekend, reliably.
What to notice. Depth on four firms beats applications to forty.
Effort and results are not linearly related. Applied to recruiting it argues for depth on four firms over applications to forty, which is the right answer.
What to notice. Networking works when you are useful before you are needy.
Networking as generosity rather than extraction, which is also the only version that works on an analyst who owes you nothing.
Coffee chats convert when you arrive with something the other person wants, which is the entire argument of the book.
What to notice. A motivation is only credible when it explains a choice you made.
A framework for articulating motivation. "Why this firm" is where most candidates are weakest, and this is a usable structure for fixing it.
Why this firm and why this seat are the two questions most answers waste, and the structure here fixes both.
What to notice. Being good at several things beats being best at one.
The talent stack: being good at several things beats being best at one. A useful frame if you are coming from a non-target university or a different discipline.
It is the honest way to answer why a physicist or a historian should get the seat, and it beats apologising for the degree.
What to notice. Routines are personal, so take three and discard the rest.
A reference book of routines and tactics drawn from several hundred interviews. Skim it, take three things, ignore the other four hundred pages.
What to notice. Owning equity and selling time are different games.
An argument against slow accumulation and for owning equity in something. Strident, and worth reading against the grain of everything else on this shelf.
What to notice. Most plans fail on volume rather than on quality.
Effort treated as the only variable that matters. Take the argument about volume and leave the rest of it where you found it.
What to notice. The whole genre traces back to one 1937 book.
The 1937 book that founded the entire genre. Read it as a historical artefact, which is the only way it holds up.
Two skills that decide more careers than modelling does: seeing what a disclosure is hiding, and seeing what an organisation is actually rewarding.
What to notice. The warning was usually in a footnote, years early.
Corporate failures traced back to the disclosure that flagged them years in advance. A forensic accounting course disguised as a collection of case studies.
Asked what you read in a set of accounts first, naming a specific footnote and what it would tell you is a complete answer.
What to notice. Every forecast row is a sentence about the business.
Where a story becomes a forecast and a forecast becomes a valuation. The bridge between a stock pitch and the DCF sitting underneath it.
Asked to defend a growth assumption, this is where you learn to answer with a business reason rather than a percentage.
What to notice. Invert the question, and look at the incentives first.
Mental models and inversion, collected from talks. The sections on incentives and on several forces compounding at once are the ones to annotate.
Asked how you would approach a problem you know nothing about, inversion is a real method rather than a slogan.
What to notice. Organisations reward what they measure, whatever they say.
Organisational politics described without moralising about it. Read it to recognise the behaviour on a floor, not to practise it in your first year.
What to notice. Breadth beats early specialisation in unpredictable fields.
The evidence for breadth against early specialisation. Reassuring and well sourced if you are arriving in finance from another subject entirely.
It is the evidence behind the answer to why a non-finance degree is an asset rather than a gap to explain away.
A recruiting cycle is eighteen months of outcomes you do not control, punctuated by rejections that are not about you. This shelf is for that.
What to notice. Do the work well and hold the result loosely.
Acting well without attachment to the result. It is hard to think of a better framing for a process where the work is yours and the decision is not.
What to notice. Rejection is information about a process, not about you.
One page a day for a year. Built for exactly the kind of sustained, impersonal rejection an application cycle involves.
What to notice. You are not the commentary running in your head.
Lectures on not identifying with your own thinking. A counterweight to a year spent optimising every hour of your life.
What to notice. Expectation, not circumstance, is the variable you control.
An engineer’s model of happiness, written after a bereavement. Off topic for markets and firmly on topic for a hard year.
The shelf for anyone interviewing into product. All four are arguing the same thing from different directions: the expensive mistake is not building it badly, it is building the wrong thing well.
What to notice. An empowered team is given a problem, not a feature list.
The book product managers are assumed to have read. It is most useful for the distinction between a team that is handed a roadmap and one that is handed an outcome, which is the difference most candidates cannot articulate.
Asked how you would run discovery, the answer that names risks in order, value then usability then feasibility then viability, comes straight from here.
What to notice. Ask about what people already did, never about what they would do.
A short, practical book on customer conversations that do not produce flattering nonsense. The rule it is named for is the most portable idea in this collection.
Any product case that starts with talk to users is really testing whether you know how to ask a question that cannot be answered politely.
What to notice. Discovery is a weekly habit, not a phase before the build.
The operational version of the argument: what a product trio does every week, and how an opportunity solution tree keeps a team from jumping to the first idea.
The opportunity solution tree gives you a structure for a product case, and structure is what those cases are scored on.
What to notice. Shipping is an output. Nobody is paying for outputs.
Why organisations measure how much they ship instead of what changed, and what has to be true structurally for that to stop. The most useful of the four if you are interviewing into a large company.
Asked how you would measure success, the output against outcome distinction is the whole answer and most candidates give the output.
Useful whether or not you write code. A product manager who understands why a change is expensive argues better, and an engineer who can name what makes a team fast interviews better.
What to notice. Good software is chosen between demos, not specified in advance.
How software was actually made inside Apple, demo by demo. A rare engineer’s-eye account, and good preparation for a product interview.
It gives you a concrete answer to how you would decide between two designs when neither can be proven better on paper.
What to notice. Most engineering judgement is about what will be expensive to change later.
The closest thing the profession has to a shared book of craft. Read it for the habits and the vocabulary rather than the specific technologies, which have moved on.
It supplies the language for the part of a system design interview that is not about scale: coupling, reversibility and what you would leave flexible.
What to notice. Complexity is what you must hold in your head to make a safe change.
A short argument about deep modules and shallow interfaces that disagrees, usefully, with a lot of received advice about small functions. Worth reading for the disagreement alone.
Having a defensible opinion about interface design, and knowing which orthodoxy you are arguing against, stands out in a design round.
What to notice. Speed and stability rise together. The trade-off is the myth.
The research behind deployment frequency, lead time, change failure rate and recovery time. It is the only book here with a defensible empirical claim about what makes teams fast.
Asked how you would tell whether an engineering organisation is healthy, four measured numbers beat an impression.
Why some businesses get harder to catch as they grow and most do not. This is the shelf that connects a product seat to the valuation question, and it is where technology and finance interviews meet.
What to notice. Competition and profit rarely occupy the same market.
A short, contrarian argument for monopoly as the only durably profitable position. Read it as a thesis to argue with rather than accept, which is also how it is most useful in a room.
Venture interviews want to hear what would stop this being competed away. The answer lives in this argument, agreed with or not.
What to notice. A platform sets rules for a transaction it does not perform.
The mechanics of two-sided markets: who subsidises whom, why one side is priced at zero, and what actually creates a network effect as opposed to merely a large user count.
It is the difference between saying a company has network effects and being able to say which side of the market they run on.
What to notice. Network effects start in one small market, never across the whole one.
The honest sequel to the theory: how a network is actually started, city by city or campus by campus, and what usually kills it before it tips.
Asked how you would launch a marketplace, the atomic network answer is far stronger than a marketing plan.
What to notice. Habit is built from a trigger, an action, a variable reward and an investment.
A model of habit-forming product design, and a fair question about where persuasion becomes manipulation. Useful and worth being uneasy about, which is the right way to read it.
Three layers of the same story: the machines, the models, and what they do once they are pointed at people. The last two entries are the ethics reading, and they are here rather than on a shelf of their own because the consequences are not a separate subject from the technology.
What to notice. One company in the Netherlands is a single point of failure for everything.
How semiconductors became the chokepoint of the world economy. The most useful single book for anyone covering technology, and increasingly for anyone covering anything.
Export controls and supply concentration now appear in technology, macro and credit interviews alike, and this is the one book that covers all three.
What to notice. Deep learning won a decades-long argument, then was bought in a weekend.
The history of how neural networks went from an academic backwater to the centre of the industry, told through the people. The best available context for why the field looks the way it does.
Knowing why the field ignored this approach for thirty years is a better answer to why now than anything about compute alone.
What to notice. Containment is the problem, and it has no precedent that worked.
Artificial intelligence and synthetic biology framed as a containment problem rather than a product one. The most frequently cited book in technology interviews this cycle.
It is the reference everyone reaches for, so having a specific disagreement with it is worth more than having read it.
What to notice. A system optimises the objective you wrote, not the one you meant.
The clearest non-technical account of why specifying what we want is the hard part. It is a research history as much as an ethics book, which is what makes it credible.
Asked what could go wrong with a model you have proposed, reward misspecification is a concrete failure mode rather than a worry.
What to notice. A model trained on a biased outcome will reproduce it at scale.
What happens when opaque scoring systems are pointed at sentencing, hiring and credit. Written by a quant who left finance for exactly this reason, which is why it lands harder than most of the genre.
Any model that touches people invites a fairness question, and naming proxy variables is a specific answer where most are vague.
Four company stories. The pattern is the same each time: an incentive was set, nobody changed it, and the culture bent around it until something broke.
What to notice. There is often no good option, only the least bad one taken quickly.
Running a company when every available option is bad. Useful for venture and growth interviews, where the question is about operators rather than multiples.
Asked what you look for in a founder, the answer about decision speed under bad information comes from here.
What to notice. Secrecy presented as protecting the technology is the warning sign.
The Theranos investigation by the reporter who broke it. The documentary is the faster version; this is the one that shows how the evidence was actually assembled.
It is the best answer to what you would verify independently, because it lists exactly what nobody verified.
What to notice. Growth at any cost is a culture, and it is priced in later.
How a company scaled faster than almost any before it and what that did internally. The governance story matters more than the personalities, and the book is good on both.
Asked about founder control and board structure, this is where dual-class shares stop being a footnote in a prospectus.
What to notice. Deleting the requirement comes before optimising the part.
A long, close-range biography. Useful in technology interviews as a case study in risk tolerance and in what that tolerance does to an organisation.
Reading is the cheap part. These are the places on the site where you have to produce something and find out whether it stuck.