☰ 분류

이력서 경력 프로필 변환 프롬프트

이력서 텍스트를 넣으면 파일명 코드블록과 표준화된 경력 프로필 보고서 코드블록으로 구조화해 주며, 누락 정보는 명시적으로 표시합니다.

분류취업 › 이력서·경력기술서
태그형식변환분석취준생템플릿
프롬프트 (영어 본문 · 답은 한국어로 옵니다)
# TITLE: Career Profile from Resume Builder
# VERSION: 1.1.3
# AUTHOR: Scott M
# LAST UPDATED: 2026-05-21
#
# CHANGELOG:
# · v1.1.3 (2026-05-21): Added filename normalization rules (no suffixes/certs, spaces to underscores) and strictly banned conversational filler between codeblocks.
# · v1.1.2 (2026-05-21): Isolated the suggested filename into its own independent codeblock at the start of output.
# · v1.1.1 (2026-05-21): Added standardized file naming convention output block before the main report.
# · v1.1.0 (2026-05-21): Added RESUME FORMAT & STRUCTURE AUDIT to catch ATS parsing risks and layout issues.
# · v1.0.1 (2026-05-21): Hardened PROFESSIONAL SUMMARY block to favor direct extraction and minimize semantic drift.
# · v1.0.0 (2026-05-21): Initial release. Canonical profile normalization and basic gap analysis.

============================================================
PROMPT PURPOSE
============================================================
Convert a user-provided resume into a structured, standardized career profile.

This is a NON-INTERACTIVE transformation tool:
· Do not ask questions
· Do not conduct interviews
· Do not request clarification
· Do not iterate with the user

Input → Resume text  
Output → Filename Codeblock + Main Profile Report Codeblock (No conversational filler)

============================================================
CORE BEHAVIOR
============================================================
Act as a precise career data normalizer.

Your job is to:
· Extract structured career data from resumes
· Standardize formatting into a consistent profile schema
· Preserve all factual information without rewriting intent
· Identify missing or unclear information as gaps only
· Avoid any assumptions or fabrication

If information is missing:
· Mark explicitly as [NOT PROVIDED]
· Do not infer or guess

============================================================
FORMATTING RULES
============================================================
· Use middle dot ( · ) for all bullet lists
· Output must contain exactly two Markdown codeblocks and ZERO conversational text or intro/outro sentences before, between, or after them
· Keep structure clean and hierarchical
· Do not use emojis or embellishment

============================================================
DATA NORMALIZATION RULES
============================================================
· Dates → "MMM YYYY – MMM YYYY" or "Present"
· Roles → "[Title] – [Company], [Dates]"
· Skills → only explicitly stated skills
· Tools → only explicitly stated tools
· Experience duration → only if explicitly stated
· Filename Extraction → Remove any professional suffixes or certifications (e.g., CISSP, CEH, MBA). Convert all spaces to underscores. Format must be exactly: Career_Profile_[First_Last].md

============================================================
OUTPUT STRUCTURE
============================================================
When processing is complete, output exactly two codeblocks in this sequence with no text surrounding or dividing them:

[START FILENAME CODEBLOCK]
Career_Profile_[Normalized_First_Last].md
[END FILENAME CODEBLOCK]

[START REPORT CODEBLOCK]
Career Profile from Resume (Canonical Record)

USER JOB TARGET (if stated in resume):
· [or: NOT PROVIDED]

PROFESSIONAL SUMMARY:
· [Direct extraction of the existing summary. If no summary exists, synthesize a 2-sentence overview using only exact nouns and metrics from the history.]

JOB HISTORY (Recent First):
[Repeat the following block for each role found in the resume]
· Role: [Title] – [Company], [Dates]
  · Responsibilities:
  · Achievements:
  · Tools/Technologies:
  · Notes: [only factual extraction]

TECHNICAL SKILLS:
· [Skill list from resume only]

CERTIFICATIONS:
· [List or NOT PROVIDED]

EDUCATION:
· [List or NOT PROVIDED]

PROJECTS:
· [Only if explicitly present]

GAPS & MISSING INFORMATION:
· Metrics missing (impact, %, $, scale)
· Tool durations missing or unclear
· Timeline ambiguity present / not present
· Scope unclear (team size, systems, environment)
· STAR stories absent (if not present)

RESUME FORMAT & STRUCTURE AUDIT:
· ATS Parsing Risks: [Identify heavy tables, text boxes, headers/footers, or non-standard fonts that will break ATS]
· Hierarchy & Layout: [Report if section headers are non-standard, disorganized, or hard to scan]
· Formatting Consistency: [Flag mixed date formats, irregular bullet types, or sloppy alignment]

IMPORTANT NOTES:
· This profile is a structured transformation of provided resume content only
· No external enhancement has been applied
[END REPORT CODEBLOCK]

============================================================
INPUT DATA
============================================================
[PASTE RESUME BELOW THIS LINE]

어떤 프롬프트인가

이력서를 일관된 경력 데이터 스키마로 정규화할 때 쓰기 좋다. 질문이나 대화 없이 정확히 두 개의 Markdown 코드블록만 출력하도록 제한한다.

모델 비교

Claude가 형식·구체성 면에서 가장 우수하다. Gemini는 과잉 해석이 많고, ChatGPT는 간결하지만 한국어 지시 위반이 크다.

Claude종합 1위
43/ 50

+ 원문 지표를 충실히 보존하고 누락 사항을 구체적으로 짚었다.

- 연락처를 직무 메모에 넣고 불필요한 번역과 추론을 덧붙였다.

ChatGPT
39/ 50

+ 원문 중심의 간결한 추출로 사실 왜곡을 최소화했다.

- 한국어 응답 지시를 어겼고 날짜 형식 불일치를 놓쳤다.

Gemini
37/ 50

+ 직무별 책임·성과와 형식상 문제를 체계적으로 정리했다.

- 이름 순서와 직무 목표가 부정확하며 원문에 없는 표현을 보탰다.

기준ChatGPTClaudeGemini앞선 모델
지시 준수597Claude +29%
정확성886동점
구체성898Claude +13%
구성·가독성999동점
분량 적정성987ChatGPT +13%

gpt-5.6-sol가 모델 이름을 가린 채 1~10점으로 채점했습니다 (2026-09-24). 측정값이 아니라 AI 심사 결과입니다.

답 전문 보기

같은 입력을 세 모델에 넣어 받은 답을 그대로 옮겼습니다. 각 CLI(에이전트 하네스)에서 실행했습니다. ChatGPT·Claude 앱이나 웹에서는 답이 다를 수 있습니다.

넣은 입력
[붙여 넣은 자료]
Kim Doyeon
Backend Developer | Seoul, South Korea | doyeon.kim.dev@gmail.com | 010-2456-7891

Backend developer with 5 years of experience building scalable APIs and payment systems for e-commerce platforms.

Experience

Backend Developer – ByteWave Commerce, Mar 2022 – Present
- Rebuilt the order processing service using Spring Boot and Kafka, cutting average checkout latency from 800ms to 210ms
- Own the payments microservice handling roughly 3M transactions per month
- Introduced canary deployments for the core API, reducing rollback incidents

Software Engineer – NovaLine Games, Jul 2019 – Feb 2022
- Built RESTful APIs for the in-game item shop
- Migrated the legacy MySQL schema to support sharding as the user base grew past 1M MAU
- Worked with the QA team to set up automated regression tests

Skills
Java, Kotlin, Spring Boot, MySQL, Redis, Kafka, AWS (EC2, RDS, S3), Docker, Kubernetes

Education
B.S. in Computer Science, Konkuk University, 2015 – 2019

Certifications
AWS Certified Solutions Architect – Associate (2023)
gpt-5.6-luna (codex CLI · 에이전트 하네스) · 실행일 2026-09-24
Career_Profile_Kim_Doyeon.md
Career Profile from Resume (Canonical Record)

USER JOB TARGET (if stated in resume):
· Backend Developer

PROFESSIONAL SUMMARY:
· Backend developer with 5 years of experience building scalable APIs and payment systems for e-commerce platforms.

JOB HISTORY (Recent First):
· Role: Backend Developer – ByteWave Commerce, Mar 2022 – Present
  · Responsibilities:
    · Own the payments microservice handling roughly 3M transactions per month
  · Achievements:
    · Rebuilt the order processing service using Spring Boot and Kafka, cutting average checkout latency from 800ms to 210ms
    · Introduced canary deployments for the core API, reducing rollback incidents
  · Tools/Technologies:
    · Spring Boot, Kafka
  · Notes:
    · Seoul, South Korea

· Role: Software Engineer – NovaLine Games, Jul 2019 – Feb 2022
  · Responsibilities:
    · Built RESTful APIs for the in-game item shop
    · Worked with the QA team to set up automated regression tests
  · Achievements:
    · Migrated the legacy MySQL schema to support sharding as the user base grew past 1M MAU
  · Tools/Technologies:
    · MySQL
  · Notes:
    · [NOT PROVIDED]

TECHNICAL SKILLS:
· Java
· Kotlin
· Spring Boot
· MySQL
· Redis
· Kafka
· AWS (EC2, RDS, S3)
· Docker
· Kubernetes

CERTIFICATIONS:
· AWS Certified Solutions Architect – Associate (2023)

EDUCATION:
· B.S. in Computer Science, Konkuk University, 2015 – 2019

PROJECTS:
· [NOT PROVIDED]

GAPS & MISSING INFORMATION:
· Metrics missing: rollback incident reduction percentage and broader impact metrics
· Tool durations missing or unclear
· Timeline ambiguity not present
· Scope unclear: team size, systems, and environment
· STAR stories absent

RESUME FORMAT & STRUCTURE AUDIT:
· ATS Parsing Risks: No heavy tables, text boxes, headers/footers, or non-standard fonts identified in the provided text
· Hierarchy & Layout: Standard section headers and clear reverse-chronological experience structure
· Formatting Consistency: Date formats are generally consistent; bullet formatting is consistent in the provided text

IMPORTANT NOTES:
· This profile is a structured transformation of provided resume content only
· No external enhancement has been applied

같은 분류의 프롬프트

입사지원서 검토 프롬프트
이력서 검토자 역할을 맡기는 프롬프트
Anthropic Fellows 이력서 검토 프롬프트
ATS 이력서 스캐너 프롬프트
커리어 코치 역할 프롬프트