Business Analyst Interview Questions.

What is the carreer path for a Business Analyst?

A Business Analyst in the IT field has many varied directions among which to choose a career path. The most direct would lead to a Lead Business Analyst position and then Project Manager whereby the incumbent manages projects through the entire lifecycle from inception to post-implementation including the management of business analysts, system analysts, quality assurance analysts and most likely development project managers or team leads. That path would then lead to Program Management, perhaps PMO management or Product Manager and on to Directorship.In addition, a good Business Analyst may find they are heading toward a Customer Relationship Manager position whereby they become the primary IT interface to a given Business Unit (BU). This role most often leads to a position within the BU as a Manager of Applications or a Process Management role. Process Management opens many jobs including process re-engineering, quality program development, and large scale or enterprise process management programs such as ITIL or Six Sigma initiatives. These roles will continue to proliferate as companies realize the benefits of having a SME in process and quality.And still many Business Analysts find their understanding of business process entirely portable into purely system related positions in the business side that are only peripherally related to IT. These of course may lead to quantitative roles, manager roles or operational roles such as supply chain, logistics et cetera.Of central importance to a successful Business Analyst is the interest in speaking to people. Face to face verbal communication is paramount to support other tools such as surveys and diagrams. Incumbents must be interested in understanding not only the pieces that comprise a system, but the people that comprise it and the realities that embrace the system. Briefly, the Business Analyst must understand and not judge the "what should be" and the "what is".

How do you resolve issues?

Its really simple as you have to check out the folowing:

(1) who(who made this issue),what(what was the actual cause of the issue?),when(when did this issue occur?),where ( where did this happen),why(why did this happen),how( how did this happen)?

and last but not the least you have to use your brain and common sense.

Take for and Example Like:

If an issue comes up saying that people are not doing their work properly in an office and in the end of the month the outcome of performance is not upto the expectations of the standards of the company. then we must look out for the following like helding up Meetings and pointing out people whose standards are not upto the mark and try to help in motivating them, and try to improve their faults, in making efforts to improve their performance standards and and then if things are not going as expected then actions should be taken against them which in Rare cases may result in Termination/suspension/or demotion of the specific employee. this is how most of the issues can be resolved....

How would you transform business requirements to functional requirements?

imple, if I am understanding your question right; Which is the most easiest way to find function requirements: USE CASES make use case for each function of system

What problems did you run into while gathering requirements?

Problems faced while gathering Customer Requirements.
Communication problem.
Inconsistent or contradictory statements which leads to delay.
Difference in Industry Knowledge.
Note: Above mentioned factors can be controled if same process is followed by the vendor as well as the Client.