Skip to content
Published on

IT転職のための英語:Tech Resume & Cover Letter 完全作成ガイド

Authors
  • Name
    Twitter

1. Tech Resumeの基本原則

1.1 日本の履歴書 vs 英文Resume

項目日本の履歴書英文Tech Resume
分量自由1~2ページ厳守
写真必須絶対禁止(差別防止)
生年月日記載禁止
学歴順時系列逆時系列(最新順)
トーン謙虚/受動的能動的/成果重視
GPA常に記載3.5以上の場合のみ

1.2 ATS(Applicant Tracking System)対策

ほとんどのグローバル企業はATSで履歴書を自動フィルタリングします:

DO:
- プレーンテキストまたはシンプルなPDF
- JD(Job Description)のキーワードを自然に含める
- 標準セクション見出しを使用(Experience、Education、Skills)
- 測定可能な成果(数字!)

DON'T:
- 複雑な表、グラフ、画像
- ヘッダー/フッターに重要情報を配置
- 略語のみの使用(ATSが認識できない場合がある)
"Kubernetes (K8s)" のようにフルネーム+略語を併記

2. Resume セクション別の書き方

2.1 Contact Information

Youngju Kim
Seoul, South Korea | youngju@email.com | +82-10-XXXX-XXXX
LinkedIn: linkedin.com/in/youngjukim | GitHub: github.com/fjvbn2003

注意:住所は都市/国のみ。詳細な住所は不要です。

2.2 Professional Summary(任意)

経験3年以上の場合、2~3行で要約:

Bad:
"I am a hardworking software engineer looking for opportunities."

Good:
"Platform Engineer with 4+ years of experience building and scaling
Kubernetes-based AI/ML infrastructure. Led migration of 200+ services
to cloud-native architecture, reducing deployment time by 73%.
Certified Kubernetes Administrator (CKA) with expertise in GitOps,
observability, and GPU workload management."

2.3 Experience — STAR + Action Verbs

STAR手法:Situation → Task → Action → Result

Bad:
"Was responsible for Kubernetes cluster management."

Good:
"Architected and maintained 15-node Kubernetes cluster serving
50+ microservices, achieving 99.95% uptime and reducing infrastructure
costs by 32% through right-sizing and spot instance optimization."

必須Action Verbs 50選:

カテゴリVerbs
構築Architected, Built, Designed, Developed, Engineered, Implemented
改善Optimized, Improved, Enhanced, Streamlined, Accelerated, Revamped
リーダーシップLed, Managed, Directed, Coordinated, Mentored, Spearheaded
分析Analyzed, Evaluated, Assessed, Investigated, Diagnosed, Identified
デプロイDeployed, Automated, Configured, Provisioned, Orchestrated, Migrated

2.4 Experience 記載例(シニア)

**Senior Platform Engineer** | Upstage AI | Seoul, Korea
_March 2024 – Present_

• Architected multi-tenant Kubernetes platform serving 30+ ML teams,
processing 500K+ inference requests/day with p99 latency < 200ms
• Designed and implemented GitOps pipeline using ArgoCD and Helm,
reducing deployment frequency from weekly to 15+ deploys/day
• Built GPU scheduling system with NVIDIA GPU Operator and MIG,
improving GPU utilization from 35% to 78% across 40+ A100 nodes
• Developed comprehensive observability stack (Prometheus, Grafana,
Loki, Tempo) reducing MTTR from 45min to 8min
• Mentored team of 5 junior engineers on cloud-native best practices

2.5 Skills セクション

**Technical Skills**
• Infrastructure: Kubernetes, Docker, Terraform, Ansible, Helm, ArgoCD
• Cloud: AWS (EKS, EC2, S3, Lambda), GCP (GKE)
• Observability: Prometheus, Grafana, Loki, Tempo, OpenTelemetry
• Languages: Python, Go, Bash, TypeScript
• AI/ML: vLLM, TensorRT-LLM, Ray, MLflow, NVIDIA Triton
• Databases: PostgreSQL, Redis, Qdrant, Elasticsearch
• Certifications: CKA, CKS, KCNA, AWS SAA

2.6 Education

**B.S. in Computer Science** | Korea University | 2016 – 2020
• GPA: 3.8/4.5 (only include if > 3.5)
• Relevant Coursework: Distributed Systems, Machine Learning, OS

3. Cover Letterの書き方

3.1 構成(4段落)

Paragraph 1: フック+応募ポジション明記
Paragraph 2: 最も関連性の高い経験12件(具体的な成果)
Paragraph 3: なぜこの会社なのか(リサーチ必須!)
Paragraph 4: Call to Action

3.2 実践テンプレート

Dear Hiring Manager,

I'm excited to apply for the Senior Platform Engineer position at
[Company]. With 4+ years of experience building Kubernetes-based
AI infrastructure and a track record of improving system reliability
from 99.5% to 99.95% uptime, I'm confident I can contribute
meaningfully to your platform team.

At Upstage AI, I architected a multi-tenant Kubernetes platform that
serves 30+ ML teams with 500K+ daily inference requests. I designed
the GitOps pipeline that increased deployment frequency by 15x and
built the GPU scheduling system that improved utilization from 35%
to 78%. These experiences directly align with your team's mission
to scale AI infrastructure efficiently.

What particularly excites me about [Company] is [specific project/
product/value from research]. Your recent work on [specific thing]
resonates with my passion for [relevant area], and I'd love to
bring my experience in [specific skill] to help advance these efforts.

I'd welcome the opportunity to discuss how my background can
contribute to your team. Thank you for your consideration.

Best regards,
Youngju Kim

4. 重要英語表現集

4.1 成果の表現

Reduced [metric] by X% through [action]
Increased [metric] from X to Y by implementing [solution]
Delivered [project] ahead of schedule, resulting in $XK savings
Eliminated [problem] that had caused X hours/week of downtime
Scaled [system] from X to Y users while maintaining Z performance

4.2 技術力の表現

Proficient in / Experienced with / Expert in
Hands-on experience building [systems] at scale
Deep understanding of [concept] and its practical applications
Track record of delivering [type] solutions in production environments

4.3 避けるべき表現

"I think I can...""I will..." / "I am confident..."
"I helped with...""I led..." / "I drove..."
"Responsible for...""Owned..." / "Spearheaded..."
"Team player" → (具体的な協業事例で示す)
"Detail-oriented" → (具体的な品質改善の数値で示す)

5. LinkedIn最適化

5.1 Headline公式

Bad: "Software Engineer at Company"
Good: "Platform Engineer | Kubernetes • AI/ML Infrastructure • GitOps | CKA/CKS"

5.2 About セクション

I build and scale the infrastructure that powers AI.

As a Platform Engineer at Upstage AI, I architect Kubernetes-based
systems that serve 500K+ daily inference requests with 99.95% uptime.
My focus areas include:

Cloud-native infrastructure (Kubernetes, Terraform, ArgoCD)
AI/ML platform engineering (GPU scheduling, model serving)
Observability at scale (Prometheus, Grafana, OpenTelemetry)

Previously, I [brief prior experience]. I hold CKA, CKS, and KCNA
certifications and am working toward Golden Kubestronaut.

Open to connecting with fellow platform engineers and AI infrastructure
builders. Let's chat!

6. クイズ

Q1. ATSとは何か、なぜ重要か?

Applicant Tracking System — 履歴書を自動フィルタリングするソフトウェア。大企業の75%以上が使用。キーワードマッチングに失敗すると、人間が見る前に不採用になる。

Q2. "Responsible for Kubernetes management" をAction Verbで改善すると?

"Architected and maintained 15-node Kubernetes cluster serving 50+ microservices, achieving 99.95% uptime"

Q3. STAR手法の4要素は?

Situation(状況)→ Task(課題)→ Action(行動)→ Result(結果、できれば定量的に)

Q4. 英文Resumeに写真を入れてはいけない理由は?

アメリカ・ヨーロッパのほとんどの国で差別防止法があるため。写真付き履歴書は即不採用にする企業もある。

Q5. Cover Letterで "Why this company?" を書く理由は?

応募者が会社をリサーチしたことを示すため。その会社ならではの製品・文化・プロジェクトを具体的に言及することで、本気度が伝わる。

Q6. "I am a team player and detail-oriented" がダメな表現である理由は?

抽象的で証明不可能。代わりに具体的な事例で示すべき:「Coordinated cross-team migration involving 5 teams and 200+ services」→ これがチームプレーヤーであることの証拠になる。

Q7. LinkedIn Headlineの最適な構成は?

「職種 | コア技術1 • コア技術2 • コア技術3 | 資格/差別化ポイント」— 検索キーワードを最大限含みつつ自然に。