How to Write a Resume When You Feel Like You've Done Nothing

If you feel like you have no idea what to put on your resume because you feel like you didn’t achieve anything significant or you didn’t contribute much to projects, let me show you an easy trick to make your application sound 10x stronger.

Most advice will tell you to write your resume in the STAR (situation, task, action, result) or PREP (point, reason, example, point) format, but even though this is great, I recommend the extended STAR-L format, where “L” stands specifically for lesson.

Basically, this is one of the better strategies if you didn’t achieve big business metrics or you don’t know specifically know what numbers to put.

Let me show you why this works.

Imagine two people apply for the same marketing job. The first applicant has written, "Launched content marketing strategy for a XYZ brand" The second one writes, "Launched a content marketing strategy while applying key learnings from early A/B testing data in TikTok Ads Manager to isolate top-performing creatives and optimize ad spend for next campaigns."

Which one would you hire? The second applicant was much more specific about their experience and also demonstrated iteration and growth despite not having significant business achievements.

It’s even better if you’re able to write the experience statements in a way where the lessons tie them back to the job description. For example, if the job position required TikTok business fluency, then the lesson itself regarding using TikTok Ads manager and A/B testing would have been a valuable match, even though there weren’t significant business achievements.

Let me show you a couple more examples in both English and Korean, and I’ll focus more on the lessons than the business results themselves, to show you that you don’t need to always have impressive results.

Example 1: A university group project

Situation: Joined a group project. 

Task: Build the final presentation with 4 other students.

Action: Became the project leader and divided the work into clear parts.

Lesson: We almost missed the deadline because we never agreed on who owned what. I learned to set clear roles on day one, and I've done that on every team since.

How to tie it back to the job description: If the JD was a project/product managerial position at a SME,  you mention how you integrated XYZ tool (for example, something like Notion, Jira, some other tool mentioned in the JD) to track responsibilities and tasks, instead of overloading team members with everything.

Korean: 팀 프로젝트 리더를 맡아 팀원 4명에게 업무를 나누는 과정에서, 역할과 책임이 명확하지 않아 마감이 늦어질 뻔한 위기를 겪었습니다. 이후 Jira, Notion 등등을 도입해 역할을 트래킹하는 시스템를 만들었고, 무엇보다 처음부터 R&R (roles and responsbilities)을 분명히 하는 것이 중요하다는 걸 배웠습니다.

Situation:  Hard it is to make local Korean friends as a foreigner

Task: Created "vibe-coded" coffee chat app to connect expats and locals at local cafes

Action: Built a prototype using Claude and getting 30 friends to sign up

Lesson: Assumed people wanted to match for coffee chat, but quickly learned that people wanted to match instead for dating potential. Important to always test my assumptions with real users before building a full product.

How to tie it back to the job description: If this JD was a developer, marketing, or design position at a startup, you mention how it’s important to gather early user feedback to test assumptions before developing a product nobody wants to use, and you utilized some XYZ tool (specific to the JD, for example, ) to do early analysis.

Korean: Claude로 외국인 매칭 커피챗 앱 프로토타입을 만들고 친구, 가족 30명을 대상으로 유저 테스트를 실행했습니다. 그 과정에서 초기 가설이었던 친목과 실제 유저가 원한 데이팅 사이의 차이를 발견했고, 제품을 본격적으로 개발하기 전에 XYZ 툴을 사용하며 유저 피드백으로 가설을 먼저 검증하는 것이 중요한지 배웠습니다.

You were never behind because you’re not impressive enough. You were behind because nobody showed you how to translate your advantages into a stronger application.

If you want the full guide, including my exact resume templates, check out Korea Career OS below!