My question is about BA resumes. I have 5 years of experience in IT and around 4.5 in BA. I am a developer/BA blend, as I understand from your book My resume lists my experiences chronologically. I remember from your IIBA presentation on resumes that a resume should contain accomplishments vs just responsibilities. What proportion of these two things do you suggest?
I don’t want the resume to sound like I am just blowing my own trumpet but balance it with something like this is what I helped the company with (in other words, accomplishments) and these are the additional responsibilities that I handled.
I totally understand the desire not to sound too much like a salesperson when you are putting your business analyst resume together. However, the reality is that you do need to sell your legitimate qualifications on your resume and be sure it clearly communicates what you can do by showing what you have done. The first person reviewing your resume is very unlikely to make assumptions in your favor. So toot your own horn or blow you own trumpet, even if just a little.
Let’s look at exactly what an accomplishment is. An accomplishment is a tangible result you’ve achieved for an organization you worked for. It is a benefit they received of employing you as a BA or a developer or in a blended role.
If you are honest about what you contributed, you’ll start to feel less like a salesperson and more like a communicator. And that’s the sweet spot you want to be in. You’ll need to be there before you succeed in the job interview, so you might as well figure it out when putting together your resume.
The other thing about accomplishments is that they don’t just happen. You have to do something to make them happen. Your projects are not wildly successful because you happened to wake up on the right side of the bed. Your requirements aren’t clear representations of real stakeholder needs that solve real business problems because you put random words down on paper. You did something tangible to make this happen.
This is why backing up your accomplishments with responsibilities is so important. Trust your “blowing my trumpet” instinct to guide you to in asking “what did I do to achieve that result?” In the answer to this question, you’ll find your how behind your what.
Include both in each bullet point.
Achieved alignment across four departments about a new, user-friendly navigation scheme by creating mock-ups, identifying stakeholders, and facilitating review meetings.
Or, as another example,
Improved communication between product managers and the software development team by modeling requirements in use cases and holding combined walk-through meetings, resulting in fewer changes in test.
This way your list combines accomplishments and responsibilities in one statement. Written this way, all of your bullet points could show accomplishments.
If you want more information on what responsibilities and accomplishments to include in your resume, especially if you have a varied career, click here to read my take on that.
>>Get More BA Job Interviews
Join us in Building a BA Resume that Lands You Interviews - a self-study virtual course that walks you through how to best represent your business analysis qualifications in your resume and provides examples using the project summary format in your work history section. Also included is my Ultimate Guide to Bullet-Proofing Your BA Bullet Points which contains patterns you can use to write credible bullet points in your work history and more project summary samples.