A Navy SEAL’s Revenge List, One Bloody Line at a Time

A SEAL comes home to nothing

James Reece is a Navy SEAL commander who leads his platoon into an ambush in Afghanistan that reads less like bad luck and more like a setup. He comes home. His team didn’t. Then, in the space of about a hundred pages, his wife and daughter are murdered too, and it becomes very clear that somebody with a lot of institutional power wanted Reece and everyone connected to him gone. So he does the only thing a man like Reece can do with that kind of grief: he makes a list, and he starts working through it.

That’s the whole engine of the book, honestly. It’s a revenge plot with a military intelligence conspiracy bolted onto it, weaving in pharmaceutical companies, defense contractors, and a government willing to look the other way when it’s convenient. I want to be upfront that I don’t think the conspiracy is the point. The conspiracy is scaffolding. The point is watching a supremely competent, deeply broken man take names, and Carr knows exactly what his readers showed up for, so he does not waste your time getting there.

What actually works, and what made me put it down twice

Here’s the thing about Jack Carr: the man was a Navy SEAL for almost two decades, and it shows in every single tactical sequence in this book. When Reece is planning an op, checking sightlines, choosing a rifle, moving through a house, you believe every word of it, because the guy writing it has actually done versions of this for real. That authenticity is the book’s entire spine. There’s a sequence involving a modified rifle and a shot that has to account for wind, distance, and a moving vehicle that I read twice just because the mechanics of it were so specific and so clearly written by someone who’s held that rifle. That’s not a small thing. A lot of thriller writers fake competence. Carr doesn’t have to.

But look, I have to be honest about the rest of it, because pretending otherwise would be a disservice. The prose outside the tactical sequences is often flat, sometimes clunky, and Carr has a habit of explaining things the reader already understood two sentences earlier. Characters state their motivations out loud in ways real people don’t. The female characters, in particular, exist mostly to be loved, then killed, then avenged, and I found myself wishing at least one of them got to be a person before she became a plot device. There’s also a chunk in the middle, once the conspiracy machinery kicks into gear with boardrooms and bureaucrats, where the pacing sags hard. I put the book down twice during that stretch, once to make dinner and just never picked it back up that night, which for a thriller is a real tell.

And I’ll admit something that might get me some pushback: I went in expecting to hate the politics of this book, because I’d heard the noise about it online before I ever opened it, and some of that noise is fair. There is a very particular worldview running under this story, suspicious of institutions, sympathetic to a certain kind of grievance, and if that’s not your thing it will grate on you in places. I noticed it. It didn’t ruin the book for me, but I’m genuinely unsure if that’s because the tactical writing is good enough to distract me, or because I was reading it in a waiting room where I badly wanted to root for somebody who wins.

Is it overrated? For what it’s trying to be, no. As a piece of literature, sure, easily. This is not going to be taught anywhere. But as a machine built to make you turn pages while a man with nothing left to lose takes his revenge one name at a time, it mostly works, even when it’s clunky doing it.

Grief with a mission attached to it stops looking like grief and starts looking like purpose, and that’s the most dangerous thing a man can be handed.

About Jack Carr

Jack Carr spent nearly two decades as a Navy SEAL, working his way up from platoon commander to leading a Special Operations Task Unit, and he retired as a Commander. He wrote “The Terminal List” essentially as his first novel after leaving the service, which explains why the tactical detail feels less like research and more like muscle memory. He’s since built out the James Reece series into a full franchise, consulted on the Prime Video adaptation, and become something of a spokesperson for a certain flavor of hard-edged military fiction, doing podcasts, hunting trips, and gun content alongside the books. He writes exactly like a man who has spent more time cleaning rifles than reading Faulkner, and once you accept that’s the deal, the books make a lot more sense.

If this hit that trigger-pulling itch, read these next

• “American Sniper” by Chris Kyle, for the real-life version of the mindset Reece is built from, unfiltered and nonfiction.
• “The Bourne Identity” by Robert Ludlum, for an older, twistier take on a lethal man being hunted by the people who made him.
• “Reacher” novels by Lee Child, if you want the same appetite for competence and violence with better sentence-level control.
• “True Believer” by Jack Carr, the direct sequel, if you want to know whether Reece ever gets to put the list down.

For your book club

1. Does Reece ever feel like a full person to you, or is he mostly a vehicle for the plot’s violence?
2. How much did the book’s politics affect your enjoyment of it, and do you think that’s a fair thing to hold against a thriller?
3. Carr writes tactical scenes with obvious real experience. Did that authenticity change how you read the parts of the book that felt less grounded?
4. The women in Reece’s life exist mostly to be lost. Does the book earn the emotional weight it asks you to feel about that loss?
5. Would this story work as well if the villain were a lone actor instead of an institutional conspiracy?