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

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?

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.

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!

I have 5 years of experience, but I’ve never had to write a resume or go through an interview process until now. (I started my development career at my current company through an internal job transfer...) Over the past 5 years, I’ve had various development experiences, and I thought my unique personal career path was a strength... so I confidently applied to my first company, only to be immediately rejected at the document stage. haha. While watching the lectures, I realized how wrong I was, so I canceled all my other applications and am now focusing on the course. Thank you for the great lectures. --- Adding more after completing the course. The part I found most useful in this course is the "Before Advice / After Advice" section. I’ve actually rewatched that part several times, analyzing the differences between what I wrote and the examples. I highly recommend this course to anyone who needs to figure out why their resume isn't appealing or what specific problems it might have.

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!!

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.

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.

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.