Why Gen Z is Obsessed with Kafka
It hit me during a coffee break at a conference last year. Two engineers, maybe 24 and 25, were arguing about Kafka. Not the streaming platform. The writer. One had "Metamorphosis" tattooed on their forearm. The other was defending "The Trial" as the better entry point. I've built production systems at SIVARO that process 200,000 events per second. I've debugged Kafka cluster failures at 2 AM. But watching Gen Z dissect Franz Kafka with the same intensity we reserve for debugging distributed systems? That made me stop.
So what is this actually about? Franz Kafka was a German-speaking Bohemian writer who died in 1924 at 40. He wrote novels and short stories about absurd bureaucracy, existential dread, and alienation. He asked his friend Max Brod to burn his unpublished work. Brod didn't. Now Franz Kafka is somehow the patron saint of Gen Z. And the question "why is gen z obsessed with kafka?" isn't just cultural curiosity — it's a signal about how a generation sees the world.
I'm going to walk through exactly why this happened, what Kafka actually wrote that resonates, and what a 100-year-dead Czech insurance clerk can teach us about building systems for a generation that grew up with algorithmically-enforced absurdity.
What Was Kafka Famous For?
Let's get the basics straight. Franz Kafka is famous for writing about situations where the rules don't make sense and nobody can explain them to you. In "The Trial," a man named Josef K. is arrested for a crime that's never named. In "Metamorphosis," a salesman wakes up as an insect and his family slowly stops caring about him. In "The Castle," a land surveyor can't get access to the castle that hired him.
These aren't horror stories. They're anxiety stories. They capture the feeling of being trapped in a system that operates on logic you can't access. That's the core of why gen z is obsessed with kafka. They grew up in systems — algorithmic feeds, gig economy platforms, admissions processes — that operate exactly like that.
There's a term for it: Kafkaesque. It means situations that feel nightmarish in their irrationality. But here's what most people miss. Kafka wasn't writing about dystopian futures. He was writing about his present. He worked at an insurance company. He saw the bureaucracy of the Austro-Hungarian Empire. He knew exactly what it felt like to fill out forms that would never be read by anyone who could change anything.
Sound familiar?
The Algorithm as The Castle
I've spent years building production AI systems. I know how recommendation algorithms work under the hood. But most people don't. And that's the point.
Gen Z is the first generation that grew up with algorithmic curation as the default experience. Instagram decides what you see. TikTok decides what's trending. College admissions are a black box. Job applications go through automated resume screeners. You don't know why you got rejected. You can't appeal. There's no human you can talk to.
This is literally the plot of "The Castle." K. can see the castle. He knows he's supposed to work there. But he can never get in. Nobody will tell him why.
Gen-Z's obsession with Kafka & Dostoevsky frames this as a generational trauma response. I think that's half right. It's not trauma — it's recognition. Gen Z reads Kafka and thinks "This guy gets it. He lived it in 1915. I'm living it in 2024."
The difference is scale. Kafka dealt with one castle, one trial, one bureaucratic process. Gen Z deals with a dozen castles simultaneously. Every platform is a castle. Every application process is a trial. Every algorithm is an unseen judge who never explains the verdict.
The Insect Identity
Let's talk about "Metamorphosis." Gregor Samsa wakes up as an insect. His first concern? He's going to be late for work. His boss will be angry. His family will lose income.
This is the most Gen Z paragraph ever written, and it was written in 1912.
Why GenZ is ADDICTED To This Author? points out that the economic anxiety in Kafka mirrors Gen Z's reality. They entered the workforce during or after COVID. They face housing costs that dwarf their parents' generation. They see automation threatening their jobs. They're told to be grateful for any opportunity while being treated as disposable.
Gregor Samsa becomes useless to his family the moment he can't work. His value was entirely instrumental. That's not 1912. That's 2024. That's the gig economy. That's the concept of "quiet quitting" — the realization that your employer doesn't actually care about you.
I've seen this play out in tech. I've watched companies lay off entire teams via automated emails. I've seen managers who never met their direct reports. I've built systems that replace human decision-making with rules. And every time, I think about Gregor Samsa's boss showing up at his apartment to yell at him for being late.
The Unburned Manuscripts
Kafka told Max Brod to burn his unpublished work after his death. Brod didn't. We now have "The Trial," "The Castle," and "Amerika" because one friend disobeyed a dying wish.
This generates a specific kind of obsession. Do you think that F. Kafka wanted his writings destroyed ... asks whether this was vanity or genuine self-critique. The answer matters to Gen Z because they live in the opposite world.
Everything they create is preserved. Every tweet. Every Instagram story. Every TikTok. Every embarassing phase. It's all archived, searchable, and potentially viral. Kafka wanted his worst work destroyed. Gen Z can't destroy anything.
That's a specific kind of pressure. Kafka got to control his legacy — or tried to. Gen Z has no control. An old post can resurface and cost you a job. An offhand comment can go viral and define you forever. Kafka's anxiety was about his work being exposed. Gen Z's anxiety is about everything being exposed.
And here's the ironic twist. Kafka's fame comes because Brod disobeyed. If Kafka had lived, he might have published polished versions. The unfinished, imperfect works are what resonate. 100 years after his death, Gen Z loves Franz Kafka makes this point directly — Gen Z connects with the incomplete, the anxious, the not-quite-perfect.
That's a generation that grew up with curated feeds and learned that curation is a lie.
The Absurdity of Modern Work
I run a product engineering company. I've hired dozens of people. I've watched the application process from both sides. It's Kafkaesque.
Consider a typical software engineering interview process:
- Submit resume (automatically parsed, probably wrong)
- Pass a coding test (unrelated to actual work)
- Do a take-home assignment (takes 20 hours)
- Pass a system design interview (mostly guessing what the interviewer wants)
- Do behavioral interviews (don't say anything authentic)
- Wait 3 weeks for an offer
- Get rejected with no reason
Sound familiar? It should. It's "The Trial" with LeetCode questions.
A Reddit thread titled Why Gen-z is so obsessed by Kafka? had a comment that stuck with me: "Kafka wrote about the horror of systems that don't make sense. My entire job application experience is that."
I've been on both sides. I've designed interview processes. I've seen them fail. Most hiring is a ritual to make the company feel rigorous, not to actually find good candidates. That's Kafkaesque. The ritual exists for its own sake, not for any useful outcome.
The Memetic Power
Here's where it gets interesting. Gen Z didn't discover Kafka through a literature class. They discovered him through memes.
There's a specific format: a screenshot of a Kafka quote over a bleak image. The quote is usually something like "I am a cage, in search of a bird" or "There is an infinite amount of hope — but not for us." These get shared on Instagram, TikTok, Twitter.
This is how Kafka becomes a cultural touchstone without anyone reading the books. Why GenZ is SECRETLY OBSESSED with this author breaks this down — Kafka works as a vibe. You don't need to read "The Trial" to understand that life feels like a bureaucratic nightmare. You just need to see one screenshot.
I'm not gatekeeping here. I've read all of Kafka. I've also seen the memes. The memes are actually good. They capture the emotional core. They make people curious. Some percentage of those people read the actual books. That's a better pipeline than any literature class ever built.
The nss magazine article Why is Gen Z obsessed with Kafka? calls this "aesthetic identification." Gen Z doesn't just like Kafka's ideas — they like Kafka as a character. The tortured writer who died young and obscure, only to become famous after death. That's a narrative that works on Instagram.
The Practical Lessons for Engineers
I'm a systems builder. I think in terms of infrastructure. So let me connect this to what I actually do.
If you're building systems that Gen Z will use or work on, here's what Kafka teaches you:
1. Explainability is not optional
Kafka's protagonists go insane because nobody explains anything. Your system should explain itself. Why was this decision made? What data informed it? Who can I talk to about it?
I've built recommendation systems. The best ones don't just give results — they show why. "We recommended this because you watched X." That's not just good UX. It's an antidote to Kafkaesque anxiety.
2. Bureaucracy is the enemy
Kafka's horror was bureaucracy. Don't build it into your systems. Don't make users fill out forms that nobody reads. Don't create approval processes that exist for their own sake.
I've debugged systems where the bottleneck was not the database or the network — it was a human approval step that could have been automated. That's Kafkaesque. If you can automate it, automate it.
3. The algorithm should have a human face
Gen Z trusts algorithms less than any previous generation. They've seen what happens when social media algorithms optimize for engagement. They know that "the algorithm" is not neutral.
Your system should have a human somewhere who can override it. Not just in theory — in practice. A phone number. An email. A real person who can say "I see this happened, it was wrong, I'm fixing it."
4. Error messages should be honest
Kafka's characters get no explanations. Your users should get explanations. If something failed, say why. If you can't explain it, that's a problem with your system, not with the user.
Here's a real example. At SIVARO, we had a system that rejected certain data inputs. The error message was "Invalid input." That's Kafkaesque. We changed it to "Input contains field X with value Y, which violates constraint Z. Maximum allowed value is 42." Users went from angry to grateful.
Code Example: The Anti-Kafkaesque Error Handler
python
# Kafkaesque approach (don't do this)
def process_request(data):
try:
result = validate_and_transform(data)
return result
except:
return {"error": "Processing failed"}
# Anti-Kafkaesque approach
def process_request(data):
try:
result = validate_and_transform(data)
return result
except ValidationError as e:
return {
"error": "validation_failed",
"field": e.field,
"value": e.value,
"constraint": e.constraint,
"documentation_url": f"/docs/errors/{e.error_code}"
}
except TransformationError as e:
return {
"error": "transformation_failed",
"step": e.step,
"input_summary": summarize(e.input),
"suggested_fix": e.suggestion
}
See the difference? One gives you nothing. The other gives you an explanation, a path forward, and a way to learn more.
Code Example: Transparent Recommendation
python
# Black box recommender
def recommend(user_id):
scores = model.predict(user_id)
return [item.id for item in scores.top(10)]
# Transparent recommender
def recommend(user_id):
scores = model.predict(user_id)
recommendations = []
for item in scores.top(10):
reasons = []
for signal in ["watch_history", "similar_users", "trending", "new_releases"]:
weight = model.explain(user_id, item.id, signal)
if weight > 0.1:
reasons.append({
"factor": signal,
"weight": round(weight, 2),
"display": signal_to_label(signal)
})
recommendations.append({
"item": item.id,
"score": round(item.score, 3),
"reasons": reasons
})
return recommendations
This is slightly more complex. It's also not that much more complex. And it changes the user experience from "the algorithm decided" to "here's why this was recommended."
Code Example: Recursive Bureaucracy Detection
python
# This is me at 3 AM debugging a Kafka cluster
# (the streaming kind, not the writer)
def detect_kafkaesque_bottlenecks(pipeline):
"""
Find stages where work is being done but no output is produced
"""
bottlenecks = []
for stage in pipeline.stages:
input_count = stage.input_counter.value
output_count = stage.output_counter.value
error_count = stage.error_counter.value
throughput_ratio = output_count / input_count if input_count > 0 else 0
if throughput_ratio < 0.01 and error_count == 0:
# Writes are being accepted but never processed
# This is the digital equivalent of "The Castle"
bottlenecks.append({
"stage": stage.name,
"throughput_ratio": throughput_ratio,
"likely_cause": "data_loss_or_silent_drop",
"kafka_equivalent": "The Castle"
})
elif throughput_ratio < 0.5 and error_count == 0:
bottlenecks.append({
"stage": stage.name,
"throughput_ratio": throughput_ratio,
"likely_cause": "backpressure_without_feedback",
"kafka_equivalent": "The Trial"
})
elif error_count > 1000 and error_count == list(set(stage.error_types)):
# Every possible error type has been hit
# Your system is a haunted house
bottlenecks.append({
"stage": stage.name,
"every_error_possible": True,
"kafka_equivalent": complete_breakdown
})
return bottlenecks
I wrote this after a particularly bad night debugging a pipeline that silently dropped 30%% of events. Nobody knew. The outputs looked fine. It took three days to find. That's pure Kafka.
The Death of the Author (and the Birth of the Meme)
Kafka died in 1924. He was relatively unknown. He published a few short stories. His novels were unfinished. His friend Brod went against his wishes and published everything.
This story is now inseparable from Kafka's work. You can't read "The Trial" without knowing that Kafka wanted it destroyed. That changes the reading. Every unfinished sentence feels intentional. Every ambiguous ending feels like a choice, not a failure.
Franz Kafka Wikipedia has the full timeline. 1924: death. 1925: "The Trial" published. 1926: "The Castle." 1927: "Amerika." The man was gone. The work kept coming.
Gen Z understands this. They've watched artists die and their work become more valuable. They've seen dead musicians get more streams than living ones. They know that legacy is weird. Kafka's trajectory — obscure in life, immortal in death — is the dream and the nightmare.
Why Now? The 2024 Moment
There's a specific reason Kafka is exploding in 2024, not 2014 or 2004.
2024 marks 100 years since Kafka's death. That's a centennial. There are events, articles, retrospectives. The Jewish Telegraphic Agency covered this — Kafka was Jewish, his works were burned by Nazis, and now he's being reclaimed.
But the bigger reason is AI. 2024 is the year generative AI went mainstream. Everyone suddenly understands what it feels like to interact with a system that produces plausible but wrong outputs. Everyone has been gaslit by ChatGPT. Everyone has had an AI say something completely confident and completely incorrect.
That's Kafkaesque. You ask a question. You get an answer. The answer looks right. But you can't verify it. The system doesn't explain itself. You're supposed to trust it. But you can't.
I've talked to engineers who trained LLMs. They described the experience of debugging a model that keeps saying "I don't know" when it clearly has the answer, or confidently making up facts. One said "It's like talking to a bureaucrat who doesn't know the rules but won't admit it."
That's Kafka. That's "The Trial." That's a system that runs on logic you can't access.
The Generational Divide
Older critics sometimes dismiss Gen Z's Kafka obsession as shallow. They say it's about aesthetics, not literature. They're right about the aesthetics. They're wrong about the shallowness.
Facebook discussion threads show the tension. Older readers talk about Kafka as literature — symbolism, structure, historical context. Younger readers talk about Kafka as therapy — "this is how I feel," "this is my life," "this writer understood me."
Neither is wrong. But the Gen Z reading is more honest. They're not analyzing Kafka. They're using him to make sense of their world. That's what literature is supposed to do. Academics wrapped it in jargon and turned it into a career. Gen Z is unwrapping it.
A post on the neurospicy researcher substack Gen-Z's obsession with Kafka & Dostoevsky calls this "emotional labor." I think it's simpler. Gen Z is trying to survive. Kafka helps. They're not writing papers about alienation. They're reading about a guy who turned into an insect and thinking "yeah, that's how it feels when my boss emails me at midnight."
The Practical Takeaway
I'm not a literary critic. I'm an engineer who builds systems. Here's what I learned from watching this unfold.
Systems should be explainable. If you can't explain what your system does and why, you've built a Kafka story. Your users will feel like they're in "The Trial."
Bureaucracy is a bug, not a feature. Every approval step, every form, every gate — ask yourself if it actually prevents harm or just creates work. Most of the time, it's the latter.
Trust is earned through transparency. Gen Z has been burned by algorithms. They don't trust "the system." They trust systems that show their work.
Vulnerability is a feature. Kafka's unfinished works are his most famous. Perfection is a trap. Ship early. Ship often. Let your users see your process.
I've applied this at SIVARO. Our data pipelines report their confidence. Our AI systems explain their reasoning. Our error messages tell you what went wrong and how to fix it. We're not perfect. But we're not Kafkaesque.
FAQ: Gen Z and Kafka
Q: Why is Gen Z obsessed with Kafka?
A: Multiple reasons: Kafka's themes of bureaucratic absurdity mirror Gen Z's experience with algorithmic systems, job applications, and economic precarity. His aesthetic — bleak, existential, honest — resonates on social media. And the centennial of his death in 2024 brought renewed attention. The nss magazine article covers this comprehensively.
Q: What was Kafka famous for?
A: Writing about absurd bureaucracies, unexplained punishments, and existential dread. His most famous works are "The Trial" (a man arrested for an unknown crime), "Metamorphosis" (a man wakes up as an insect), and "The Castle" (a man can't access the castle that hired him). The Wikipedia page has the full biography.
Q: Did Kafka really want his work destroyed?
A: Yes. He asked his friend Max Brod to burn his unpublished manuscripts. Brod didn't. This is now one of the most famous literary decisions in history. The Quora discussion on this topic explores the ethical and literary implications.
Q: Is Gen Z reading Kafka or just sharing memes?
A: Both. Memes drive discovery. Some percentage of meme-sharers actually read the books. The YouTube breakdown on this dynamic argues that the memes are surprisingly faithful to Kafka's themes.
Q: Why is Kafka relevant to AI and technology?
A: Because Kafka wrote about systems that operate on hidden logic. Algorithms, recommendation systems, and AI models are exactly that. The feeling of being judged by a system you can't understand — that's Kafka. I wrote about this from an engineering perspective above.
Q: Is this just a trend that will pass?
A: Partially. The centennial-driven spike will fade. But Kafka's themes are permanent. As long as there are bureaucracies, algorithms, and systems that don't explain themselves, Kafka will be relevant. The Reddit discussion has a thread arguing this will last.
Q: What should I read first?
A: Start with "Metamorphosis." It's short (70 pages), it's the most accessible, and it's the most immediately relatable. Then "The Trial." Then "The Castle" if you want to suffer. The Facebook discussion group has reading order recommendations.
Q: How is Kafka related to Dostoevsky?
A: Both write about existential crisis, alienation, and suffering. But Dostoevsky wrote from a Christian perspective (redemption through suffering). Kafka wrote from a secular, bureaucratic perspective (there is no redemption, only more forms). The substack article comparing both authors is excellent.
Closing Thought
I started this article thinking about a simple question: why is gen z obsessed with kafka? I end it thinking about what that obsession tells us about the systems we're building.
Every time you build an opaque algorithm, you're writing a new chapter of "The Trial." Every time you add an approval step without explaining why, you're extending "The Castle." Every time you design an error message that says "something went wrong," you're turning your users into Gregor Samsa.
Don't do that. Build systems that explain themselves. Build systems that can be appealed. Build systems that treat users like humans, not insects.
Kafka died in 1924. His work survives because he captured something true about human experience under indifferent systems. We can't fix all of society. But we can fix the systems we control.
That starts with asking — every time you write a line of code, every time you design a process, every time you decide what to tell the user — "am I building Kafka's world, or am I helping people escape it?"
Nishaant Dixit — Founder of SIVARO. Building data infrastructure and production AI systems since 2018. Built systems processing 200K events/sec.