Which BA are you?

I have never heard of a profession that has more titles than ours. Sometimes I wonder if the reason why everyone is so confused about the role of Business Analysts isn't related to the vast array of hats we wear and things we do. For someone who is new to Business Analysis, this can be confusing.
Imagine this scenario: you just read a great BA job description for a job that you are really interested in. The job is asking for someone who understands different Business Analysis techniques and can be a good liaison between different stakeholders.
Without a question, you know you qualify... First day on the job, things are becoming a bit gray. Who do you liaise with? Do you really have the experience using Business Analysis techniques in the context of your new job? How can you tell if an organization is the right fit for your skills? What type of BA are you and should you be?

BA in customer facing organizations

If the organization has external stakeholders -- consumers of your products or services, and is small enough where internal processes are not complicated enough to deliver the solutions; The role of BA in such organization can be solely customer facing. This BA would work with the BA of the other organization (assuming there exist one) to analyze the need of the external organization and define requirements based on the capabilities of their products and/or services. In my past experience, this role requires not only the hard skills of Business Analysis (interviewing, requirement workshops... etc) but you will bring more value to this organization if you knew how to negotiate, facilitate, lead meetings... etc. The skills not taught in school. But most importantly: If you are this type of BA, you may not have the opportunity to define your stakeholder's processes nor may have time to do so. The BA in this role has a number of challenges:

1. Quickly grasping stakeholders process and assessing if the solution will address these processes.
   
2. Defining the gap needed for the product/service to fulfill the requirements.
   
3. Remembering who they work for... hint: not the client!

Internal BA

You may also find yourself working in an organization where your job is confined to fixing internal processes. In this role, there isn't much convincing you need to do. Your job is to define the As-Is (Current State) then work with internal stakeholders to develop a To-Be (future State). Your job is to understand what does the process do... what is its end result. Then assess its efficiency (is the process producing the end result without wasting too many resources - time, money, human capital... etc)

Hybrid BA (and I don't mean PM/BA or BAM)

I am talking about BAs who must interact with external stakeholders to understand their requirements. At the same time, they also review internal processes in order to determine if the implementation of a solution will affect internal processes. For example, after conducting market research your company decides to implement a product. You decipher requirements from the research... before you finish documenting them, you need to turn to the business/operation side of your organization and see how the implementation of the solution will affect their processes (training, customer support.. etc)
You may find yourself documenting the as-is and formulating the to-be process that will support the solution.
This role can be broken up into two BA roles or can be combined into one role. In my experience, companies do not break up this role. The person in this role has to understand process modeling and reengineering to some degree and also be great with documenting business requirements and user requirements. Then translating them into functional requirements.

My question to you is what kind of BA are you? Have you found yourself working in different scenarios than the ones I listed?