Race After Technology and the New Jim Code
Ruha Benjamin's Race After Technology is one of the clearest short books for understanding why discriminatory technology is not only a problem of bad data, biased coders, or insufficient representation. It is a book about social hierarchy becoming infrastructure: older racial arrangements rewritten as apps, scores, filters, databases, defaults, and cheerful products that claim to be neutral.
The Book
Race After Technology: Abolitionist Tools for the New Jim Code was published by Polity in 2019. Benjamin's author page lists the subtitle, publisher, year, and several honors, including the 2020 Oliver Cromwell Cox Book Award, a 2020 CITAMS honorable mention, and the 2020 Brooklyn Public Library Literary Prize for Nonfiction. Academic listings in Social Forces, Nature Machine Intelligence, Cultural Sociology, and New Media & Society identify the book as a 2019 Polity Press title.
The book's importance is not that it was first to notice algorithmic bias. Its strength is that it refuses the thin version of the problem. Benjamin is not mainly asking whether a model contains prejudice as an accidental contaminant. She is asking how technology can inherit racial order while appearing modern, efficient, objective, innovative, and even humane.
That shift matters. If bias is only a bug, the cure looks like better training data, more diverse teams, technical audits, and fairness metrics. Those can matter. But Benjamin's argument is larger: the institution deciding what to build, whom to monitor, what to predict, whose pain counts as evidence, and what counts as progress may already be carrying the old arrangement into the new tool.
The New Jim Code
Benjamin's central phrase, the New Jim Code, names technologies that reproduce or deepen racial hierarchy while presenting themselves as race-neutral or benevolent. The Ohio State University research guide summarizes the point directly: automation can hide, accelerate, and intensify discrimination while appearing neutral compared with older forms of racism.
The phrase works because it holds two ideas together. "Code" means software and technical rule-making, but it also means the social codes that teach institutions whom to suspect, serve, exclude, protect, classify, or ignore. The system does not need an explicitly racist instruction if its inputs, categories, objectives, procurement logic, and deployment setting already encode the hierarchy.
This is why the book belongs near work on legibility and classification. A person becomes a record; the record becomes a category; the category becomes a risk score, ranking, alert, denial, or automated suspicion. The social fact is then returned to the world as if it were a technical finding.
Classification and Exposure
Princeton's coverage of the book lists the kind of examples Benjamin uses: gang databases with overwhelmingly Black and Latinx entries, automated beauty judging that selected almost entirely white winners, recidivism risk scoring that misclassified Black defendants at higher rates, and seemingly small but revealing language glitches such as a map system misreading Malcolm X Boulevard.
These examples are not all the same technically. That is part of the point. Discrimination can appear through training data, label choices, feedback loops, institutional use, user-interface defaults, surveillance intensity, error tolerance, and unequal exposure to experimental systems.
Exposure is the crucial word. Technological harm is not evenly distributed. Some people meet automation first as convenience: recommendation, speed, personalization, novelty. Others meet it first as suspicion: fraud detection, policing, welfare eligibility, border screening, school discipline, workplace monitoring, tenant scoring, or biometric misrecognition.
A system can therefore be accurate enough to sell and still unjust enough to govern badly. The test is not only benchmark performance. It is who is placed inside the machine's jurisdiction, who can contest its output, and who is forced to live with its mistakes.
Benevolent Interfaces
One of Benjamin's most useful moves is her attention to technological benevolence. Harmful systems do not always arrive with hostile branding. They arrive as safety, efficiency, health, personalization, modernization, fraud prevention, child protection, beauty, convenience, or inclusion.
The Institute for Advanced Study excerpt from the book uses the Beauty AI contest to show the pattern. A project framed as technical novelty and health-oriented assessment produced racially skewed results, then made those results look like machine judgment rather than social preference hardened into a model.
This is a general interface problem. A clean design can launder a dirty social process. A dashboard can make coercion look administrative. A score can make a contested judgment look measured. An AI answer can make a ranking decision look like knowledge. A companion interface can make asymmetrical data extraction feel like care.
Benjamin helps readers see that the moral danger often lies in the friendliness of the system. The more benevolent the interface feels, the less likely users are to ask who was classified, excluded, watched, or made available for intervention in order for that benevolence to appear.
The AI-Age Reading
The AI-era reading of Race After Technology is straightforward: foundation models, agents, AI search, workplace copilots, hiring filters, police analytics, health triage tools, and automated public services do not escape social history because their outputs are generated by statistical systems.
Shakir Mohamed's review in Nature Machine Intelligence makes that connection explicit, placing the book inside machine-intelligence work and noting examples across healthcare, policing, welfare, dating, and hiring. The point is not that every model is equally harmful. The point is that AI systems are deployed into already unequal worlds and can make those worlds easier to administer without making them more just.
For AI governance, Benjamin's book is an antidote to a narrow safety culture. It asks questions that capability discourse often skips. Who is the default user? Who is the default suspect? Which communities become test beds? Whose data is treated as public raw material? Who has appeal rights? Who is represented in the design meeting, and who is represented only as a data point?
Those questions do not replace technical evaluation. They make it honest. A model card that describes performance but not institutional purpose is incomplete. An audit that reports error rates but not exposure patterns is incomplete. A fairness metric that ignores power over deployment is incomplete.
Where the Book Needs Friction
The book is short, accessible, and deliberately broad. That makes it powerful as an entry point, but it also means some technical mechanisms receive less detail than an engineering reader may want. Predictive policing, computer vision, automated scoring, data infrastructure, user-interface design, and platform ranking each have different failure modes.
That distinction matters because good governance needs both social diagnosis and implementation detail. A database error, a biased training distribution, an invalid proxy, a badly scoped objective, a procurement incentive, and an abusive deployment context may require different interventions.
Still, this is not a serious weakness of the book's argument. It is a boundary. Benjamin is giving readers a political and ethical grammar, not a compliance checklist. The responsible next move is to bring that grammar into audits, procurement rules, participatory design, appeal systems, civil-rights enforcement, and technical practice.
The Site Reading
For this site, Race After Technology is a guide to how recursive reality becomes racialized.
A classification system does not only describe people. It changes what institutions can see, what they can ignore, what they can automate, and what they can justify later. Once those outputs circulate, they shape the next round of records, decisions, incentives, and beliefs. The loop can make an imposed category look natural because the world has been reorganized to confirm it.
That is why civil-rights literacy belongs inside AI literacy. The question is not only whether machines think, reason, align, or hallucinate. It is whether machine-mediated institutions are building a world in which some people are more searchable, more punishable, more predictable, more exposed, and less able to contest the reality being assigned to them.
Benjamin's practical demand is not despair. It is design discipline joined to political imagination: refuse neutral theater, inspect defaults, follow exposure, build appeal, include affected communities before deployment, and treat technical systems as arrangements of power. The machine is never outside the society that trains, funds, buys, and believes it.
Sources
- Ruha Benjamin, Race After Technology author page.
- Social Forces, Marie Jipguep-Akhtar, review of Race After Technology, 2019.
- Princeton University Department of African American Studies, Denise Valenti, "Benjamin's Race After Technology speaks to a growing concern among many of tech bias", May 18, 2020.
- Institute for Advanced Study, Ruha Benjamin, "Race After Technology: Shining Light on the New Jim Code", 2019.
- Shakir Mohamed, Nature Machine Intelligence, "Domesticating the techno-racial project", 2020.
- Roy Celaire, Cultural Sociology, review of Race After Technology, 2020.
- Madeleine Crutchley, New Media & Society, review of Race After Technology, 2021.
- Ohio State University Libraries, "What is The New Jim Code".
Book links are paid affiliate links. As an Amazon Associate I earn from qualifying purchases.