West with
the Night

Beryl Markham was a bush pilot in 1930s East Africa. She flew mail and passengers across terrain that had no landing strips, no reliable charts, and no margin for error. In 1936 she flew solo from England to Nova Scotia — east to west across the Atlantic, against the prevailing winds, through the night. She was the first person to do it in that direction.

Her memoir of those years, West with the Night, is one of the most honest accounts of professional life ever written — not because it is dramatic, but because it refuses to be. The extraordinary is described in the same flat register as the ordinary. The danger is noted without theatrics. The loneliness is acknowledged without self-pity. She packed a comb for the Atlantic crossing. That detail appears without comment.

Ernest Hemingway, who did not distribute praise carelessly, read it and wrote to a friend: "She can write rings around all of us who consider ourselves writers." What he recognized, I think, was the discipline of her honesty. She did not reach for significance. She reported what she saw from where she was sitting. The significance was already there.

A career, at its best, works the same way.

The Plural of Flight

There is a version of professional life that looks, from the outside, like a series of positions held and titles accumulated. A resume of this kind is a timeline — dates and organizations and roles, arranged in reverse chronological order, suggesting a progression that may or may not reflect what actually happened.

There is another version that is harder to document. The version where the work itself was the point. Where the engagement that lasted six months contained more concentrated professional challenge than most people encounter in six years. Where the client was a central bank in a country still finding its post-Soviet footing, and the problem was building financial infrastructure for a market that had not existed two years earlier. Where the counterpart across the table was a derivatives trader at a major exchange in a city you had never visited before, and you had forty-eight hours to understand their system well enough to connect it to yours.

This version does not fit neatly into a resume. The bullet point that results — "led implementation of trading system integration" — is not false. It is simply not the thing. It is the shape of the thing, flattened into two dimensions, stripped of terrain and weather and the specific quality of the problem at three in the afternoon when the deadline was moving and the solution was not yet visible.

What Gets Lost

Consider what a six-month engagement at a financial institution actually contains. The initial assessment — understanding not just the technical architecture but the political one, who owns which system and who resents that they do not. The negotiation of requirements that are not yet requirements, only anxieties that have not found their form. The moment when the thing you built first fails in a way that reveals something true about the problem you were actually solving, which was not the problem you were hired to solve.

Consider what it means to stand in a trading room in a capital city where your native language is not spoken, where the regulatory framework was written last year and may be rewritten next month, where the people you are working with are brilliant and exhausted and have been building the future of their country's financial system on a timeline that would be considered aggressive in a stable environment.

Consider the sanctions compliance filter built into a messaging system that processes international transactions — the architecture decisions made at two in the morning, the test cases that had to account for scenarios the specification writers had not imagined, the launch that had to be clean because the consequences of failure were measured not in lost revenue but in regulatory action.

None of this is on the resume. The resume says "implemented sanctions compliance module." It is not wrong. It is simply not the thing.

The Company That Worked

In the middle of a consulting career that crossed many time zones and more institutional cultures than I can easily count, there was one organization that was different. Not louder about its values — quieter, actually. Not more documented — less so. The difference was something more fundamental: the standards were real, and the people who held them were accountable to the same standards they enforced.

It was the kind of place where a problem surfaced on Monday was understood by Tuesday and addressed by Wednesday — not because the process required it, but because everyone in the building understood that slow resolution of real problems was a form of organizational dishonesty. Where the work was taken seriously because the people doing it were taken seriously. Where disagreement was possible without consequence, which meant that the agreements that emerged from disagreement were actually agreements.

I went full-time. I stayed. I began, eventually, to take it for granted — the way you take for granted the air quality until you leave the mountains.

Then the acquisition came.

It is one of the most reliable patterns in corporate life, and one of the least discussed. A large institution acquires a smaller one specifically because the smaller one has produced something the large one cannot — a product, a technology, a way of working that generates results the acquirer's own methods have failed to generate. The acquisition price reflects this. The integration plan does not.

Within eighteen months, the people who built the thing had left. Not fired — simply gone, one by one, in the quiet way that people leave when the environment that made their work possible no longer exists. The processes that replaced theirs were more legible to the parent organization, more auditable, more formally correct. They were also slower, more political, and less effective. The thing that had been acquired — the actual thing, not the assets or the headcount or the intellectual property — had been dismantled with great organizational efficiency.

This is not a story about bad intentions. The people who made those decisions were not malicious. They were applying the tools they had to a problem those tools were not designed to solve. An integrity-tight, human-affirming culture is not an asset that transfers on a balance sheet. It is a practice. It requires practitioners. When the practitioners leave, the practice ends.

Evidence and Its Limits

A resume is a document of evidence. Done honestly, it captures what you did — not what you felt about it, not what it cost you, not what it taught you that cannot be named in a bullet point. Evidence, in this sense, is both the resume's strength and its limitation. It can prove that you were there. It cannot prove what it was like.

This is not a flaw to be corrected. It is a condition to be understood.

The cover letter exists, in part, to carry what the resume cannot. The narrative that explains why a six-month engagement at a central bank in a country mid-transformation is more relevant to this role than three years at a stable institution doing well-defined work. The context that makes the bullet point legible — not inflated, not embellished, but placed in the terrain that gives it its actual shape.

The danger, in the current environment, is the temptation to use AI to fill the gap between what you did and what you wish you had done. To generate the bullet points that sound right, the metrics that round up to significance, the skills that appear in the job description and therefore appear in the resume. This is not evidence. It is the shape of evidence, without the substance — and it fails in exactly the moment that matters most: the interview, where the hiring manager asks you to describe what you actually did, and the answer has to come from memory, not from a language model.

The work you did is sufficient. The flights you flew are real. The instruments you used, the terrain you crossed, the problems you solved at three in the afternoon when the deadline was moving — these are worth documenting honestly. They do not need to be embellished. They need to be described.

The Return to the Quote

Beryl Markham flew west against the wind because that was the direction that had not been done. The technical challenge was considerable. The meteorological odds were not favorable. She packed a comb.

She did not hope her way across the Atlantic. She worked her way across it — with instruments she understood, in an aircraft she trusted, toward a destination she had calculated. The hope was present, but it was subordinate to the work. It always has to be.

A career built on evidence is built the same way. Not on the hope that the hiring manager will not ask too many questions. Not on the optimism that an invented metric will survive contact with a reference check. On the work itself — documented honestly, described specifically, offered without inflation to people who are capable of recognizing it for what it is.

The people worth working for always are.

That is what an evidence-based resume is. Work, documented. Not hope, dressed up as experience. The flights you actually flew, described from the cockpit, in the honest flat register of someone who was there and knows what it was like and does not need to reach for significance.

The significance is already there. It always was.