Quiet Quitting, Korean Developer Edition

There's One on Every Team

Shows up in the morning, does the assigned work, clocks out on time.

Slack reactions are a single emoji. Code reviews are one-line "LGTM"s. Minimal contributions in meetings. Name absent from tech seminars. No side projects. It's not that they can't do the work. They deliver what's asked. They just don't do anything beyond what's asked.

Quiet quitting. Not actually resigning — just doing the bare minimum.

It's Different from the American Version

In the US, quiet quitting is closer to setting rational boundaries: "I won't do work that's not in my job description." An active practice of work-life balance.

In Korea, the texture is different. Quiet quitting is often not a choice but the result of burnout.

The person who used to code through the night as a junior, run side projects, write blog posts, give conference talks — they go quiet around their 3rd or 4th year. Their passion didn't cool off. It burned out. The fuel tank hit empty.

The Invisible Expectations

There are unspoken expectations in the Korean tech industry.

Study after work. Keep up with new tech trends. Run side projects. Fill in your GitHub contribution graph. Maintain a tech blog. None of this is in the employment contract. But if you don't do it, you get labeled as "someone who doesn't care about growth."

After writing code for 8 hours, should you have to write more code at home to be considered growth-minded? If you told a chef to cook after clocking out, you'd think that's weird. If you told an architect to design buildings on weekends, you'd call it unfair. Why is this expectation uniquely generous toward developers? (The more I think about it, the stranger it seems.)

Watching That Colleague

Watching a colleague who's quiet-quitting brings up mixed feelings.

Part of me worries, "won't their growth stall?" The other part thinks, "isn't that actually healthy?" If you give 120% every day, you'll eventually go into the negatives. Sustaining 80% consistently might actually take you further in the long run.

Like how a marathon runner doesn't sprint from the start. A developer career is a marathon, not a sprint. I think that's true, but it's hard to practice. It's hard to walk when everyone else is running.

It's a Systems Problem

Organizations that rely on individual passion don't last.

If quiet quitting is on the rise, it's not an attitude problem — it's a systems problem. Is the organization offloading growth onto employees' personal time and money? Is it trying to solve motivation with "passion" alone?

Good organizations create structures where people can grow within work hours. They guarantee learning time, give room to reduce tech debt, and allow experimentation. If employees have gone quiet, look at the environment before blaming the individual.

Going Quiet Is a Survival Strategy Too

Sometimes I want to ask that colleague if they're okay.

But I don't. Because that's their pace. Whether it's a choice or burnout, they have the rhythm they need right now.

Sometimes going quiet is a way to survive. You don't have to be MVP every season. Some seasons, just staying in the game is what matters.

Just — I hope the quiet doesn't become resignation.

There's a difference between resting and giving up. Probably.