You know, I started my career as an IT consultant who loved programming code.
How’d I get from there to a full fledged BA?
Well, the truth is, I slowly learnt over a period of five years.
First, I signed up for BA roles in my IT consulting projects, despite my other colleagues leaning towards IT Architect and Programmer roles.
Next, I learnt how to elicit and document system requirements to a high degree of quality.
I also learnt how to stand up in front of a group of users and steer them towards agreeing a set of system requirements or business process workarounds.
I remember I signed up for large scale Business and IT Transformation projects, specifically asking to be one of the BAs.
It would be a boon if the project was banking or insurance related, as I felt those were the industries where cutting edge Ops and IT work was being done.
Doing the above allowed me to transition from an IT guy to a Banking Business Analyst.
Perhaps you can do the same.
And if you’re serious about becoming a Banking Business Analyst, then you need to get some solid tips on what to do.
My best-selling Banking Domain Knowledge For Business Analysts guide book consolidates ALL my know-how about the Banking Domain and also BA Career into one huge resource.
>> Click here to check out Banking Domain Knowledge for BAs << This book has helped countless readers of mine secure interviews and jobs as BAs with banks, consulting firms and software vendors. You should check it out. I’d also love to hear you thoughts! Just reply and let me know. And as always, I wish you the absolute best success in your Business Analysis career and I’m here to help in any way that I can.