사람이 쓴 글

The line not to cross when AI writes your application

What must never be invented and what may be proposed are different things. How to write that boundary into the request.

이 가이드는 영어로 쓰였습니다. 한국어판 읽기

What makes this hard

A cover letter or personal statement carries two opposing demands at once: nothing fabricated, yet persuasive with the material you have. If the request doesn't set that balance, AI collapses to one side.

Each collapse looks like this. The fabricating side: projects you never ran, awards you never won, numbers you never produced blend in naturally — one interview question about that sentence ends everything. The over-cautious side: a skeleton where every line reads [fill in: achievement metric] — after you fill it all in, you've written it yourself anyway.

What can't be invented vs. what may be proposed

This distinction is the core. Factual claims can't be invented — but intent and direction are not factual claims.

Never invented — company names, job titles, employment dates, awards, performance numbers. If it's not in the material you provided, it must not be in the text
Fine to propose — post-hire goals, how to phrase a reason for leaving, career direction. These are your views, not facts, and editing a draft beats starting from blank

Write the distinction into the request and AI treats the two differently — the former stays blank, the latter comes as a proposed draft with a request for your confirmation.

Put it like this

Use only the experience and numbers I gave you — invent nothing. But for things I need to decide, like post-hire goals or motivation, don't leave blanks: propose a draft and ask me to confirm.

The structure for writing one experience

Listing experiences leaves the reader unsure what to look at. Make it write situation → action → result, and each paragraph becomes one piece of evidence.

Situation — what was the problem. Don't spend long explaining company context here
Action — what did *I* do. Not 'our team' — 'I'
Result — what changed. With numbers if you have them; without, if you don't

Write experiences without numbers too. Saying there is no number is safer than making one up — the goal of this document is to leave only sentences you can defend when an interviewer asks.

Checklist for writing it yourself

1Did you paste the job posting's required skills into the request — without them you get generic prose
2Are the achievement numbers copied verbatim from your own material
3Did you state the per-question length limits
4Did you write both 'invent nothing' and 'propose the aspirational parts' — one without the other collapses to a side

읽었으면 직접 해 보는 편이 빠릅니다.

지금 만들어 보기