Writing (쓰기)
What this domain tests
The writing section moves from controlled tasks (completing a sentence with the correct connective or honorific form) to practical writing - an email, a notice, a short self-introduction - and finally a 200–300자 paragraph arguing or explaining a given topic. Markers reward task fulfilment, paragraph structure, accurate honorifics and correct 띄어쓰기 as much as ambitious vocabulary.
Core rules
- Style: formal tasks take 습니다체 throughout. Never mix 습니다체 with 해요체 in one text.
- Structure: 서론 (state the topic) – 본론 (two supporting reasons with examples) – 결론 (restate the position). One idea per paragraph.
- Connectors: -기 때문에, -므로, -는 반면에, -뿐만 아니라, -도록, -기에 suitable for written prose. Avoid conversational items such as 진짜, 되게, -거든요, -잖아요.
- Honorific consistency: if the reader is an institution or an elder, keep -시- and 격식체 addresses (귀 기관, 선생님) throughout.
Worked example
Task: write a short email asking a 담당자 to confirm a document deadline. Weak version: "빨리 답장해 주세요. 저는 시간이 없어요." Strong version: "바쁘시겠지만 5월 10일까지 회신해 주시면 감사하겠습니다." Reasoning: the strong version uses the honorific -시- for the reader, softens the request with -겠-, sets a concrete date, and closes with a formulaic 감사하겠습니다 - all of which markers look for in practical writing.
Traps that cost marks
- Exceeding or falling far short of the required character count.
- Writing a list of sentences with no 결론, so the position is never stated.
- Correct grammar but wrong register, for example -해요 in a 공지문.