Hi, I have been rejected at a couple of BA interviews because the client interviewer thinks I am too technical. But if the interviewer asks me for instances from practical experiences I find it difficult to give just a bird's eye view. I am flummoxed whether to project myself as a generic BA or a technical BA, or how do I maintain a balance between the two.
On my resume I have:
"Project Manager / Business Analyst with a Technical Programming background"
Tailor your job activites more towards the BA part (Requirements, Spec Writing, JAD / RAD sessions, QA Testing, etc.)
If you're making to the interview process then it's probably not your resume that's the issue.
I'm trying to understand if you believe the issue here is that the answers you provided to certain questions were too technical, or that you provided too much detailed information. Those are two different issues. You can be asked a technical question and provide too much detail, and you can be asked a soft skills or business question and reply with technical jargon not relevant to the question.
Can you provide a few questions that you thought were an issue and give the general type of response you gave?
Hi:
Sounds like you have the tech skills. As for a "generic" BA, I am not sure what you mean. Do you? Try answering the following question: The primary purpose of a (non-technical) BA is to xxxxxxx". Figure out what xxxxxx should be. Hint: This is not an easy question to answer. But to the extent that you have a solid answer and can slant your answers to interview non-techincal questions according to that answer, you will come out ahead.
FYI: My answer to the question: The primary purpose of a BA is to come up with a comprehensive, integrated understanding of the key processes/functions and - especially - to come up with an understanding of their essential interrelationships.
You can come up with your own answer, but, key is to come across as a purpose driven individual.
Tony
Do you know your interviewer ? Google and find out their skills.
If they're not technically inclined and you use tech-speak jargon, then that would be a concern. Because it's been an eternal problem of tech folks using acronyms and tech-speak which leave the non-IT community befuddled.
Articulate your answer in plain English
brought to you by enabling practitioners & organizations to achieve their goals using: