11 Resume Mistakes You're Probably Making 📝

and how to fix them

Hi there!

Welcome to this week's edition! We're excited to kick off a new series focused on Resume Tips to help you stand out in your job search. As a mentor, I've reviewed more than 100 resumes, and I can tell you—there are always common mistakes engineers make when crafting their resumes.

This week, we highlight those mistakes and how to avoid them.

Top Job Picks 🔝

• Software Engineer - Salesforce (Remote)

• Data Engineer - Spotify (Remote)

• Data Scientist - Stripe (Remote)

Looking for more opportunities? Join our Talent Pool for personalized job matches and explore all our listings at TopAIsJobs.com.

---

Resume Tips Series: Avoid These 11 Common Mistakes

After reviewing more than 100 resumes as a mentor, here are some of the most common mistakes engineers make and how you can avoid them to make sure yours stands out:

1. Using a Generic Resume

Tailor your resume for each job. Match the job description to show you're the right fit.

2. No Action Verbs

Avoid phrases like "responsible for." Instead, use strong action verbs to show initiative.

Example: "Automated data collection processes, reducing report generation time by 50%."

3. Highlighting Duties Instead of Accomplishments

Don’t just list tasks, focus on your achievements. Employers want to know how you made a difference.

Example: Instead of "Developed software solutions," say "Created a software application that streamlined workflow, saving the team 10 hours per week."

4. Lack of Specifics

Be detailed about your contributions.

Example: "Developed and tested a new algorithm that improved processing speed by 25% in a real-time data processing application."

5. Not Using the Right Formula for Bullets 🎯

To write clear and effective bullet points, use this formula:

• Action Verb: Start with a strong verb that shows what you did.

  Example: "Implemented"

• Task: Describe the task or what you worked on.

  Example: "a new data pipeline"

• Tools/Frameworks Used: Mention the tools or frameworks you used to achieve the task.

  Example: "using Python and Apache Kafka."

• Result: Explain the outcome or benefit.

  Example: "which increased data processing speed by 30%"

• Impact/Benefit: Highlight the broader impact or benefit of your work.

  Example: "enhancing the team's ability to make timely data-driven decisions."

6. Overlooking Soft Skills

Highlight soft skills, these can be just as valuable as technical skills.

7. Not Adding Relevant Links

Make it easy for employers to see your work.

Include links to your portfolio, GitHub profile, Linkedin, Kaggle profile, published research papers, and any other relevant online presence.

8. Making It Too Long

Keep your resume to one page.

9. Not Making Your Resume ATS-Friendly

Many companies use Applicant Tracking Systems (ATS) to filter resumes.

To ensure yours gets through:

• Use a simple, reverse-chronological format.

• Include relevant keywords from the job description.

• Avoid images, and unusual fonts that ATS may struggle to read.

10. Poor Layout

A cluttered or confusing format can turn off recruiters. Use clear headings, bullet points, and consistent style.

Avoid overly designed or two-column templates, they can confuse ATS software.

If you’re subscribed to this newsletter, you should have received an ATS-friendly one-column template that's well-structured to help you get through filters and be easy to read. If you’re not subscribed yet, you can do so here.

11. Not Adding Relevant Additional Activities

Don't skip experiences that showcase your skills.

Include participation in hackathons, mentoring experiences, side projects, and relevant volunteer work.

Your resume is your first impression—make it count! You’ve got this! 💪

---

Articles to Read This Week 🗞

- Facial Detection — Understanding Viola Jones’ Algorithm
Written by AaronWard

- The best way to test Web APIs Written by Daniel Moka.

- SQL Has Problems. We Can Fix Them: Pipe Syntax In SQL, Google.

- Work Queues: The Simplest Form of Batch Processing Written by Raul Junco.

- A Practical Guide To Coaching Software Engineers Written by John Crickett.

---

That's all for this week! We appreciate you being here and hope we've added value to your day.

See you in the next edition!

- Gina

P.S. Know someone who'd love this newsletter? Share this post and spread the knowledge!