When I was in elementary school, I watched a movie called Hackers. You know, the 1995 one with Angelina Jolie and rollerblading through New York. I thought it was the coolest thing I’d ever seen. Then I watched Live Free or Die Hard and decided — yeah, I want to be that person. The one who understands how systems work. The one who can break things and fix things.
The funny part? I was a humanities major in college. Not computer science. Not engineering. When graduation came around, I looked at my skills and realized the only thing I was actually confident about was computers. Everything else? Not so much.
So I studied networking on my own, got a job at a small NAC (Network Access Control) solution company, eventually transferred to their development team, and that’s where it all started. Fifteen years later, I’m working in the IT division of a major Korean financial company in Gangnam.
Not a tech company. Not a startup. A financial institution. And in Korea, that’s a very different world.
Why Financial IT Is a Different Planet
When people outside Korea think about “working in tech in Korea,” they picture Naver, Kakao, Coupang — the companies Korean developers call 네카라쿠배당토 (NCLKBDT), our version of FAANG. I get it. Those companies make headlines. They’re the ones foreign tech blogs write about.
But here’s a reality most English-language content completely ignores: a huge number of Korean IT professionals don’t work at tech companies at all. We work in IT divisions of banks, insurance companies, securities firms, and financial holding companies. The work is technical. The culture is corporate. And the environment has rules that would make a Silicon Valley developer’s head spin.
The biggest one? 망분리 (mangbunli) — mandatory network separation. Korean financial companies are required by regulation to keep their internal development and production networks completely isolated from the internet. I can’t Google a Stack Overflow answer from my work machine. I can’t install a random npm package on a whim. Everything that enters or leaves our systems goes through strict security protocols.
This means no Slack. No Jira. No GitHub. We use an internally built messenger for communication and a custom-developed project management system for the entire development lifecycle — from requirements gathering, to assignment, development, testing, deployment, and post-release monitoring. Everything runs on systems we built ourselves, inside our own walls.
It sounds restrictive, and honestly, sometimes it is. But it also creates a certain discipline. You learn to be self-sufficient. You can’t rely on “just Google it.” You solve problems with what you have, or you build the tool you need.
My Career Path: Humanities Major to AI Architect
Here’s something you won’t find in most “how to become a developer” guides: my path into tech was completely non-linear.
After joining that small network security company out of college, I started as a network engineer. Then I moved to development. Then mobile planning. Then digital strategy. Then architecture. Now I’m working on AI — specifically, building LLM infrastructure on our closed network so that hundreds of internal developers can use AI-powered code assistants and development tools without any data leaving our walls.
Now, I should be honest: my career path is not typical. In Korean companies, general business staff rotate across departments fairly often, but developers and IT specialists tend to stay in their lane — they’re considered technical professionals, and they usually keep doing what they do best. I just happened to bounce around more than most.
Korean companies use a title system based on years of service — 사원 (sawon, staff) → 대리 (daeri, assistant manager) → 과장 (gwajang, manager) → 차장 (chajang, deputy general manager) → 부장 (bujang, general manager). Promotions at the lower levels are somewhat automatic, tied to years served rather than purely to skill or output.
The upside of my unusual path: I’ve seen technology from nearly every angle — infrastructure, code, product, strategy, and now AI. The downside: I’ve never had the luxury of being a deep specialist in one thing.
What the Daily Grind Actually Feels Like
I leave home from Sanseong Station around 8 AM and arrive at Gangnam Station by 8:45. About 45 minutes on the subway, shoulder to shoulder with other commuters. I’ve gotten good at reading articles on my phone while being gently compressed from all sides.
The office dress code used to be strict — full suit and tie for everyone, even those of us who never met a single customer face-to-face. That changed around COVID. Now it’s completely casual. Almost everyone wears jeans and sneakers. The only exception is the sales team and other customer-facing departments — they still suit up. But for IT? We dress like we’re heading to a coffee shop. The transformation was sudden and nobody wants to go back.
Lunch is usually at the company cafeteria — ₩6,500 ($4.70) for a full Korean meal: rice, soup, three or four side dishes, and kimchi. The menu rotates daily. Some days are genuinely great. When I eat out instead, which happens maybe once or twice a week, lunch in Gangnam runs ₩10,000 to ₩13,000 ($7–$9.50). Lunchflation — 런치플레이션, as Korean media calls it — is real. A few years ago, eating out was closer to ₩8,000.
After lunch, the team grabs coffee. Usually one of the budget chains — Mammoth Coffee, Bana Presso, Compose Coffee, Mega Coffee — the Korean low-cost franchises where an iced Americano costs ₩2,000 ($1.50). Someone says “커피 한 잔 하자” (let’s grab a coffee) like it’s a spontaneous idea, not a ritual we perform every single day.
On-Call Nights and the 2 AM Myth
Here’s where I want to correct a narrative I see everywhere in English-language content about Korean tech: the idea that Korean developers are constantly pulling all-nighters, getting emergency calls at 3 AM, and living in a state of perpetual crisis.
That used to be closer to the truth. Years ago, outages were frequent. Services went down. Something would break at 2 AM. You’d groggily open your laptop, remote into the system, and start digging through logs half-asleep.
But systems have matured. Technology has improved. Infrastructure is more stable. The dramatic 2 AM emergency that makes for a great blog post opening? It’s rare now. Really rare.
I still get on-call alerts through our operations team — what we call OP. But most of them are things like filesystem usage hitting 80%, or CPU load exceeding thresholds. Non-critical stuff. The kind of thing I note on my phone, then handle first thing the next morning when I get to the office. Actual service-down situations? They happen, but they’re extremely uncommon these days. And when they do, I open my laptop at home and remote in — no dramatic midnight drives to the office.
The honest truth that doesn’t make for exciting content: developer life in Korea has gotten significantly better over the past few years. The all-nighters, the sleeping-at-the-office stories, the not-going-home-for-days marathons — I don’t see that around me anymore. Maybe it’s just my circle. Maybe financial IT is different from startup life. But the people I know are going home at reasonable hours. And it feels… normal. Finally.
The 6 PM Shutdown
Here’s a detail that surprises people: at our company, PCs automatically shut down at 6 PM.
This isn’t a suggestion. It’s a system-enforced shutdown. The reason is straightforward — if you work past 6, the company has to pay overtime. And Korean labor law takes overtime compensation seriously now. So rather than deal with the accounting complexity, many large Korean companies simply made staying late structurally difficult.
Can I still work late when I need to? Yes. If there’s a task that has to happen outside business hours — like a deployment that can’t run during service hours — I’ll stay an extra hour or two. Those cases exist. But the days of sitting at your desk until 10 PM because your boss hasn’t left? That culture is effectively dead at companies like mine.
This is a massive change from even five or six years ago. Korean corporate culture used to run on 눈치 (nunchi) — that instinct for reading the room. Leaving before your boss left was seen as a statement. Now, the PC turns off, and everyone goes home. Technology solved a cultural problem that decades of complaining couldn’t.
What’s Changed — The Before and After
I’ve been in this industry long enough to remember the “before.”
Before: Wearing a full suit every day to sit in front of a monitor. Staying late because everyone else was staying late. Frequent outage alerts waking you up at night. Hoesik (회식, after-work dinners) that were mandatory and lasted three rounds of drinking.
After: Jeans and sneakers. PC off at 6. On-call alerts that are mostly routine. Hoesik that’s now optional, often just lunch, and nobody pressures you to drink.
COVID accelerated most of these changes, but the shift was already happening. The MZ generation — Korea’s term for millennials and Gen Z — pushed hard against the old culture. They asked “왜요?” (Why?) when given tasks without context. They left at quitting time without guilt. Some older managers call them lazy. I think they just have better boundaries than we did.
The generational tension is real. There’s a Korean word for out-of-touch seniors who lecture younger workers: 꼰대 (kkondae). And the MZ generation’s favorite comeback is mocking the phrase “라떼는 말이야” — a play on “라떼” (latte) that sounds like “나 때는 말이야” (back in my day). It’s become such a meme that older workers are genuinely afraid of being called a kkondae.
I’m in my forties now. That puts me in an awkward middle ground. I remember the old ways. I also think most of them were genuinely wasteful. Junior employees sitting at their desks for hours doing nothing, just waiting for the boss to leave — that wasn’t dedication. That was theater.
AI in the Financial Bunker
The hottest topic in my work right now is AI — specifically, deploying large language models inside our network-separated environment. But not for the reason you might think. We’re not building AI to serve customers or analyze financial data. We’re building it for our own developers.
Our company has hundreds of internal developers, and the goal is to give them AI-powered code assistants and development tools — think GitHub Copilot, but running entirely inside our closed network. When the rest of the world just opens a browser and uses ChatGPT or Claude, we’re figuring out how to run LLMs on isolated servers behind firewalls that don’t touch the internet.
It’s a fascinating challenge. How do you fine-tune a model without internet access? How do you update it? How do you evaluate it against benchmarks when your system can’t reach Hugging Face? The 망분리 (network separation) that makes everyday work frustrating becomes a genuine technical puzzle when you’re trying to implement cutting-edge AI.
These are the problems I think about now. A long way from watching Hackers as a kid.
What Foreigners Get Wrong
Let me address a few things I consistently see in English-language content about working in Korean tech:
“Korean developers work 16-hour days.” Maybe at some startups, during crunch time. But at large financial companies? My PC shuts down at 6. The extreme overtime stories are increasingly historical, not current.
“The Korean tech scene is just Samsung and startups.” There’s an enormous middle ground that nobody writes about in English: the IT divisions of banks, insurance companies, telecom firms, and conglomerates. Thousands of IT professionals work in these environments. The culture is different from a Pangyo startup, the tools are different, the constraints are different — but the work is real and often more complex than people assume.
“You need a CS degree to work in Korean tech.” I’m a humanities major. I got into this industry because I loved computers, studied networking on my own, and took opportunities as they came. Is a CS degree helpful? Obviously. Is it required? My fifteen-year career suggests otherwise.
“Korean work culture is toxic.” Parts of it were. Some parts still are, somewhere. But the Korea I work in today is genuinely different from the Korea I started working in. The hours are shorter. The dress code is relaxed. The hierarchy has softened. The hoesik is optional. It’s not perfect. But the direction of change is undeniably positive.
The Honest Summary
Some days, I get an on-call alert at midnight about a filesystem hitting 80% capacity. I check my phone, make a mental note, and go back to sleep. I’ll handle it tomorrow.
Other days, I eat a ₩6,500 cafeteria lunch that’s honestly better than most restaurant meals, grab a ₩2,000 iced Americano with my team, and spend the afternoon figuring out how to make an AI code assistant work inside a network that can’t reach the outside world.
I wear jeans. I go home when my PC shuts down at 6. I started as a humanities major who loved a cheesy 90s hacker movie, and now I’m building AI code assistants on a financial institution’s closed network.
It’s not glamorous. It won’t make TechCrunch. But it’s real, it’s stable, and after fifteen years — honestly? It’s pretty good.
That’s what working in Korean tech looks like — at least, my version of it. Not the startup version. Not the 네카라쿠배 version. Just one Korean IT guy’s life in Gangnam.
Related Posts: