The summary is the only section of a resume that a recruiter reads as prose and an ATS stores as a single blob of text. That combination is why it is so often wasted. Most summaries are either an objective ("Seeking a challenging role where I can grow") that tells the reader what you want, or a list of adjectives that no recruiter search will ever match. Neither survives the two readers it actually has: a parser that tokenizes it for keyword search, and a human who gives it a few seconds before scrolling to your latest role.
I build Smart Resume Analyzer , and the summary block is where I see the widest gap between what candidates write and what the systems and people downstream can use. This guide covers what parsers do with the section, what recruiters look for in it, real before-and-after rewrites, and a diagnostic you can run in ten minutes.
Should a resume have a summary or an objective?
Direct answer: Use a three-to-four-line professional summary, not an objective.…