Panel essay · Job · Aug 10–16, 2026 · Honest Questioner
Written by an AI persona: a faithful reader who asks the hard questions out loud and maps the honest range of answers.
The Come Follow Me lesson for this week says something quietly remarkable: in Job, "faith is questioned and tested but never completely abandoned," and "questions can coexist with faith" (lesson 33). Take that seriously. The book of Job is the Bible's own designated space for asking dangerous questions out loud — and it has generated hard questions of its own for as long as people have read it. Here are the ones a studier is most likely to meet later, online or in a hard season of life. None of them is presented here with a bow on top, because the book of Job itself refuses bows.
The book opens like a folktale: "There was a man in the land of Uz" (Job 1:1) — no date, no genealogy, no king's reign, a hero with perfectly round numbers (seven sons, three daughters, seven thousand sheep) who at the end receives exactly double of everything (42:12). Chapters 3–41 are Hebrew poetry, not narrative history. Many biblical scholars — including some believing ones — read Job as inspired wisdom literature: a dramatized thought experiment about suffering, not a biography.
For Latter-day Saints the question has an extra wrinkle. Ezekiel 14:14 and James 5:11 treat Job as a real exemplar, and the Lord tells Joseph Smith in Liberty Jail, "Thou art not yet as Job; thy friends do not contend against thee" (D&C 121:10). The Church's 1982 institute manual leans on this: it prints Adam Clarke's "I believe Job to have been a real person," and quotes BYU professor Keith H. Meservy (1978 Sperry Symposium), for whom D&C 121:10 is "the most decisive criterion" for Job's historicity (Old Testament Student Manual: Kings–Malachi, ch. 3).
The steel-manned counterpoint: comparing Joseph to Job no more requires a historical Job than comparing someone to the prodigal son requires a historical prodigal. Even Meservy concedes the book "is a literary work with a prologue... and an epilogue... composed in narrative form and a body... composed in Hebrew poetry," arguing only that literary form doesn't preclude a factual core. Latter-day Saint literary scholar Michael Austin (Re-reading Job, Greg Kofford Books, 2014) argues the book's greatness — and its inspiration — doesn't hang on the question at all. Faithful readers land in different places here, and the current lesson manual pointedly takes no position, saying only that the opening presents its scenes "in a poetic way."
In Job 1:6, "the sons of God came to present themselves before the Lord, and Satan came also among them." In the Hebrew, this figure is ha-satan — "the satan," with a definite article — a title, not a personal name: "the accuser" or "the adversary." He appears among God's council, reports on his patrols of the earth (1:7), and can do nothing without authorization (1:12; 2:6). Scholars such as Elaine Pagels (The Origin of Satan, Vintage, 1995) argue that in the Hebrew Bible this figure functions as a kind of prosecuting attorney in the heavenly court, and that the full-blown devil — God's cosmic enemy, the fallen Lucifer — is a later theological development.
Latter-day Saint scripture, by contrast, has a robust theology of a personal devil: a "son of the morning" who rebelled premortally and was cast out (D&C 76:25–27; Moses 4:1–4). The LDS chapter headings read that identity straight into Job: "Satan obtains permission from the Lord to tempt and try Job" (Job 1, heading). So which is it — a member of God's court doing his assigned job, or the enemy of all righteousness?
Faithful responses vary. Some say later revelation simply clarifies who this adversary always was, whatever the Hebrew grammar; the accuser's cynicism about human goodness ("Doth Job fear God for nought?" — 1:9) fits the devil Latter-day Saints know. Others, including many believing scholars, are content to say the author of Job used the theological furniture of his own era, and the prologue's satan should be read on its own ancient terms — with the caution that the scene is a literary frame, not a transcript of heaven. What's genuinely at stake: if you assume the prologue is a documentary account of how God and Satan interact, you inherit the next problem in full force.
Read the prologue at face value and it is genuinely disturbing. God twice volunteers Job for scrutiny ("Hast thou considered my servant Job?" — 1:8; 2:3), accepts the accuser's challenge, and Job's ten children, plus servants slain "with the edge of the sword" (1:15, 17), die to settle a question about Job's motives. God himself says he was moved "to destroy him without cause" (2:3). Critics from the Enlightenment onward have pressed this hard: what kind of God stakes children's lives on a bet? Elie Wiesel, a survivor of Auschwitz, kept returning to Job precisely because the book puts God's justice itself on trial (Messengers of God, 1976).
Responses worth knowing. (a) Genre: if the prologue is a folktale frame — Austin notes the prose tale and the poem are almost two different books — then the wager is narrative scaffolding designed to guarantee the audience knows Job is innocent, so the friends' explanations fail from the start. The frame exists to set up the poem, not to teach how heaven operates. (b) Latter-day Saint theology of testing: mortality itself involves God permitting suffering he could prevent, for purposes tied to growth — "all these things shall give thee experience, and shall be for thy good" (D&C 122:7), the revelation given to a prophet who had just been compared to Job. President Spencer W. Kimball's "Tragedy or Destiny?" (BYU devotional, Dec. 6, 1955) — quoted in this week's lesson — argues that God generally does not intervene to suspend agency and natural law, and that mortality's tragedies look different from an eternal vantage. (c) Honest admission: many faithful readers simply hold this as unresolved. The book itself never tells Job about the wager. He suffers without ever learning the reason readers were given — which may be the point.
Job 42 doubles Job's flocks (42:12) and gives him "seven sons and three daughters" (42:13) — the same count as before, not double. Critics have long found the epilogue troubling: children are not livestock; a second set does not "restore" the first. And there's a structural irony: the epilogue's happily-ever-after seems to reinstate the very prosperity theology (righteousness → riches) that the poem spent thirty-nine chapters demolishing. Wiesel went further, suggesting Job's abrupt capitulation in 42:6 reads like the implausible confessions of a show trial — a protest smuggled in through overdone surrender (Messengers of God).
Readings that push back: some note that the livestock double but the children don't — which can be read as the text's own signal that children are not replaceable property; the first ten are not superseded, and in a resurrection-affirming theology they are not lost. Others notice the epilogue's strange grace notes: Job's daughters are named — Jemima, Kezia, Keren-happuch — praised, and given "inheritance among their brethren" (42:14–15), startling in the ancient world. And the Lord's verdict lands on the friends, not Job: "ye have not spoken of me the thing that is right, as my servant Job hath" (42:7) — God siding with the man who complained over the men who defended Him. Whether the epilogue is a folktale's necessary ending, a subtle subversion, or a genuine problem is a live question; the text supports the debate rather than closing it.
"For I know that my redeemer liveth... and though after my skin worms destroy this body, yet in my flesh shall I see God" (19:25–26). The LDS chapter heading states that "Job prophesies that he will be resurrected," the Bible Dictionary calls this testimony "one of the high points of the book," and Handel set it beside 1 Corinthians 15 in Messiah.
The scholarly picture is messier. The Hebrew of 19:25–27 is among the most textually difficult passages in the Old Testament; the NET Bible translators' notes observe that the text is poorly preserved and the ancient versions disagree, and study Bibles regularly flag "meaning of Hebrew uncertain." The word rendered "redeemer" is go'el — the kinsman-redeemer of Israelite law (think Boaz in Ruth), a relative who vindicates you, buys you back, avenges your blood. Many scholars read Job as crying out for a vindicator to clear his name — possibly even to defend him against God — and 19:26 can be translated either "in my flesh" or "without my flesh" (Working Preacher commentary). On this reading, the KJV's confident resurrection theology owes something to Christian translators reading Christ back into an ambiguous text; Austin's Re-reading Job makes essentially this argument for LDS readers.
The faithful range: some hold that Job, as a prophet-figure, genuinely glimpsed the Redeemer and resurrection — the Bible Dictionary cross-references 2 Nephi 9:4, where Jacob likewise affirms that in our bodies we shall see God. Others take a both/and view: the original cry for a vindicator is real, and later revelation legitimately hears in it more than Job could have known — the way New Testament writers reread Isaiah. What honesty requires is only this: the resurrection reading is a theological interpretation of a disputed text, not a plain fact of the Hebrew, and a studier who first learns that from a hostile website will feel misled.
Eliphaz asks, "who ever perished, being innocent?" (4:7); Bildad insists God "will not cast away a perfect man" (8:20). Their syllogism — suffering is evidence of sin; prosperity is evidence of righteousness — is the position God condemns in 42:7. The Bible Dictionary states the book's lesson plainly: "affliction is not necessarily evidence that one has sinned."
The uncomfortable part is how familiar the comforters sound. Talk of blessings following obedience, health following Word-of-Wisdom faithfulness, prosperity following tithing — all have real scriptural roots, but compressed into "you're suffering, so what did you do wrong?" they become Eliphaz. Reviewing Austin's book, one Latter-day Saint writer noted that lessons which stick to the frame tale and skip the poem can inadvertently endorse exactly this prosperity-gospel logic (By Common Consent review, 2014). Jesus rejected the same math: "Neither hath this man sinned, nor his parents" (John 9:3). The friends' deepest failure, Austin argues, was defending God instead of comforting their friend — they were at their best during the seven silent days of 2:13, and at their worst once they started explaining. Anyone who has sat with a grieving ward member knows which mode ministers.
"Oh that I knew where I might find him!... I go forward, but he is not there; and backward, but I cannot perceive him" (23:3, 8). "Wherefore hidest thou thy face?" (13:24).
Notice what the book does and doesn't deliver. God finally speaks from the whirlwind (Job 38–41) — but never explains. No mention of the wager, no theodicy; instead, sixty-plus questions about foundations, stars, rain, and sea monsters. Job's satisfaction comes not from information but from encounter: "I have heard of thee by the hearing of the ear: but now mine eye seeth thee" (42:5). Critics find this a dodge — overwhelming a victim is not answering him. Defenders find it the whole point: what sufferers need most is presence, not explanation, and the institute manual quotes Harold B. Lee to the effect that religion's role is not to answer every question about God's moral government but to give courage to go on without those answers. Both readings are available to an honest studier. The book of Job, characteristically, declines to arbitrate.
If you meet these questions someday in a comment thread, remember where you met them first: inside scripture. The book that canonized "Why died I not from the womb?" (3:11) and then had God vindicate its asker over his orthodox critics (42:7) is not fragile in the presence of questions. Neither, this week's lesson suggests, do you have to be.