Video summary
모든 합격 자소서 첫줄의 공통점 & 최고의 경험으로도 탈락하는 실수 feat. 서울특별시 [잡담캠프 하이라이트]
Main summary
Key takeaways
Main ideas / lessons conveyed
-
Personal statements aren’t “easy”: Even if they look straightforward at first glance, they’re often the hardest part of the application.
-
Avoid common rejection patterns by following “what not to do” guidance:
- Don’t rely on vague intuition or impression-based evaluation.
- Don’t use a narrative format that buries the point until the end (e.g., a beginning–middle–end story where the main message appears last).
- Don’t write strengths that don’t connect to the specific job and company you’re applying for.
-
Use a structure that shows value immediately:
- Instead of storytelling that ends with conclusions, start with results/achievements, then explain the situation and actions that produced them.
- If you’re constrained by time/length, it’s acceptable to write only:
- your achievements/results, and
- the actions that led to them. The interviewer can ask follow-ups during the interview.
-
Strengths must be linked to the job:
- Yes, it’s natural to highlight strengths—but the key is finding a “connecting link” to the target position.
- Even impressive claims (e.g., graduating top of the class) can be low value if the job has no meaningful connection to the knowledge/skills implied.
- The “importance” of credentials depends on fit:
- In some fields (example given: humanities), “top of class” may matter less because it doesn’t directly translate into job-relevant knowledge.
- In other fields (example given: where knowledge is applied immediately), it can be highly relevant.
-
If your background seems unrelated, you must bridge the gap:
- Example approach discussed: even with a master’s in Political Science & Diplomacy (not directly related to the role), you can make it relevant by emphasizing how you extracted insights from many articles/literature and used that process for problem-solving, especially if applying for a staff role.
- Lesson: if you clearly connect your education/accomplishments to job-relevant work, it stops being mere bragging and becomes a genuine strength.
-
STAR method guidance for structure:
- The speaker references using STAR:
- Situation
- Task
- Action
- Result (called “LET” in the subtitles—likely the same concept/order used by the channel)
- Implementation emphasis:
- Write results first (per the earlier instruction to lead with achievements).
- Then describe Situation/Task/Action and the resulting effects.
- Use this standard not just inside the narrative, but also for how you divide paragraphs.
- The speaker references using STAR:
-
Weighting content: prioritize Action:
- The subtitles mention a “255%” repetition that appears to indicate emphasis/weighting:
- give the most weight to the Action section.
- Rationale given:
- Situation and Task are influenced/defined by the external environment (often “given”).
- The differentiator is showing what you did and how.
- The subtitles mention a “255%” repetition that appears to indicate emphasis/weighting:
Method / instruction checklist
-
Before writing: decide what you should not do
- Don’t bury your main point at the end of the story (avoid “beginning–middle–end” with conclusions last).
- Don’t present accomplishments without linking them to what the company/job actually needs.
- Don’t make the evaluation rely on impression/intution; structure your writing so it’s clearly evaluable.
-
Core writing order
- Start with Results/Achievements (lead with what you achieved).
- Then describe:
- Situation/Context (what circumstances you faced)
- Actions you took
- Effects/Outcomes (what happened as a result)
- If short on time/space: write only Achievements + Actions.
-
Strengths selection rule
- Highlight strengths only when there is a clear connection to the target position.
- Avoid spending too much space on credentials the role can’t leverage.
-
STAR / paragraph-structure approach
- Use STAR as the organizing framework:
- Situation → Task → Action → Result
- Apply it consistently to paragraph division (not just the overall story).
- Ensure results/achievements appear early, aligned with the “results first” rule.
- Use STAR as the organizing framework:
-
Content emphasis
- Give the largest emphasis to Action.
- Treat Situation/Task as supporting context; evaluation focuses heavily on decision-making and execution.
Speakers / sources featured
- Manager (interviewer/host figure)
- Senior interviewers (referenced generally)
- Jacob (name mentioned)
- Hansang (name mentioned)
- [Music] (background audio cue)