If you've been in IT for more than, say, a few years, you have more skills than room on your resume - especially if you're keen to keep it to one page.
So how do you determine what stays and what goes? Writer Jack Wallen tells pluralsight all you have to do is answer one question:
"How did those skills and experience affect the bottom line of the company you worked for?"
Given the fact hiring managers spend 6 seconds skimming resumes on an initial purge, you need to hop to. Listing extraneous skills - no mater how wonderful and legitimate - will bore the screener and send your resume straight to the trash.
"You have to immediately display how you can affect a positive change to the bottom line for prospective clients," he adds. "That will get you much farther than a bulleted list."
Wallen outlines excellent examples of how to apply this approach to an IT resume.
"If you re-deployed a company network using all open source technology, and saved said company tens of thousands of dollars on their yearly budget, that should land on or near the very top of your list," he argues. "If you implemented a firewall system that served to not only block unwanted access to your network, but significantly drove down port scans to your servers, that too should land on or near the very top of your list. If you served as desktop support for a twenty or so desktop users, yes, that could go on the list, but how did it save the company money?"
The bottom line? Think bottom line.