your resume should tell a story #resumetips #resumehelp

25 Mar 2026 · 0 min

Watch on YouTube

0:28

In this brief video, the speaker criticizes the common practice of filling the top of a résumé with vague, generic statements that fail to convey a clear narrative. He stresses that the résumé’s opening section is the first impression for employers and should immediately communicate a concrete story about the candidate’s capabilities. To achieve this, he advises placing specific skills together with the number of years of experience in the top third of the résumé. He provides concrete examples—such as “TypeScript – 3 years,” “AWS cloud – 2 years,” and “.NET web development – 10 years”—to illustrate how to format these details. The overall message is that precise, quantified skill listings at the top create a stronger, story‑driven résumé.

Most of y'all just have a bunch of jibber jabber at the top of your resume, and it's awful. It doesn't tell a story. You have to understand something. Your resume is the first thing that employers see, and it crafts a narrative. So, at the very top of your resume, the very top third of your resume, I need specific skills, what you've done, how many years of experience. I've done TypeScript for 3 years. I've done cloud AWS for 2 years. I've done .NET web development now for 10 years, right? I need specifics.