Nobody knows who wrote the Book of Job. The text names no author, and the earliest Jewish and Christian traditions that address the question disagree with one another. Scholarly estimates for its composition range from roughly the seventh to the fourth century BCE, which means the question of authorship may span several writers and editors rather than one.
The book itself is a 42-chapter Hebrew poem framed by a prose prologue and epilogue. Its scale and density make it one of the longest wisdom texts in the biblical canon. That scale matters for authorship: texts this long and this linguistically unusual rarely come from a single hand in a single sitting. Understanding who wrote Job requires understanding how biblical books were made.
The silence of the text itself
The Book of Job never identifies its author. Unlike prophetic books that open with a call formula ("the word of the LORD came to..."), Job opens in medias res with a scene in heaven. The human protagonist is introduced by location and wealth, not genealogy. This is deliberate literary architecture, and it removes the single most common authorship clue ancient texts provide.
The book also describes Job as a man from Uz, a region outside Israel. He offers sacrifices without a temple, a priest, or a mediating institution. Some scholars read this as evidence the story predates Israelite temple religion; others read it as a deliberate literary choice placing the story in a universal, non-national setting. The text gives no verdict.
One structural detail deserves attention. Job 19:23-24 contains the line "Oh that my words were written! Oh that they were inscribed in a book!" The narrator quotes Job wishing his speech were permanently recorded. This is a literary device, not a claim about the book's own composition, but it shows the author was thinking self-consciously about writing.
How biblical books were composed
Most Hebrew Bible books grew through a layered process. Oral traditions circulated first. Scribal editors collected, arranged, and revised them. Later hands added interpretive glosses. The final text is a snapshot of that process, not a single author's manuscript.
Job shows textbook signs of this layering. The prose frame (chapters 1-2 and 42:7-17) is written in relatively simple classical Hebrew narrative. The poetic core (chapters 3-41) uses a dense vocabulary with dozens of words appearing nowhere else in the Hebrew Bible. Vocabulary divergence this large between frame and poem points to different compositional stages.
The Elihu speeches (chapters 32-37) are a specific flashpoint. Elihu appears nowhere in the prologue, is never answered, and is absent from the epilogue. These four chapters introduce a fourth friend after the three friends have been silenced. A significant minority of scholars treats this block as a later insertion. Professional caveat: minority opinion, and the text itself contains no seam marker confirming it.
One counterintuitive detail: the epilogue has God declaring the three friends correct and Job correct, while Elihu goes unmentioned entirely. If Elihu were original to the book, his complete absence from the verdict is hard to explain.
Dates, languages, and the authorship candidates
Estimating a composition date for Job is an exercise in indirect inference. The Hebrew contains Aramaisms (Aramaic loanwords and grammatical forms) that cluster in later biblical texts. It also contains vocabulary paralleling Ugaritic texts from the 14th-13th centuries BCE. These two signals pull in opposite directions, and the standard resolution is that a very old tradition received a late linguistic layer.
| Candidate position | Core argument | Main weakness |
|---|---|---|
| Moses (traditional Jewish attribution) | Antiquity of the story and its non-Israelite setting | No textual or historical evidence; assumes Mosaic authorship of the whole Torah |
| Solomon (some rabbinic opinion) | Job grouped among wisdom books attributed to Solomon's era | Attribution rests on genre, not evidence |
| An anonymous Israelite sage, 7th-4th c. BCE | Aramaisms and wisdom-genre parallels | Cannot identify an individual |
| Multiple redactors over centuries | Vocabulary layers, Elihu block, frame/poem split | No explicit seam markers |
| A non-Israelite author | Edomite/Uz setting, absence of covenant language | Hebrew composition language is Israelite |
| Modern literary reading: single brilliant author | Unity of theodicy argument across the book | Does not explain the linguistic layering |
The Talmud (Bava Batra 14b) records an opinion attributing Job to Moses. That tradition is ancient, but it is a tradition, not evidence. No manuscript, colophon, or external source names an author.
Translation and transmission: what "wrote" can mean
The question "who wrote the book" collapses three different things. Composition means creating the text. Redaction means editing and arranging it. Transmission means copying it forward. For Job, the answer differs at each layer.
The Hebrew text of Job is among the hardest in the Bible to translate. The Greek Septuagint version of Job is roughly one-sixth shorter than the Hebrew Masoretic text. That gap means the Greek translators worked from a shorter or different Hebrew parent text, or deliberately abbreviated. Either way, the book existed in multiple textual forms before standardization.
The Dead Sea Scrolls include Job fragments among the Qumran library, which confirms the book's circulation in multiple copies by the late Second Temple period. Copying was manual work, and scribal hands introduced and preserved variants. The Masoretes standardized vowel pointing centuries later. None of these copyists "wrote" Job, but they produced the text we read.
Plain-language version: the book has an originator, an unknown number of editors, and a long chain of copyists. Only the first category answers the authorship question, and the text hides it.
Misconceptions worth correcting
The most common error is treating "Moses wrote Job" as settled fact. It is one ancient opinion among several, recorded alongside competing opinions in the same passage. Tradition is not the same as attribution evidence.
A second error assumes the book is a transcript of real speeches. Job's dialogues follow a rigid poetic structure: three cycles of speeches, then a fourth voice. Real conversations do not do that. The symmetry is authorial construction, and recognizing it tells you the author was a skilled literary craftsman, whatever the date.
A third error treats the book as a treatise answering the problem of suffering. The book famously refuses that answer. God's speech from the whirlwind (chapters 38-41) responds to Job with questions about creation rather than explanations of suffering. The author's argumentative strategy is to challenge the premise that suffering maps to guilt, not to supply a formula.
Watch for these red flags when reading authorship claims: Any source naming a specific author as established fact without citing a text or manuscript Dated estimates presented with false precision ("written in 950 BCE") when the range is centuries wide Claims that Elihu's speeches are certainly original or certainly interpolated Arguments from the book's beauty to a specific named author Conflating "the text says Job was a real person" with "we know who wrote the text" Citing modern devotional tradition as historical evidence
Practical steps for reading and research
If you want a defensible answer rather than a repeated tradition, work the evidence in order.
First, read the prose frame and the Elihu speeches separately from the poetic core and note the register shift yourself. Second, check any authorship claim against a critical commentary that discusses the Hebrew, not just an introduction. Third, treat date ranges as ranges: a 7th-4th century BCE window is the scholarly working consensus, not a precise date. Fourth, distinguish tradition from evidence in whatever source you read; the Talmud records opinions, and so do modern introductions.
For the practical threshold: if a source gives a single author and a single year with no discussion of the language layers or the Elihu block, it has skipped the actual evidence. If it gives a range, multiple compositional stages, and acknowledges the anonymity, it is tracking the data. A useful cross-check is whether the source mentions the Septuagint's shorter text, since that fact requires engaging with transmission rather than just attribution.
The most current and defensible position: the Book of Job is anonymous, composed over a span of centuries by at least one major poet and probably several editors, with the Elihu speeches and the prose frame as the most likely later or separate layers. That is a less satisfying answer than a name, but it is the one the evidence supports.
Limits of what can be concluded
The honest boundary is this: no manuscript, no colophon, no contemporary reference, and no external source identifies the author of Job. Everything beyond the text's anonymity is inference from language, structure, and tradition. Inference can rank hypotheses; it cannot name a person. Claims of certainty in either direction, whether "Moses wrote it" or "we know it was a single exilic poet," exceed what the evidence supports.
The authorship question is therefore not a research gap waiting for a discovery. It is a structural feature of how this book entered the canon. The text was designed to stand without an author's name, and readers have been arguing about it for over two thousand years as a result.