Let’s see how this formula works in practice:
[I am a] Seasoned systems analyst with strong commitment to time and resource budgets, new-business development, strategic planning, innovation, technology trends, customer-service needs, and close collaboration with sales and marketing during development.
[I am a] Competent problem-solver who resolved sales and shipping issues by creating internal customer-care system and saving 20 percent on shipping; researched and delivered Web conferencing service for sales that saved 30 percent of travel budgets.
[I am a] Visionary innovator who partnered with another programmer to create pioneering language-learning software that earned national attention; served as lead analyst for revolutionary legal document generating and tracking product.
[I am a] Technical guru who provided direct support for successful million-dollar negotiation with major print vendor and completed many successful major conversions from mainframe to mini-computer systems.
[I am a] Strong communicator who was voted best specification writer “ with least number of re-writes “ by programmers and their managers.
You’ll note that the story-based grammatical structure of these parallel bullet points goes like this:
[Adjective] [noun] [connecting words] [phrase describing skill/strength/expertise] [supported by quote, example, numbers]
Composing RAS/RAP/RAC Stories as Bullet Points to Describe Accomplishments
Presenting your accomplishments in your resume represents a case where it’s OK, indeed desirable, to give away the end of the story first. Tell the Result (R) of your Action (A) first so it catches the employer’s attention. Then, ideally, describe the Situation (S), Problem (P), or Challenge (C) that your Action addressed. Quantify wherever possible.