What are the main red flags to watch for in resumes?

If resumes look AI-generated or have numerous spelling and grammatical errors, that’s usually a bad sign. A cluttered history with short job stints, lots of buzzwords, and missing any direct proof of skills (like a relevant portfolio) can also be a reason to raise an eyebrow. For web dev positions, a missing portfolio is often a dealbreaker.

Pay attention to how easy it is to get to the interesting parts of the resume. If you find yourself reading through long paragraphs without hitting any key points within 20 seconds, the formatting is a problem! Good resumes should be concise but informative. And don’t forget to check GitHub or personal projects—test coverage on personal projects can show commitment to quality.

When reviewing resumes, first and foremost, consider if the applicant seems like someone you would enjoy working with. You're hiring for skills, not for resume-writing expertise. And don't forget to check for actual relevant experience rather than just buzzwords; it should be grounded in real projects they've worked on.

Job hopping is a major concern. If someone has multiple jobs for less than two years each, they’re likely going to leave you looking for a replacement soon after hiring. Also, watch out for resumes over one page for junior roles; they should generally be simpler and to the point.

A huge red flag is when candidates list every single technology they've ever come across without detailing their actual experience with them. It often suggests they don’t have deep knowledge in any. Also, overlapping job dates can raise suspicion. If they seem to have one foot in a side project while applying, it can be a sign they aren't fully committed.