Somewhere in the midst of discussions about things like “tailoring your resume to the position,” one of the best pieces of resume advice gets lost: Your resume needs to be accomplishment-oriented. Many resumes that I see do precisely the opposite. They offer bullets like: Contributed to design documents on ________ feature and helped coordinate international expansion. Implemented various features for new Office layout tool. Yawn. I want to know what you accomplished. I don’t really care much about your team’s accomplishments. And, in many cases, I already know what your responsibilities were because I know your job title. If you were a developer, you probably wrote some code, did a little testing and maybe helped out with a few design docs. How does a good resume read? Here are the first words of each bullet from a strong programmer resume I saw recently: “reduced,” “implemented,” “redesigned,” “promoted,” “created,” “promoted,” “implemented,” “created,” “optimized,” “bu