A Resume Guide from a CTO Who Has Reviewed 10,000 Resumes

This is a practical resume writing strategy lecture shared directly by a Technical Director who has reviewed over 10,000 resumes. There is no such thing as a "guaranteed pass template" or a "must-pass formula" in this world. I will show you the perspective of a document reviewer—how they read resumes, what they focus on, and what makes them feel fatigued. A resume is not a subject for memorization. The core of this lecture is understanding the process itself of properly organizing and expressing who you are. Whether you are an experienced professional or a newcomer, this lecture will be helpful for any developer who has ever struggled with their resume.

(5.0) 100 reviews

929 learners

Level Beginner

Course period Unlimited

Interview
Interview
Resume
Resume
Tech Interview
Tech Interview
get a job
get a job
Interview
Interview
Resume
Resume
Tech Interview
Tech Interview
get a job
get a job

Reviews from Early Learners

5.0

5.0

CCTH

95% enrolled

To be honest, before taking this course, I thought of a resume as just a "document that lists the things I've done." However, after finishing the course, I reflected a lot on how I had been writing my resume completely wrong. While listening to the lectures, my standards for "how to write about projects" changed entirely. (It's difficult to mention the specific content of the lecture directly, but) I was able to get a feel for what context and criteria should be used to organize the content, rather than simply listing tech stacks or numbers. The most impressive part was the section that compared an actual resume before and after the advice. Seeing firsthand how the delivery can change so much depending on how the same experience is explained made the vague standards much clearer, and I was able to apply it to my resume immediately. I completely rewrote my resume right after the course, and the result was a totally different document from before. I felt like I had finally written a "proper resume." Above all, I was very satisfied because it wasn't just simple theory, but a course that sets a direction from the perspective of an actual reviewer. I highly recommend this to those who are writing a resume but feel like something is missing, especially those like me who have practical experience but are struggling with how to present it. Lastly, I would really like to participate in the resume feedback event held for course reviewers. I look forward to this being an opportunity to take the resume I just overhauled to the next level. 🙂 PS. Thank you so much for the limited quantity discount coupon provided on YouTube, which allowed me to take the course even cheaper than the early bird discount. Is there anything in the content above that exposes the course material?

5.0

코딩하는 누누

56% enrolled

While watching this lecture, I realized that everything you said not to do was in my resume. I felt a bit called out, but now I understand why all my applications were rejected while I was preparing to change jobs. This time, I will revise my resume and experience description well to achieve a good result. Thank you for creating such a great lecture.

5.0

신영인

100% enrolled

This lecture clearly answered the questions I had while reviewing others' resumes and writing my own! I'm leaving with great insights. I especially liked how you clearly explained what makes a good resume and what its purpose is, while leaving the actual writing up to me. Thanks to that, I think I'll be able to take my time and think more deeply about it. The lecture was easy to listen to and the content was so good that I finished it in less than a day. Thank you for the great lecture!

What you will gain after the course

  • Understanding the essence and strategy of resume writing, regardless of whether you are a job seeker, a new graduate, or an experienced professional.

  • Understanding the attitude toward resumes and the essence of writing them

  • Understanding resume utilization strategies and management systems

  • An experience that makes you rethink your resume

  • The perspective of a document reviewer looking at a resume

What 10,000 Resumes Have Taught Us

There is no common formula for a passing resume,
but for resumes that fail, there is a repeating pattern.

10,000 people have 10,000 different charms.
However, many people often fail the screening process because of resumes that do not properly capture their unique appeal.

I hope you don't give up because of your resume.

Based on patterns discovered while reviewing over 10,000 resumes,
I will point out what to do, what not to do, and the reviewer's perspective one by one.

Our story of preparing for employment/career change

You wrote it diligently,
but failed again?

I wrote my resume diligently to prepare for employment.
I organized it with great care. I included every skill I know and described my projects in as much detail as possible.
However, all I received in return was a rejection email without a single line of feedback...

Without knowing the reason, you submit the same resume again with only minor adjustments. You are rejected once more.
Is it because you lack experience? Or because your qualifications are insufficient? That might not be the case.

Your resume is not properly conveying your appeal.


" The problem isn't your diligence. It's your direction.
The things you included because you thought they would look good might actually be points of deduction. "


<Common Mistakes That Diminish the Appeal of Your Resume>

1️⃣ Listing every technology you've ever touched without considering what needs to be emphasized.

2️⃣ Listing only numerical achievements of what was done without providing any background explanation for the project.

3️⃣ You focus so much on highlighting what you want to emphasize that you fail to demonstrate your suitability for the job.

4️⃣ Out of fear that leaving something out might be a disadvantage, you include as many experiences and career details as possible.


If you want to create a compelling resume,

"From the reviewer's perspective,
you must redefine your resume."

Why this lecture is different

Not just a standardized template,
but a lecture that changes your perspective

Point1.

Understanding the perspective of the document reviewer

Resumes are essential for document screening and technical interviews!
If you want to write a good one, you must first understand the reader.

Document reviewers judge resumes much faster and more strategically than you might think. This is why the content you wrote so painstakingly goes unread, and why the projects you carefully organized fail to stand out.


Understanding the reviewer's perspective is not just a simple tip.
It is an experience that completely changes your perspective on writing a resume.


Point 2.

Experience it through the resumes of current developers

The lecture includes a section where you can experience the actual resumes (anonymized) of three current developers.

It is not simply about "write it like this." We will look together at actual resumes to see where a reviewer's eyes linger, what parts they find appealing, and what parts they find lacking.


Why is it important to look at other people's resumes?
It is difficult to view your own resume objectively, but you can look at someone else's resume through the eyes of a reviewer. In particular, by comparing resumes before and after advice, you can see for yourself how the same person's experience can be conveyed differently.

See for yourself the difference in impression created by just a few lines of text and their layout.


What you'll learn

Section 1. 15 Things You Should Not Do

Most resumes are ruined not because they are lacking, but because effort was put in the wrong direction. Things included because they seemed good, appeared diligent, or felt like a waste to leave out are actually the very reasons for document rejection.

In this section, we will point out the bad habits that many people are inadvertently repeating one by one.
Once you learn about them, there will definitely be things that make you think, "I was doing that too."

Section 2. 14 Things You Should Do

Now that you've removed what shouldn't be there, it's time to focus on how to fill it. There is a clear difference between simply listing your history and creating a resume that actually gets read.

In this section, we will guide you through the practical steps to create a resume that catches the reviewer's eye and moves you to the next stage. A small shift in perspective can make your resume look completely different.

Section 3. The Perspective of the Document Reviewer

If you want to write a great resume, you must first understand the perspective of the person reading it. Reviewers read resumes in a different way and in much less time than you might think.

In this section, we will reveal the exact perspective of a CTO who has reviewed 10,000 resumes. The moment you understand "how my resume appears to a reviewer," your entire perspective on writing a resume will change.

Section 4. Experiencing Real Resumes

This is a section where you can see what you've learned in theory applied to actual resumes. We will take a look at the resumes of current developers together to get a sense of which parts are lacking and which parts are good.

The difference between a good resume and a disappointing one is truly felt when seen with your own eyes rather than just hearing an explanation. This is a time to personally experience the concepts learned previously through real-world examples.

Section 5. Appendix

This section is for those who might still have lingering concerns after the lecture, such as, "But my situation is a bit different... what should I do in this case...?" It covers a variety of topics, including concerns about employment in the AI era, worries of newcomers, and the dilemmas of developers whose experience is limited to legacy system improvements.


Recommended for these types of people.

Those who keep failing the document screening process but don't know why

Those who have received only rejection notices without a single line of feedback on why they failed despite writing diligently.
Those who are repeatedly submitting the same resume without even being able to identify what the problem is.

Those who are cramming everything in because they lack the criteria for what to include or exclude in their resume

Those who have included everything—from every technology they know to every project and award—fearing they might lose out if they leave anything out. Those who want to take this opportunity to properly organize a resume that has been piled up without any clear standard of what to emphasize.

Those who want to understand the perspective of a document reviewer

Those who have been curious about what resume reviewers actually look for and what makes them feel fatigued.
Those who have wanted to think from the perspective of the reader, rather than the writer, even just once.


Course Notes

Learning Materials

  • 4. Lecture Materials You can receive the PDF used in the lecture during the class.


A message for the students 💌

After reviewing 10,000 resumes, I have come to one certainty:
10,000 people have 10,000 different unique charms..

However, many people keep failing at the document screening stage because they hide their charm and use resumes that fail to express themselves properly. Recently, I have come to feel even more deeply that there are far more people than expected—both promising newcomers and capable experienced professionals—who do not even get the chance for an interview. I created this course because I wanted to help them.

This course is not about providing the right answers.
It is a course that captures the process of thinking together about how to bring out what is already within you, organize it, and present it properly. While there is no formula that guarantees passing, I can give you the power to create a resume that is uniquely yours.

I hope you take this opportunity to check with this course whether your current resume truly captures your unique charm.

gemini_mentoring_banner

The person who created this course

Key Experience

  • Former Technical Director (Director of Engineering) at Toss Payments

  • Former Woowa Brothers Server Developer

  • Former Server Developer at Lezhin Entertainment

  • Possess diverse experience at 7 other companies, including startups

Presentations & Interviews

Recommended for
these people

Who is this course right for?

  • Job seekers or entry-level developers who find it difficult to write a resume

  • Experienced professionals who don't know how to articulate their experience and career history on their resume.

  • Those who keep failing the document screening process and don't know why

  • Those who want to understand the perspective of document reviewers

  • Those who want to understand the essence of the resume writing and document review process

  • Those who were only focused on filling their resumes with simple career history

  • Those who are cramming everything into their resume because they don't have a standard for what to include and what to leave out.

Need to know before starting?

  • Although this lecture was created based on a general developer resume, it is fundamentally structured from the perspective and background of a backend developer.

Hello
This is geminikims

Inflearn Verified

Career Verified

6,466

Learners

326

Reviews

144

Answers

4.9

Rating

7

Courses

Key Experience

  • Former Director of Engineering at Toss Payments

  • Former Server Developer at Woowa Brothers

  • Former Server Developer at Lezhin Entertainment

  • Possesses diverse experience at 7 other companies, including startups

Presentations & Interviews

Blog

More

Curriculum

All

59 lectures ∙ (7hr 34min)

Course Materials:

Lecture resources
Published: 
Last updated: 

Reviews

All

100 reviews

5.0

100 reviews

  • alstn113님의 프로필 이미지
    alstn113

    Reviews 1

    Average Rating 5.0

    Edited

    5

    100% enrolled

    Thank you for the great lecture. I am also a regular viewer of your YouTube videos. I am currently preparing for backend positions, and I noticed that most companies require both a resume and a portfolio when applying. Therefore, I have been summarizing my accomplishments concisely in my resume, while using my portfolio to describe problem situations, solutions, and my thought process in more detail. After taking your lecture, a concern has come up. If I should include the problem background, solution process, and my considerations within the resume itself, how should I structure the content in my portfolio? I am wondering if it is better to expand on those points in even greater detail, even if it means some content might overlap.

    • geminikims
      Instructor

      Hello Minsu, thank you for the course review! The atmosphere and patterns vary much more than you might think depending on the company and the reviewer (various situations such as company size, recruitment process, number of document reviewers and interviewers, etc.). Therefore, it is difficult to generalize, but in my opinion, you should provide enough explanation in the resume to lightly aid understanding and include the details in the portfolio. As I mentioned similarly in the lecture, since reviewers ultimately focus more on the resume when there are "many applicants," I believe it is correct to sufficiently appeal your primary charm within the resume itself. If you have any further questions, feel free to ask in the community section! Thank you!

    • geminikims
      Instructor

      To celebrate the launch of the course, I will be conducting resume feedback sessions through a lucky draw! You can participate in the event by writing a "detailed course review"! Please check the news section for more details: https://inf.run/gKTVL

  • daynarr0070454님의 프로필 이미지
    daynarr0070454

    Reviews 6

    Average Rating 5.0

    Edited

    5

    63% enrolled

    First of all, I trust your content because it lacks misleading phrases like "The Resume Formula" or "Write like this to get hired." (Looking at the career you've built, it's impossible to argue otherwise.) However, conversely, the idea that there is no "right answer" for a resume left me feeling complicated, thinking, "Then what am I supposed to do?" It's truly difficult. I don't think I'm just a typical developer who has only done standard development; I consider myself a bit of a unique case. Because of that, I'm at a loss as to how to explain my story. As I get older year by year, I've suddenly reached 6–7 years of experience. In a smaller team, 6–7 years of practical experience is a time when one should be taking on a leadership role, but facing the reality of not even passing the initial document screening makes me wonder if my skills are really that lacking. All sorts of thoughts are crossing my mind. (It makes me feel gloomy thinking that everyone else looking for a job probably feels the same way I do.) Still, no one else is responsible for my life, and I believe I must trust the conclusions I reach myself. Although the growing pains of figuring this out are arduous, I think this is a great lecture to start the process of pioneering my own life from scratch in order to gain confidence in my own answers. P.S. I would like to ask questions about the things I'm struggling with, but since a resume contains personal information, I'm honestly hesitant and embarrassed about posting on a public forum like the Inflearn Q&A board where others can see. I'm not sure what to do in this case.

    • geminikims
      Instructor

      JH! Thank you for the review! "The saying that there is no right answer for a resume—then what am I supposed to do?" This is actually very true. It's almost like trying to learn how to swim through words...? Nevertheless, as you wrote, I created this course with the intention of it being "a good lecture to start the process of pioneering my life all over again." Thank you for thinking of it that way! I believe there are definitely fundamental strengths in the experiences you have that aren't related to general development. My first career was also in firmware development, and I have built my career through various forms such as embedded systems and SI. At the time, I thought those careers were something I should discard, but looking back at some point, there were definitely things I gained back then... Anyway, I hope you reflect and contemplate well so that you can write an even better resume!! Regarding the part you mentioned in the P.S., I think there will be quite a few inquiries for me to handle via personal email, so I will think about whether there is another way to resolve this! As you wrote, it would be great if you could ask questions in the community section from the perspective of general strategies!

  • keephun님의 프로필 이미지
    keephun

    Reviews 2

    Average Rating 5.0

    5

    14% enrolled

    Hello, I am an aspiring back-end developer looking for a job. I have been a subscriber to Gemini's YouTube channel for a year and started this course with high expectations, but this course far exceeded them! While writing my resume until now, I used to keep the problem definitions in my portfolio and focus my resume on how I solved those problems and what results I achieved. However, after watching this lecture, I was able to understand how it feels from the reader's perspective, and I think I've found a great sense of direction again. Also, by thinking about what I should showcase on my resume, this lecture helped me establish a direction for what I need to do more of in the future! For those who are new to the field or in their second year, who have many projects but find their resumes becoming mediocre, or who don't understand the essence of the reasoning behind technical choices—I believe this course is a must, not an option. Good luck to everyone with your job searches and career moves!!

    • geminikims
      Instructor

      Hello Jihoon, thank you for your thoughtful review! I'm so glad to hear that you were satisfied with the course :D I tried to deliver the content as raw and authentic as possible, and I'm very happy if that came across well! It feels very rewarding because it seems like you understood the intention I wanted to convey while creating this course. haha I wish you the best of luck and hope you keep up the great work, Jihoon!

    • geminikims
      Instructor

      To celebrate the launch of the course, I will be conducting resume feedback sessions through a lucky draw! You can participate in the event by writing a "detailed course review"! Please check the news section for more details! : https://inf.run/gKTVL

  • junyeokk님의 프로필 이미지
    junyeokk

    Reviews 7

    Average Rating 5.0

    Edited

    5

    100% enrolled

    I used to think that I had to explain my experiences quantitatively by including numbers, but after taking this lecture, I realized that such an approach can end up looking like a mere performance report. It should have been obvious to consider who is reading it first, but I reflected a lot on how I had been writing my resume mechanically until now. When I considered that document reviewers are also busy developers with their own primary tasks, I realized for the first time that they have no choice but to quickly judge an applicant's appeal while skimming resumes in short bursts between work. I truly felt that removing experiences is more difficult and more important than adding many of them. Based on Gemini's actual experiences, I was able to get a sense of what the reviewer's perspective is like, and thanks to that, I had many thoughts while looking over my resume again. It was a lecture that made me think more deeply on my own because you provided a sense of direction rather than just a "correct answer." Thank you.

    • geminikims
      Instructor

      Thank you for your review, junyeokk! It would be very helpful if you could leave a detailed review and feedback later on as well! In addition, we are planning to conduct resume feedback sessions through a lucky draw as part of our course launch event! You can participate in the event by writing a "detailed review"! (You may also edit the review you have already written!) Please check the "What's New" section for more details! : https://inf.run/gKTVL

  • kayden님의 프로필 이미지
    kayden

    Reviews 10

    Average Rating 4.9

    5

    100% enrolled

    The "direction" of my resume has changed. This is a lecture that changes your perspective, not just your technique. I used to write my 5-page resume by repeating the "Problem→Solution→Technology→Result" pattern. I thought I had organized it well by including metrics, but after listening to the lecture and re-reading it from a reviewer's perspective, it was exactly as the CTO described: a "performance report." The biggest turning point was the perspective that "reviewers start at 100 points and subtract." Once I realized it’s a structure where points are docked every time they are disappointed, rather than building up from zero, I stopped being afraid of removing unnecessary items and was able to focus on the 2-3 things I truly wanted to emphasize. The Before/After comparison videos were especially helpful. The difference between writing the same experience as a pattern versus telling it as a story was clear, and I truly felt why documenting trade-offs serves as such a positive signal. In the process of reducing it from 5 pages to 3, I experienced the content actually becoming richer. This isn't a lecture that just teaches you a resume format; it's a lecture where you learn "how to see your own resume through the eyes of a reviewer."

    • geminikims
      Instructor

      It is so rewarding to hear that the direction of your resume writing has changed, Kayden. Thank you for the thoughtful review! I am very grateful that you recognized the intentions I had while creating the lecture. I hope it proves helpful for the resume you will write in the future!

geminikims's other courses

Check out other courses by the instructor!

Similar courses

Explore other courses in the same field!

Limited time deal

$48.40

29%

$68.20