Did God Really Command Genocide?
A lot of people carry around a picture of the Old Testament God as a monster. A God who delights in genocide, in the death of humans, in the abuse of creation. And I get why. There are stories in there that read that way on the surface, and nobody handed us the tools to read them any differently.
I want to look at one of those stories with you. Not to explain it away, not to pretend it doesn't sting, but to actually ask whether we understand this text for what it is.
Here's the story, from Exodus 17.
Amalek came and attacked Israel in Rephidim. So Moses said to Joshua, "Choose some of our men and go out, fight against Amalek. Tomorrow I will stand on top of the hill with the staff of God in my hand." So Joshua fought against Amalek just as Moses had instructed him, and Moses and Aaron and Hur went up to the top of the hill. Whenever Moses would raise his hands, then Israel prevailed, but whenever he would rest his hands, then Amalek prevailed. When the hands of Moses became heavy, they took a stone and put it under him, and Aaron and Hur held up his hands, one on one side and one on the other, and so his hands were steady until the sun went down. So Joshua destroyed Amalek and his army with the sword. The Lord said to Moses, "Write this as a memorial in the book, and rehearse it in Joshua's hearing, for I will surely wipe out the remembrance of Amalek from under heaven." Moses built an altar, and he called it "The Lord is my Banner," for he said, "For a hand was lifted up to the throne of the Lord, that the Lord will have war with Amalek from generation to generation."
(NET Bible, Exodus 17:8-16)
This is a familiar story in church circles. You've probably heard it preached as a lesson about lifting your hands in worship, about persevering in prayer, about needing people around you to hold you up when you get tired. All of that is fine as far as it goes. But there is something underneath this story that we tend to skip past, and it is the part I actually want to sit with.
Before we get to the hard part, a couple of things worth noticing
This story marks two firsts in the text. It is the first time Joshua is named, introduced here as a warrior, which tracks with who he becomes later as the leader who takes Israel into Canaan. And it is the first time the Bible talks about the Bible being written. Verse 14 has God telling Moses to write this down as a memorial. Think about that. The first instance of scripture referencing its own writing is a story being preserved specifically so it would not be forgotten.
That detail matters more than it might seem. The Pentateuch, the first five books, was not handed down in one sitting. It was formed, edited, and adapted over time, using preserved fragments and accounts from earlier generations. Older scholarship called this the documentary hypothesis, first proposed by Julius Wellhausen in the late 1800s. Most current scholarship has moved toward what is called a fragmentary hypothesis, the idea that whoever compiled Genesis through Deuteronomy was weaving together existing stories and records rather than writing the whole thing from scratch in one moment. John Sailhamer's The Pentateuch as Narrative is a helpful companion read if you want to dig into how these stories were shaped and preserved (Sailhamer, The Pentateuch as Narrative: A Biblical-Theological Commentary, Zondervan, 1992). Tim Mackie also walks through this idea in his lecture "Who Wrote the Bible?," including the observation that Exodus 17:14 is the first place in scripture where the text references its own writing.
You can see this pattern elsewhere too. The book of Zechariah has an earlier section addressing a Babylonian context, and a later section that reflects the Greek empire that came generations after. Two different eras, likely two different hands, one scroll. If that unsettles your idea of what it means for a text to be inspired, I would offer this: preserving and shaping a true account over time does not make it less inspired. It just means these are real records of real people, not dictation from the sky.
Who were the Amalekites, and why does this matter
The Amalekites only appear in the biblical record. There is no outside archaeological trace of them the way there is for groups like the Hittites. According to the text, they were a nomadic people from southern Canaan, and their king Amalek was the grandson of Esau.
That genealogy is not incidental. Esau was Jacob's brother, and their relationship was defined by rivalry from birth. When Amalek's people attack Israel with no stated provocation in verse 8, a reader familiar with Genesis is meant to hear an echo. This is not just a battle. It is the continuation of a much older family conflict.
That reframes the question we should be asking. It is tempting to read a story like this and ask, "did this literally happen exactly as written." I want to suggest a better question: why am I being told this story. Out of everything that could have been recorded, why this. Once you start asking that question, the thematic weight of Jacob and Esau's descendants clashing again becomes part of the point, not a detail to explain away.
Key Takeaways
Exodus 17 is the first place scripture references its own writing, which points to real preservation and compilation over time, not single-moment dictation.
The Amalekites are introduced as descendants of Esau, connecting this conflict back to the Jacob and Esau rivalry in Genesis.
The better question to ask of a text like this is not "did this happen literally," but "why am I being told this story."
Now to the verse that actually bothers us
Verse 14: "I will completely blot out the name of Amalek from under heaven."
That is the line that makes us flinch. Where is turn the other cheek. Where is love your enemies. Where is the Jesus we know from the New Testament in a line like that.
If you have felt that tension, you are not the first. Marcion, in the second century, felt the same thing so strongly that he concluded the Old Testament God and the New Testament God had to be two different beings entirely, one vindictive, one loving. The early church rejected that conclusion. I think they were right to. But I also think we owe it to ourselves to sit with why that reading feels so tempting.
Here is what I want you to notice. The text does not leave verse 14 sitting by itself. Verse 15 and 16 come immediately after.
Moses built an altar and called it "The Lord is my Banner." He said, "For hands were lifted up to the throne of the Lord. The Lord will be at war against the Amalekites from generation to generation."
So which is it. Is Amalek being erased so completely that no one will remember them, or is this a war that continues generation after generation. The text puts both claims two verses apart. That is not an accident we need to smooth over. It is a clue.
And when you follow the Amalekites through the rest of the Hebrew Bible, the second claim is the one that actually plays out. In 1 Samuel 15, Saul is commanded to wipe them out completely and fails to finish the job, which becomes the beginning of his downfall. A few chapters later, in 1 Samuel 27 and 30, Amalekites are back on the scene fighting David. After that, 1 Chronicles 4:43 records a remnant of Amalekites being defeated yet again. And by the time you reach the book of Esther, the villain Haman is identified as an Agagite, a direct link back to Agag, the Amalekite king from Saul's story. Some scholars read this as more typological than genealogical, but either way, the pattern holds. Amalek keeps showing up in the text long after being "utterly destroyed."
Key Takeaways
Exodus 17:14 says Amalek will be completely blotted out. Verse 16, two lines later, says Israel will be at war with Amalek for generations. The text holds both claims at once.
1 Samuel 15, 1 Samuel 27 and 30, and 1 Chronicles 4:43 all show Amalekites still present long after their supposed total destruction.
Haman's title "the Agagite" in Esther links back to the Amalekite king Agag, showing this conflict still carrying symbolic weight generations later.
So what is actually going on
Here is what I want to propose. What if total destruction language in the Old Testament is a literary genre, not a moral problem we are required to solve.
This is not a modern dodge. Ancient Near Eastern kings used this exact kind of language as a matter of convention. The clearest example is the Merneptah Stele, dated to around 1208 BC, which holds the earliest known reference to Israel outside the Bible. In it, Pharaoh Merneptah claims, "Israel is laid waste, his seed is not." Israel obviously did not cease to exist. This was war propaganda, a rhetorical convention for claiming decisive victory, not a literal casualty report.
Read Exodus 17 with that convention in mind, and the tension between verse 14 and verse 16 stops looking like a contradiction the text failed to notice. It starts looking like the text telling you, in its own structure, how this kind of language was meant to be understood.
This is not unique to Exodus 17 either. The same pattern shows up in the conquest of Jericho, where the text claims not a man, woman, child, or animal was left alive, and yet those same people groups reappear later in the narrative. Once you see this genre, you start noticing it everywhere.
So is God a monster commanding genocide. On a surface reading, it can look that way. But when you read these texts as what they actually are, ancient accounts written in a specific genre with specific conventions, there is something more going on than a God who delights in wiping people out.
Key Takeaways
Total destruction language in the ancient Near East functioned as a rhetorical convention for claiming victory, not a literal report of extermination.
Exodus 17's own internal tension between "blotted out" and "war for generations" reflects this convention rather than a contradiction in the text.
The same destruction language pattern appears in the conquest of Jericho, where the supposedly annihilated people reappear later in the narrative.
I do not think this resolves every hard question in the Old Testament. There is more here, including the Joshua conquest narratives, that deserves its own honest look. But I hope this opens a door. If a passage like this has been sitting unresolved in the back of your mind, maybe the answer was never to abandon the question. Maybe it was to ask a better one.
