How to find a business analyst.

Business Analyst is a title that describes a location in an organisation rather than a skill set. In financial services it usually means requirements and specifications. In retail and e-commerce it frequently means SQL and dashboards. In operations it can mean process mapping and improvement work.

Those are three different professions, and people rarely span more than one well. A BA who writes excellent specifications may never have written a query; a data-leaning analyst may never have run a requirements workshop. The job description does the filtering that no search string can.

Job titles worth searching

Grouped by what the person actually does, because searching all43 at once produces a result set you cannot triage. Decide which group you need first — that decision does more for the search than any string below.

Where business analysts actually are

IIBA chapters are the professional home of the requirements-focused discipline, running local events and publishing member and volunteer activity. The CBAP and CCBA credentials require documented practice hours rather than only an exam, which makes certified practitioners a genuinely filtered population rather than people who studied well.

For platform specialists, vendor communities are the strongest source by a wide margin. Salesforce Trailblazer profiles, SAP Community contributions, and ServiceNow forum activity all show demonstrable expertise with the specific platform and module, which is what actually matters — and platform experience transfers far less freely than generic BA skill suggests.

The most underused pool is domain transitions. Underwriters moving into insurance analysis, clinicians into clinical systems work, and operations staff into process improvement all bring domain depth that career analysts lack. Because their history is not in analysis, keyword-driven screening rejects them systematically, which is precisely why they remain available.

Boolean search strings

Written to be pasted as-is. Each one is built around an intent rather than a platform, since the useful question is what you are trying to find, not which site you happen to be on.

site:linkedin.com/in/ ("business analyst" OR "product owner" OR "business systems analyst") (CBAP OR Agile OR SQL) "{city}"

("business analyst" OR "requirements analyst") ("user stories" OR "acceptance criteria" OR "BRD" OR "functional specification") -jobs -course

("business analyst" OR "BI analyst") ("SQL" OR "Power BI" OR "Tableau" OR "Looker") ("dashboard" OR "reporting") -jobs -course

("CBAP" OR "CCBA" OR "PMI-PBA" OR "IIBA") ("business analyst" OR "business analysis") "{city}" -jobs -training -course

("SAP" OR "Salesforce" OR "Workday" OR "ServiceNow") ("functional analyst" OR "business analyst" OR "functional consultant") "{module}" -jobs

("Six Sigma" OR "Lean" OR "process mapping" OR "value stream") ("green belt" OR "black belt" OR "process analyst") -jobs -course

("business analyst") ("Basel" OR "Solvency II" OR "IFRS" OR "HIPAA" OR "MiFID" OR "GDPR") -jobs -consulting

("business analysis" OR "requirements") ("lessons" OR "how we" OR "case study") ("elicitation" OR "stakeholder") -jobs -course

Mistakes that cost the most time

1. Not establishing which kind of BA the role needs

   Requirements analysis, data analysis, and process improvement are three different jobs sharing one title. A BA who writes specifications may never have written SQL; a data-leaning BA may never have run a requirements workshop. The candidate pools barely overlap, and a job description that does not distinguish them attracts all three and satisfies none.

2. Underestimating domain knowledge in regulated sectors

   In banking, insurance, and healthcare, the regulatory and product knowledge frequently matters more than generic analysis skill. A strong BA without domain grounding spends months learning terminology, rules, and system landscape that a domain-experienced candidate already carries. Where the domain is complex, it is the requirement rather than a preference.

3. Assuming platform experience transfers

   SAP, Salesforce, Workday, and ServiceNow functional analysts are platform specialists, and even within a platform the module matters — an SAP FICO consultant is not an SAP MM consultant. Treating these as interchangeable BA roles produces candidates who cannot configure the system they were hired to work on.

4. Confusing business analysts with product owners

   In agile organisations much traditional BA work sits with the product owner, and the titles are used inconsistently across companies. Searching only for Business Analyst misses people doing exactly that job under a different label, and vice versa. Search both and judge on the work described rather than the title.

5. Screening on methodology keywords

   Agile, waterfall, Scrum, and SAFe appear on nearly every BA CV, and the words say little about capability. What discriminates is how someone handles ambiguity, conflicting stakeholder demands, and incomplete information. Methodology familiarity is easy to acquire; stakeholder judgement is not.

6. Ignoring that BA is often a transition role

   Many business analysts arrive from operational roles within the same domain — an underwriter becoming an insurance BA, a nurse becoming a clinical systems analyst. These people bring domain depth that pure analysts lack, and because their history is not in analysis, keyword-driven screening rejects them systematically.

Common questions

What job titles should I search for when hiring a business analyst?

It depends which of the three BA disciplines you need. For requirements work, search Business Analyst, Requirements Analyst, Business Systems Analyst, and Product Owner, since agile organisations often place this work with the PO. For data-leaning roles, Data Analyst, BI Analyst, Reporting Analyst, and Insights Analyst. For operational improvement, Process Analyst, Continuous Improvement Analyst, and Lean Six Sigma roles. Platform-specific work uses its own titles — SAP Functional Analyst, Salesforce Business Analyst, Workday Analyst — and that experience is much less transferable than it appears.

What is the difference between a business analyst and a data analyst?

A traditional business analyst elicits requirements, documents processes, and bridges business stakeholders and technical teams, producing specifications and user stories. A data analyst queries data and builds reporting to answer questions, producing dashboards and analyses. The confusion arises because many organisations use Business Analyst for both, particularly in retail and e-commerce where the title often means SQL and reporting. Many BAs have never written SQL and many data analysts have never run a requirements workshop, so establishing which the role needs is the most important step before sourcing.

Do business analyst certifications matter?

The IIBA credentials — CBAP and CCBA — are more meaningful than most because they require documented hours of actual business analysis practice rather than only an examination, which makes them an experience marker. PMI-PBA is similar. Lean and Six Sigma belts indicate structured training in process improvement and usually a completed project, which is relevant where the role is operational rather than software-focused. Methodology keywords such as Agile, Scrum, and SAFe appear on nearly every CV and say very little, since familiarity is easy to acquire.

How much does domain knowledge matter for a business analyst?

In regulated and technically complex sectors, often more than analysis skill. A business analyst in banking needs to understand the products, the regulatory reporting requirements, and the system landscape; one in healthcare needs clinical workflow and compliance knowledge. These take months to build, and a strong generalist will be slower to contribute than a domain-experienced candidate with less polished analysis technique. In simpler domains the reverse holds and analysis skill dominates. Establishing which situation applies determines whether the search should prioritise domain or discipline.

Where can I find business analysts outside LinkedIn?

IIBA chapters run local events and publish member and volunteer activity, identifying practitioners committed to the discipline. For platform specialists, the vendor communities are the strongest source — Salesforce Trailblazer, SAP Community, and ServiceNow forums have visible, active participants with demonstrable expertise. An underused pool is people transitioning from operational roles in the same domain, such as underwriters moving into insurance BA work or clinicians into clinical systems analysis; they bring domain depth that keyword screening systematically rejects.