Toss Payments Systems Engineer Resume Review

# Toss Payments Systems Engineer Resume Review

AI Summary

Purpose:

• Record the content and visual review of the existing Toss Payments Systems

Engineer ATS resume without copying the personal PDF into the wiki repository.

Key points:

• Source path: /Users/khw/Downloads/김현욱_토스페이먼츠_Systems_Engineer_ATS_이력서 (2).pdf.
• The PDF has two clean, readable pages and no visible clipping, overlap, broken

glyphs, or layout defects.

• Page 1 is a Systems Engineer summary plus experience bullets; page 2 expands

the AWS/general-purpose-PC to IDC migration and the 2-node to 6-node hybrid Kubernetes expansion.

• Strong reusable evidence for a Data Engineer application includes more than 80

crawlers, Airflow/KubernetesExecutor operations, DML Broker, database error reduction, monitoring, storage, backup, and platform ownership boundaries.

• For the Toss Payments Data Engineer version, replace the AWS/PC migration case

with data-quality, missing-data recovery, reconciliation, or CDC evidence.

Relevant when:

• Converting the Systems Engineer resume into a Toss Payments Data Engineer resume.
• Reusing the existing visual layout for a new targeted PDF.

Do not read full document unless:

• Deciding which existing sections to keep, remove, or reorder.

Linked documents:

• ../../wiki/projects/2026-career-transition.md
• ../../wiki/projects/data-platform-systems-engineering.md
• ../../wiki/projects/bts.md
• ../../../human/resume/toss-payments-data-engineer/resume-draft.md

Open Questions

• Editable source file for the existing PDF is not in this repository.
• Exact CDC deployment start date remains unknown. Role ownership was clarified on

2026-07-16: Hyunwook designed and implemented the system and completed scenario review; the technical-support team performs customer deployment and day-to-day operation, while Hyunwook improves issues reported from operation.

• Confirm whether the phone number should remain in the public/application PDF.

Details

Visual review:

• Two-page A4-like ATS layout with a single blue accent color.
• Page 1 hierarchy is clear: identity, summary, experience, skills.
• Page 2 uses two large problem-improvement cases plus smaller operating improvements.
• Text density is high but still readable at the rendered resolution.

Recommended Data Engineer transformation:

1. Change the headline from on-premise Systems Engineer to Kubernetes/Airflow

Data Platform Engineer.

1. Keep the hybrid Kubernetes capacity case, but frame it as batch-workload

reliability rather than infrastructure expansion alone.

1. Promote DML Broker and 80+ crawler platform evidence.
2. Add SQL/index optimization and missing-data reconciliation evidence.
3. Keep Spark/Kafka/Flink out unless their actual experience level is verified.
4. Add CDC only after confirming design/PoC/pilot/production status.