Chaos and Order

💡 왼쪽 원문을 읽으면서 오른쪽에 따라 써보세요. Tab 키로 힌트를 받을 수 있습니다.

원문 렌더가 준비되기 전까지 텍스트 가이드로 표시합니다.

Why English + Japanese still matter in 2026

The 2026 Korean developer market splits into two tracks. One side is companies where English is the de facto operating language — Toss, Coupang, LINE, Dunamu. The other is the Japan-anchored career path through Mercari, Yahoo Japan, LINE, DeNA, Rakuten. Both demand the same micro-skills beyond writing code: drafting an elegant PR description in English, or reaching consensus with a Japanese senior manager in 30 seconds during an incident.

This guide lays out 21 scenarios side by side: Korean intent → English (formal + casual) → Japanese (敬語 + business casual). The goal is less about memorizing phrases and more about **tone calibration** — reducing cultural friction without softening directness.

1. Self-introduction - The onboarding hello

Day one in Slack `#introductions` or the first team meeting. The most common Korean-speaker mistake: opening with an apologetic tone like "I'm new here." Global teams treat new members as assets, not liabilities.

| --- | --- | --- | --- | --- |

| First introduction, joining as backend | Hello team, I'm Youngju, joining as a backend engineer on the Payments squad. | Hey folks, Youngju here, new backend on Payments. Excited to be here! | はじめまして、本日付でPaymentsチームにバックエンドエンジニアとして入社しました金と申します。 | はじめまして、金です。今日からPaymentsでバックエンドやります、よろしくお願いします。 |

| Previous experience with payments | Previously, I led the payment infrastructure team at company X for three years. | Last gig was leading payments infra at X for ~3 years. | 前職ではX社で決済基盤チームを3年間リードしておりました。 | 前は X で3年くらい決済の基盤やってました。 |

**Common Korean-speaker pitfall**: "I hope I can contribute" reads as low confidence in English. Pair intent with value: "I'm here to help us ship faster on Payments."

2. Standup / Daily

Async standup (Slack text) or live Zoom — the core is **Yesterday / Today / Blockers**, three lines. The Korean narrative pattern ("there was this issue yesterday, so I ended up...") inflates the message.

| --- | --- | --- | --- | --- |

**Tip**: In English-speaking environments, "Y / T / B" abbreviations are widely used. In Japan, "昨日 / 今日 / 障害" or "やったこと / やること / 困りごと" appear often.

3. Code review - Requesting changes politely

The trickiest tone area for Korean developers. Direct-translated "This is wrong" reads as aggressive in global teams. But too much hedging loses the information.

3.1 Comment prefix conventions - nit, blocker, suggestion

| --- | --- | --- | --- |

3.2 Verb intensity spectrum

In English code review a single verb sets the tone. Ordered from soft to hard:

| Soft → Hard | Verb / phrase | Korean nuance |

| --- | --- | --- |

| 1 | `consider ...ing` | "you might want to think about" |

| 2 | `it might be worth ...ing` | "it could be worth" |

| 3 | `I'd suggest ...ing` | "I'd recommend" |

| 4 | `we should ...` | "we should probably" |

| 5 | `we need to ...` | "we have to" |

| 6 | `we must ...` / `this must be fixed before merge` | "must do this (before merge)" |

3.3 Scenario table

| --- | --- | --- | --- | --- |

| Missing null check | This function doesn't handle the null case — could you add a guard? | blocker: null case isn't handled, can you add a guard? | こちらの関数で null のケースが処理されていないように見えます。ガードを追加していただけますでしょうか。 | ここ null のケース落ちてる気がする、ガード入れて! |

3.4 Words Korean developers should avoid

- `obviously` / `clearly` — direct-translated from "당연히" or "명백히". Reads as "you should know this."

- `just` — minimizes the work. "Just use the helper" → "I'd use the helper here" is safer.

- `actually` — corrective tone. "It actually returns null" → "It returns null in this case."

- `simply` — same trap as `just`.

- `should be easy to fix` — sounds like pressure when the author is struggling.

4. PR writing - Title, body, Conventional Commits

The 2026 standard is still Conventional Commits. Title within 50 chars, body with three sections: **What / Why / How tested**.

4.1 Title prefix table

| Prefix | Use | Example |

| --- | --- | --- |

| `feat:` | new feature | `feat(payment): add Apple Pay support` |

| `fix:` | bug fix | `fix(auth): handle expired refresh token` |

| `refactor:` | refactor without behavior change | `refactor(api): extract retry helper` |

| `perf:` | performance | `perf(db): add index on user_id` |

| `docs:` | docs only | `docs(readme): clarify setup steps` |

| `test:` | tests | `test(payment): cover Apple Pay path` |

| `chore:` | build / tooling | `chore(deps): bump next to 15.4` |

| `ci:` | CI changes | `ci: cache node_modules in pipeline` |

| `revert:` | revert | `revert: feat(payment): add Apple Pay support` |

| `BREAKING CHANGE:` | breaking change | add a `BREAKING CHANGE: ...` line in body |

4.2 PR body templates

| --- | --- | --- | --- | --- |

| Breaking change marker | BREAKING CHANGE: `payment.create()` now requires `currency`. | BREAKING CHANGE: `payment.create()` needs `currency` now. | 破壊的変更: `payment.create()` に `currency` が必須になります。 | 破壊的変更あり、`payment.create()` で `currency` 必須にした。 |

4.3 Scope naming tips

The scope in `feat(scope):` is usually the folder or domain name. `feat(api): ...`, `feat(web/payment): ...` — slash-separated hierarchies are common.

5. Incident response - SEV1/SEV2 phrasing

Incident channels follow a **3-second rule**: one sentence captures *what / who / when from*. The Korean-speaker pitfall: writing only "I'm looking into it" without naming the ownership area.

5.1 SEV severity labels

| Level | Meaning | Japanese |

| --- | --- | --- |

| `SEV1` | full outage, revenue impact | 重大障害 (じゅうだいしょうがい) |

| `SEV2` | core feature partially down, some users affected | 部分障害 |

| `SEV3` | non-core feature, workaround exists | 軽度障害 |

| `SEV4` | internal tool, no external impact | 内部障害 |

5.2 Scenario table

| --- | --- | --- | --- | --- |

| Detected elevated errors on payment | We're seeing elevated 5xx errors on `/payment/create` — opening SEV2. | seeing elevated 5xx on /payment/create, calling SEV2. | `/payment/create` で 5xx エラーが急増しております。SEV2 として対応開始します。 | /payment/create で 5xx 上がってる、SEV2 開ける。 |

5.3 Why "blameless" matters

In English-speaking postmortems, "blameless" is almost a religious keyword — a covenant to flip the question from "Who broke prod?" to "What in our system made it possible to break prod?" Japan picked this up via Mercari and Cookpad as "犯人探しをしない" (no manhunt), which is even more explicit than the Korean equivalent.

6. 1on1 - One-on-one with your manager

The golden rule: **the IC owns the agenda**. A 1on1 where the manager opens the topic is essentially a status meeting. The Korean "I don't really have anything" answer zeroes out the value of 1on1.

6.1 Agenda categories

| Category | Meaning | English example |

| --- | --- | --- |

| Career growth | growth / promotion | "I'd like to chat about my growth path to staff." |

| Feedback for me | feedback I'm receiving | "What's one thing I could be doing better?" |

| Feedback for you | feedback I'm giving the manager | "I have some feedback for you, can I share?" |

| Project | project state | "Quick update on Payments v2 — we hit X." |

| Personal | personal | "I'd like to share something personal." |

| Team dynamics | relationships in the team | "I want to talk about the dynamic with X." |

6.2 Scenario table

| --- | --- | --- | --- | --- |

7. Requirements meeting - Resolving ambiguity

The Korean-speaker pattern: nodding "yes I understand" in the meeting, then asking the same question in Slack afterward. Inefficient in both English-speaking and Japanese teams.

7.1 Surfacing ambiguity

| --- | --- | --- | --- | --- |

7.2 What "let's take this offline" actually means

In video-meeting age, "offline" means "outside this meeting." It's a polite topic blocker: "this topic is too long to unblock here — let's schedule separately." Japanese equivalent: "別途調整" / "別途お時間いただけますか."

8. Data analysis reports - KPI, north star, lift

Sharing A/B test results or quarterly reviews. Statistical vocabulary is the foundation of trust.

| --- | --- | --- | --- |

8.1 Presentation scenarios

| --- | --- | --- | --- | --- |

**Korean-speaker pitfall**: don't conflate `significant` and `meaningful`. `Significant` is statistical; `meaningful` is business impact. "0.1% lift was significant but not meaningful" is a perfectly valid sentence.

9. PTO / OOO - 育休, 有給, vacation

| --- | --- | --- | --- | --- |

**Japan culture note**: 有給 (yuukyuu, paid leave) is a right, but the "everyone takes it" culture isn't universal. Mercari and other globalized firms encourage PTO actively; traditional SIers still carry an apologetic tone.

10. Declining - Saying NO gracefully

The hardest area for Korean developers. "I'll try" is read as "YES" in English-speaking environments; "it'll be difficult" is read as "NO" in Japanese — culture collisions abound.

| --- | --- | --- | --- | --- |

**ESL tip**: When declining in English, almost always pair the no with an **alternative or reason**. `No, but here's what I can do: ...`

11. Apologies - Calibrating responsibility

In English, `I'm sorry` and `I apologize` carry different weights — the latter is more formal. Japanese has finer gradations.

| --- | --- | --- | --- | --- |

**Japanese apology gradations** (by weight):

1. すみません - light apology

2. ごめんなさい - personal

3. 申し訳ございません - business standard

4. 大変申し訳ございません - heavier

5. 誠に申し訳ございませんでした - formal public apology (e.g., outage notice)

12. Praise - Beating praise inflation

English-speaking workplaces have heavy praise inflation — `Great work!` is almost a greeting. For meaningful praise, **specificity** is required.

| --- | --- | --- | --- | --- |

12.1 Mapping Korean "수고하셨습니다" to English / Japanese

- "수고하셨습니다" has no 1:1 English equivalent. Context-dependent:

- End of meeting: `Thanks everyone!` / `Great session!`

- End of day: `Have a good evening!` / Japanese `お疲れ様でした`

- End of project: `Great work shipping this!` / `Massive props to the team`

13. Email - Greetings and sign-offs

| --- | --- | --- | --- |

13.1 Email body phrases

| Korean intent | English | 日本語 |

| --- | --- | --- |

| Got your email | I received your email — thank you. | メール拝受いたしました。 |

| Will look into it | I'll look into it and get back to you. | 確認のうえ、ご連絡差し上げます。 |

| Please find attached | Please find attached ... | 添付ファイルをご確認ください。 |

| Want to schedule | Could we find 30 min next week to discuss? | 来週中に 30 分ほどお打ち合わせのお時間をいただけますでしょうか。 |

| Sorry for late reply | Apologies for the delayed reply. | ご返信が遅くなり申し訳ございません。 |

14. Slack / chat abbreviations cheat sheet

The 2026 global IT Slack abbreviation standard is mostly locked in.

| --- | --- | --- | --- |

| `FYI` | For Your Information | "FYI" | ご参考まで |

| `TIL` | Today I Learned | "TIL" | 今日知った |

| `OOO` | Out Of Office | "PTO" | 不在 |

| `EOD` | End Of Day | "by today" | 本日中 |

| `EOW` | End Of Week | "by end of week" | 今週中 |

| `ETA` | Estimated Time of Arrival | "ETA" | 完了予定時刻 |

| `WIP` | Work In Progress | "WIP" | 作業中 |

| `MVP` | Minimum Viable Product | "MVP" | MVP |

| `POC` | Proof Of Concept | "POC" | PoC / 概念実証 |

| `NIT` | nitpick | "nit" | 細かい指摘 |

14.1 Emoji culture

- `:eyes:` 👀 — "I'm looking, response coming"

- `:pray:` 🙏 — request / thanks

- `:white_check_mark:` ✅ — done

- `:fire:` 🔥 — urgent or amazing (context-dependent)

- `:rocket:` 🚀 — deploy / launch

- `:bug:` 🐛 — bug report

- `:facepalm:` 🤦 — self-deprecating

Japanese Slack: `:bow:` (お辞儀) emoji handles both apology and thanks broadly.

15. Running a meeting - Agenda, action items, recap

Running meetings in Korean doesn't automatically transfer to English. A phrase kit is required.

15.1 Meeting facilitation phrases

| --- | --- | --- | --- |

15.2 What "parking lot" really means

"Let's put that in the parking lot" means "that topic is too big or off-topic — let's set it aside." Japanese: "保留" or "別途検討."

16. Interviewing - System design, behavioral STAR

Interview English is its own sub-genre. Two-way phrasing for being interviewer or candidate.

16.1 System design phrases

| Korean intent | English (formal) | English (casual) |

| --- | --- | --- |

| Let me clarify reqs | Let me clarify the requirements first. | Let me get the reqs straight first. |

| Throughput / latency | What's the expected throughput and latency budget? | What's the QPS and latency target? |

| Consistency vs availability | We'd trade strong consistency for availability here. | Eventual consistency works here. |

| Box-and-arrow first | I'll sketch the high-level components first. | Let me box-and-arrow this. |

| Trade-offs | The trade-off is X vs Y — I'd lean toward Y because ... | Trade-off: X vs Y, I'd pick Y because ... |

16.2 Behavioral - STAR

`STAR` = Situation / Task / Action / Result.

| Korean intent | English example |

| --- | --- |

| Situation | "Last year my team was facing a 30% error rate spike during checkout. (Situation)" |

| Task | "As tech lead, I owned both the triage and the long-term fix. (Task)" |

| Action | "I led a war room, ran a binary-search rollback, and identified a Redis key collision. (Action)" |

| Result | "Error rate dropped to 0.2% within 4 hours, and we shipped a postmortem with three preventative actions. (Result)" |

**Korean-speaker pitfall**: answering behavioral questions with "our team solved it together" makes it hard to evaluate you. Use **I** precisely. "I led ... while the team supported with ..."

17. Governance - RFC / ADR phrasing

Large technical decision documents. What matters is the **section keyword standard**.

17.1 RFC section vocabulary

| Section | English | 日本語 |

| --- | --- | --- |

| Motivation | Motivation | 動機 / 背景 |

| Goals | Goals | 目的 |

| Out-of-scope | Non-goals | 非目標 / スコープ外 |

| Proposal | Proposal | 提案 |

| Alternatives considered | Alternatives considered | 検討した代替案 |

| Trade-offs | Trade-offs | トレードオフ |

| Open questions | Open questions | 未解決の論点 |

| Decision | Decision | 決定事項 |

| Consequences | Consequences | 結果 |

17.2 Phrase table

| Korean intent | English |

| --- | --- |

| I'd like to propose | I'd like to propose adopting X for use case Y. |

| Stating non-goals | Non-goals: we're not addressing X in this RFC. |

| Open questions | Open question: how do we migrate the legacy data? |

| Decision deadline | Decision deadline: end of week. |

| Alternative A rejected | Alternative A was considered but rejected because of X. |

18. Postmortem - 5 Whys, lessons learned

Drafted within 24–72 hours after an incident. The vocabulary is almost ritualistically standardized.

18.1 Core vocabulary

| English | Korean | 日本語 |

| --- | --- | --- |

| Blameless postmortem | 비난 없는 포스트모템 | ブレームレス・ポストモーテム |

| Timeline | 타임라인 | タイムライン |

| Root cause | 근본 원인 | 根本原因 |

| Contributing factors | 기여 요인들 | 寄与要因 |

| 5 Whys | 다섯 번의 왜 | なぜなぜ分析 |

| Lessons learned | 배운 점 | 教訓 |

| Action items | 액션 아이템 | アクションアイテム |

| Detection time (TTD) | 탐지까지 시간 | 検知までの時間 |

| Mitigation time (TTM) | 완화까지 시간 | 緩和までの時間 |

| Recovery time (TTR) | 복구까지 시간 | 復旧までの時間 |

18.2 Phrase table

| Korean intent | English |

| --- | --- |

| No blame | This is a blameless postmortem — we focus on systems, not people. |

| Root cause | Root cause: a race condition in the connection pool when traffic exceeded 5k QPS. |

| Why detection was late | Our alert thresholds were tuned for the old traffic baseline and didn't trip. |

| Action items | Action 1: Add SLO-based alerts. Owner: @alice. Due: end of next sprint. |

19. Resigning / changing jobs - Graceful exit

| --- | --- | --- | --- | --- |

**Culture note**: in Japan, the standard notice period is 1–3 months, not 2 weeks. Korea is typically 1 month, US is 2 weeks. The biggest friction point when crossing global teams.

20. Negotiation - Promotion, salary, compensation

In manager negotiation meetings, the Korean "just take care of me, you know" approach fails in both English and Japanese cultures.

20.1 Phrase table

| --- | --- | --- | --- | --- |

**Term note**: **TC** = Total Compensation. Base + bonus + equity. In English-speaking IT negotiations, almost all numbers are TC-based.

21. Global meeting manners - Timezone, accents, repeat requests

| --- | --- | --- | --- |

21.1 Accents and ESL manners

- "I didn't understand" puts the gap on you. "Could you clarify?" shifts it to the speaker — more balanced.

- In Japanese meetings, "もう一度お願いします" is the safest catch-all.

- Voice-recognition captions (Zoom AI Companion, Otter, Granola) are 2026 standard in global teams. "I have captions on" at the start of a meeting is a non-issue.

22. Korean dev community case studies - Going English

22.1 Toss going English

Toss began rolling out English-language internal documents and Slack channels in 2023 to support global team expansion. Key assets:

- **Toss Tech Blog English edition** ([toss.tech](https://toss.tech/)) — Korean originals with English translations.

- Design system docs in English.

- Standardized English job descriptions on global hiring pages.

The lesson: English-ization isn't "translation" — it's "restructuring." Moving Korean docs verbatim feels off; English requires its own sentence length and paragraph structure.

22.2 Kakao / LINE English learning

Kakao runs internal English learning programs (1on1 English coaching, English PR-writing workshops). LINE operates with daily collaboration with the Tokyo HQ, giving it a Japanese + English bilingual baseline.

22.3 Korean-language IT English assets

- [Korean-English Translation Guide](https://github.com/translate-kr/style-guide) — style guide maintained by Korean translators for IT docs.

- Book: "개발자를 위한 영어" (Hanbit Media).

- Book: "직장인 영어회화 무작정 따라하기" (Gilbut).

- [Stack Overflow](https://stackoverflow.com/) — best place to see natural English technical phrasing in context.

23. Japanese dev community case studies - IT katakana mapping

23.1 Mercari English as official language

Mercari adopted English as its internal operating language in 2018. Effects:

- **Engineering blogs** ([mercan.mercari.com](https://mercan.mercari.com/), [engineering.mercari.com](https://engineering.mercari.com/)) — bilingual English/Japanese.

- 50%+ foreign engineer ratio.

- Meetings in English, Slack defaults to English.

Tokyo-anchored but globally toned. For Korean developers eyeing Japan, Mercari is an English-base entry point.

23.2 Core IT katakana vocabulary mapping

| English | Korean | カタカナ |

| --- | --- | --- |

| Deploy | 배포 | デプロイ |

| Rollback | 롤백 | ロールバック |

| Code review | 코드 리뷰 | コードレビュー |

| Pull request | PR | プルリクエスト / プルリク |

| Merge | 머지 | マージ |

| Refactor | 리팩터링 | リファクタリング |

| Repository | 저장소 | リポジトリ |

| Branch | 브랜치 | ブランチ |

| Commit | 커밋 | コミット |

| Issue | 이슈 | イシュー / 課題 |

| Sprint | 스프린트 | スプリント |

| Retro | 회고 | レトロ / ふりかえり |

| Standup | 스탠드업 | スタンドアップ / 朝会(あさかい) |

| 1on1 | 1대1 | ワンオンワン |

| Onboarding | 온보딩 | オンボーディング |

| Tech lead | 테크 리드 | テックリード / TL |

**Tip**: In Japanese IT, English-as-is is growing, but senior/SIer environments still favor kanji terms (障害 = incident, 復旧 = recovery) for trust signal. Switching fluidly between the two tones is the best move.

23.3 Japanese dev community

- [Qiita](https://qiita.com/) — Japan's largest developer blog platform.

- [Zenn](https://zenn.dev/) — modern Japanese developer community.

- Book: [WEB+DB PRESS](https://gihyo.jp/magazine/wdpress) (now ceased, but the back catalog is invaluable).

- LINE / DeNA / Yahoo Japan engineering blogs.

24. ESL tone calibration - "Less direct ≠ less effective"

For Korean developers, English tone calibration feels inefficient at first. "Why beat around the bush?" But the data shows polite forms are *faster*:

- **Aggressive code review** → author defensive → 5–10 back-and-forth comments → merge delayed 2 days

- **Polite code review** → author agrees → 1–2 comments → merge delayed 4 hours

Core principles:

1. **Critique the code, not the person** — `You did X wrong` → `This line does X, which leads to Y`

2. **Lead with curiosity** — `Why is this here?` → `Curious about the reasoning here — could you walk me through?`

3. **Own your limits** — A single `I might be missing context, but ...` keeps the other side off the defensive.

4. **Offer options** — `must do X` → `we could do X or Y; I'd lean toward X because Z`.

5. **Acknowledge fast** — When they make a good point, `Good point` / `Fair` in one word.

24.1 Anti-pattern words for Korean speakers

| Words to avoid | Why it backfires | Replacement |

| --- | --- | --- |

| `obviously` | "you should know this" tone | (omit) or `as you might know` |

| `simply` / `just` | trivializes, pressures | (most often omit) |

| `actually` | corrective tone | `in this case` |

| `should be easy` | pressuring | `if it's feasible` |

| `why don't you ...` | imperative | `would it be possible to ...` |

| `you need to ...` | imperative | `we'd benefit from ...ing` |

| `I think you misunderstood` | aggressive | `I might not have explained well — let me try again` |

25. Closing - The next 90 days

Repetition matters less than **real exposure**.

25.1 90-day plan

| Week | English | Japanese |

| --- | --- | --- |

| 1–2 | Rewrite the body of your last PR in English | Read one Mercari engineering blog post fully |

| 3–4 | Write 5 English code review comments | Try writing one Qiita post in Japanese |

| 5–6 | Take notes once in English in a meeting | Read one LINE engineering Japanese post |

| 7–8 | Draft one English RFC / ADR | Read one Japanese RFC |

| 9–10 | Watch + shadow one English conference talk | Watch a Japanese conference (Builderscon, etc.) |

| 11–12 | Simulate an English 1on1 | Simulate a Japanese 1on1 |

25.2 Recommended tools

- **DeepL** ([deepl.com](https://www.deepl.com/)) — most natural KO → EN/JA.

- **Grammarly** ([grammarly.com](https://www.grammarly.com/)) — English tone calibration.

- **Granola** ([granola.ai](https://www.granola.ai/)) — meeting captions + summaries.

- **HeyGen / Otter** — English pronunciation / English meeting notes.

References

1. [Google's Engineering Practices documentation - Code Review](https://google.github.io/eng-practices/review/)

2. [Conventional Commits specification](https://www.conventionalcommits.org/)

3. [The Pragmatic Engineer Newsletter](https://newsletter.pragmaticengineer.com/) - global developer culture case studies.

4. [Atlassian Incident Management handbook](https://www.atlassian.com/incident-management)

5. [GitLab Handbook - Communication](https://handbook.gitlab.com/handbook/communication/) - the most async-English-first company case.

6. [Lara Hogan - Resilient Management](https://larahogan.me/) - 1on1, feedback, manager phrasing standards.

7. [Stripe Press](https://press.stripe.com/) - English business writing exemplars.

8. [Mercari Engineering Blog](https://engineering.mercari.com/) - English-as-official-language case in Japan.

9. [LINE Engineering](https://engineering.linecorp.com/) - JA / KO bilingual environment.

10. [Toss Tech](https://toss.tech/) - bilingual KO/EN blog case.

11. [Qiita](https://qiita.com/) - Japanese dev blog standard.

12. [Zenn](https://zenn.dev/) - modern Japanese dev community.

13. [Etsy Code as Craft - Blameless postmortems](https://www.etsy.com/codeascraft/blameless-postmortems/) - the original blameless writeup.

14. [Google SRE Book - Postmortem Culture](https://sre.google/sre-book/postmortem-culture/)

15. [Increment Magazine - On-Call issue](https://increment.com/on-call/)

16. [SmartHR Tech Blog](https://tech.smarthr.jp/) - Japanese dev writing standard.

17. [Cookpad Engineering](https://techlife.cookpad.com/) - Japanese English-ization case.

18. [Engoo Blog](https://engoo.com/blog/category/all-tips/) - common English mistakes by Korean speakers.

19. [Daniel Stenberg - Working in Open Source](https://daniel.haxx.se/blog/) - PR / issue English at its purest.

20. [Will Larson - Staff Engineer](https://staffeng.com/) - senior-and-above engineer phrasing / RFC culture.

21. [The Manager's Path - Camille Fournier](https://www.oreilly.com/library/view/the-managers-path/9781491973882/) - 1on1 phrase collection.

22. [Crucial Conversations book](https://cruciallearning.com/crucial-conversations-book/) - English phrasing for hard conversations.

23. [Hanbit Media - 개발자를 위한 영어](https://www.hanbit.co.kr/) - IT English guide for Korean speakers.

24. [Spotify Engineering](https://engineering.atspotify.com/) - English phrasing + engineering culture.

Final note: the most important realization for Korean developers is that "you can signal great work even when English / Japanese is imperfect." Carrying the impact of your work into the other language is a bigger asset than memorizing perfect phrases.