Everything written here is based on advice I gathered from YouTube, seminars, and mentoring, focusing primarily on the “Developer” and “AI Engineer” roles. Because this isn’t based on my direct experience, please treat this material purely as reference.

Please note that since most of the advice I’m hearing is from an undergraduate perspective, I ask that you keep this context in mind. If I’ve misunderstood anything, or if you have any further advice, I would really appreciate it if you could let me know in the comments.

I will revise that section if there are any issues.

Resume, Portfolio, and Experience Certificate

• Resume: A formal document submitted to an applying company, typically 1-2 pages long, including education, work experience, tech stack, and project history.
• Portfolio: A resource—usually a personal website or PDF—that visually showcases your skills and experience by including detailed project descriptions, code samples, and demo links.
• Experience Certificate: An official document issued by a previous employer that verifies your career by specifying employment duration, job title, and responsibilities.

I think it’s uncommon for undergraduates to have formal work experience certificates, but I imagine there are people who served in the industry rather than the military, or those with 1-2 years of internship experience, or people who paused their studies, got a job, and then returned to school. For those individuals, if the role aligns with your background, I recommend applying to companies by utilizing those work experience certificates along with your other materials.

A resume is generally structured with sections like a personal photo, Contact information, Job Role, Summary, Education, Tech Stack, Projects, Work Experience (covering internships, freelance, and previous jobs), Awards, and other activities.

My resume absolutely cannot be messy; it needs to be extremely clean and neatly organized. Ultimately, the goal is to make it effortless for the reader to consume.

So, how can I build a clean resume? I’ll walk you through it in the order of [Summary, Tech Stack, Projects, Awards, Other Activities].

Please remove the icon.

Summary

I notice people writing summaries like, “As an AI engineer, I am passionate about developing machine learning and deep learning models. Based on my diverse project experience and tech stack, I aim to develop innovative AI solutions that positively impact society.” However, the consensus is that if 100 people write this, it becomes boring to read and doesn’t really stick with people. Therefore, I recommend writing something that feels genuine and comes directly from your unique experiences.

Since everyone’s life environment is different, there’s something unique that comes from the environments you’ve lived in. I recommend writing while drawing heavily from that personal experience.

Can I use AI? -> If you can definitively answer the question, “Does AI know the 20 years of your life?”, then I suggest using AI.

Tech Stack

I recommend tailoring your tech stack based on the role you are applying for.

1. When applying, many people mix up frameworks and libraries when writing this section, so please be careful about this.
2. I notice some people write tech stacks like “On Python,” or “On JavaScript.” I recommend removing the qualifier like that and just listing it as “Python: TensorFlow, PyTorch, Scikit-learn.” Ultimately, what matters is showcasing how you’ve used that tech stack in your projects and experience.
3. Assuming you’ve taken all required and elective courses from freshman to senior year, you’ll learn languages like C, C++, C#, Java, and Python. Don’t list all of them! Instead, I recommend tailoring it to the role you’re applying for—for example, use C++ and C# if you’re going for a game development role, or use Python if you’re aiming for an AI Engineer role.

Projects

When I’m designing a resume to fit on a single page, the space allotted for projects is really limited. Because of this, I recommend keeping the project count to around 1 or 2.

If you plan to stretch your resume to two pages, it implies you have a lot of impressive work to show off, so I recommend keeping the featured projects to about 3-4.

When documenting a project, I recommend including the project name, duration, and a short summary. For the detailed content below, I suggest structuring it using the format: Problem + Solution + Achievements. Here is an example.

If I set the font size for the name to 14pt, the period to 10pt, and the short summary to 12pt, etc., I recommend varying the font sizes so that the project name stands out the most.

If I want to create a really clean resume, I recommend studying Typography or gathering inspiration from various resumes online and combining elements to build my own.

“Building an AI Automated Ticket Reservation System” [Jan 2026 ~ Feb 2026] (Individual/Team) This was a team project of three people where I built an AI ticket reservation system utilizing “Technology A,” “Technology B,” etc., designed to secure tickets within 0.1 seconds for a BTS concert.

Since BTS concert tickets sell out in ?? seconds, the chance of succeeding manually was extremely low. I leveraged “Technology A” and “Technology B” to capture the network traffic when the server opened, and then used “Technology C” to automatically refresh the screen every 0.1 seconds, ensuring the booking would happen the moment the reservation button became active. Through this system, I was able to build a system achieving a 99.9% success rate. (I recommend structuring this in 3-4 lines to clearly illustrate the problem, the thought process, and the solution during the project.)

Technologies Used: ~~~~

What I wrote is absolutely not the definitive answer. I recommend structuring it to clearly highlight the problems and the entire resolution process from a project you personally worked on.

Awards & Activities

I suggest structuring the entries using the format: “Organizer, Award Name, Award Date, Topic, Summary.” I recommend arranging these in a 2-column block layout.

I recommend structuring it like this. For awards and other activities, since these demonstrate what I’ve done—rather than describing a project—I suggest keeping the descriptions concise rather than going into detail like a full project explanation.

For extracurricular activities, you can briefly list any activities you’ve participated in, such as clubs, academic societies, external projects, or volunteering. I recommend listing them with the name, duration, and a short description.

Publications and Undergraduate Research

If you have any papers that were submitted and accepted during your time as an undergraduate research assistant, I recommend creating a separate “Publications” section. For these, include the paper title, authors, conference/journal name, date, and a brief description.

If I structure it like this, the resume should naturally come out to about 1–2 pages. For those whose resumes are 3–4+ pages, I strongly recommend taking a moment to reflect on what your most critical experiences and projects are, and what you truly want to highlight.

Of course, sometimes people have incredible track records, but ironically, their resumes are actually quite short. It’s because they don’t need to say much—their achievements speak for themselves.

Next, I’m going to write a post about how to plan out a portfolio.