🎯 𝐓𝐡𝐞 𝐒𝐩𝐞𝐫𝐦 𝐚𝐧𝐝 𝐭𝐡𝐞 𝐄𝐠𝐠: 𝐀 𝐅𝐫𝐞𝐬𝐡 𝐓𝐚𝐤𝐞 𝐨𝐧 𝐂𝐕 𝐖𝐫𝐢𝐭𝐢𝐧𝐠 Yes, it’s a strange title for a CV post—but stick with me. There’s a method to the madness. Here’s the thing: in my (slightly cynical) view, once a job is advertised, it’s often too late to stand out. Timing is everything. Think of it like the sperm and the egg—if you’re not prepared, someone else gets there first! 🏁 Now, let’s dive into the advice: 1️⃣ It’s a Marketing Document—Plain and Simple Your CV is a tool to get one thing: a conversation. 🗣️ That’s it. No fluff, no fancy tricks—just a clear message that makes someone want to talk to you. 2️⃣ How Long Should It Be? 🚨 It doesn’t matter. One page? Great. Five pages? Also fine. What matters is relevance. If it’s useful to the reader and shows your value, it works. 3️⃣ First or Third Person? 👉 Always write in the first person. Third-person CVs often feel impersonal and awkward. But hey, if breaking the rules works for you, more power to you—I love a maverick! 💥 4️⃣ Focus on Outcomes, Outcomes, Outcomes 💡 Especially for senior roles like CTOs, hiring managers care about one thing: ROI. Quantify your results. Show your impact. Be crystal clear about the role you played in delivering success. 5️⃣ Cover Letters: Always Yes ✍️ A tailored cover letter is your secret weapon. Make it short, relevant, and polite. Use it to explain why you’re worth their time. This is where you connect the dots between your CV and their needs. 🔑 Final Thought: Your CV isn’t just a list of jobs—it’s your story. Make it compelling. Make it intriguing. Make it count. What’s your biggest CV-writing challenge? Drop it in the comments—I’d love to help! 👇
Does that mean the ATS is a condom?
Thanks so much for putting this out Warren Beazley (FIRP)! Much appreciated. I've sent it out to our CTO Job Club and invited them to ask any questions they have.
VP Engineering at Treecard | Building Consumer Apps to Combat Climate Change
6dWarren Beazley (FIRP) Is there a CV format you've found particularly impactful? My current structure includes an overview, work experience, education, and skills. I'm curious how should I approach the 'skills' section? Any tips or alternatives?