By Shivanshi Sehgal - Career researcher and writer Business analyst skills fall into three groups: technical (SQL, Excel, process maps, requirements writing, a BI tool, Jira), domain (how a bank, hospital, retailer or ERP system really works) and behavioural (finding the real need, handling stakeholders, writing clearly). Most of the skills needed for a business analyst role are table stakes. What gets you picked is one core skill, one multiplier skill and proof that another person can check. That combination is a high-value skill portfolio, and the choices behind it are what open high income opportunities and earlier financial freedom.
The short version
- Learn the table stakes first: Excel, SQL basics, requirements and user stories, process maps, Jira. Then add one multiplier, either one domain or SQL with a BI tool.
- Judge every skill by the proof you can show. A reviewed requirements pack beats a certificate.
- Next step: read three live postings for the employer type you want, tally the repeating skills, and build one artifact for the top two.
IIBA, the body behind the BABOK Guide, says a business analyst is anyone who performs business analysis tasks, whatever their job title. So the skills below also help if your title is business systems analyst, process analyst, product owner or even data analyst. This guide sits in Skills. To decide whether the career itself suits you, read is business analyst a good career in India. To get the first job, use how to become a business analyst at entry level in India. To compare with analytics, see business analyst vs data analyst.
Skills required for a business analyst, in one table
Table stakes are skills you need just to be considered. Differentiators decide between two candidates who both pass the first screen. This split is our reading of live postings and fresher guides, not an official list, so check postings for your own target.
| Skill | Group | Level | What to know |
|---|---|---|---|
| Excel (pivots, lookups, clean data) | Technical | Table stakes | Named in every fresher guide we read. Without it you are filtered out early. |
| SQL basics (SELECT, WHERE, JOIN, GROUP BY) | Technical | Table stakes | A senior bank posting we read asks for strong SQL and knowledge of data models. Freshers are usually asked for the basics. |
| Requirements writing: BRD, FRD, user stories, acceptance criteria | Technical | Table stakes | This is the product of the job. Weak writing here ends the conversation. |
| Process mapping (flowcharts, BPMN) | Technical | Table stakes | Shows you can turn a messy process into steps a business person and a developer both follow. |
| Jira and Confluence | Technical | Table stakes | Where the backlog and the documents live in many teams. Learn the basics, not every plugin. |
| A BI tool (Power BI or Tableau) | Technical | Differentiator, becoming table stakes | Lets you check a number yourself instead of waiting for a data team. |
| Python (optional) | Technical | Differentiator | Useful when the work touches large data or automation. Not needed to get a first BA role. |
| Domain depth in one sector | Domain | Differentiator | Two candidates with the same tools are separated by who understands the business. |
| Elicitation: finding the need behind the request | Behavioural | Differentiator | The hardest skill to fake and the one that clients and managers remember. |
| Negotiation and scope pushback | Behavioural | Differentiator | Matters more as you get senior, because you start owning decisions. |
| Clear written English | Behavioural | Table stakes that many miss | Short, exact sentences beat fancy ones. Every artifact you build is writing. |
What IIBA's own exam weights say about the job
IIBA publishes the weights of its CCBA exam by knowledge area. They test knowledge, not hours at work, but they show where the profession puts its weight.
Elicitation, analysis and requirements upkeep together carry 70% of that blueprint. The core of the work is finding needs and keeping requirements accurate, not tool tricks. Tools help you do that faster.
Honest take
Most "top skills" lists give a flat list of 9 to 13 skills with no order and no proof. That is why two people with the same list can get very different results. The list is the entry ticket. The proof and the pick of one multiplier decide the outcome.
Technical skills required for a business analyst, and how deep to go
For each skill, learn enough to start, then know what a differentiator looks like.
Technical skill 1
Excel
Technical skill 2
SQL
Technical skill 3
Requirements documents and user stories
Technical skill 4
Process modelling (BPMN) and basic diagrams
Technical skill 5
A BI tool
Technical skill 6
Jira and Confluence
Technical skill 7
Python (optional)
Technical skill 8
AI drafting and checking
Domain skills: BFSI, healthcare, retail and ERP
Tools can be learned faster than a sector. Understanding a sector takes longer, which is why it is the best multiplier for many analysts. You do not need a job in the sector to start. You need its vocabulary, one full process, and one person who works there to check your notes.
Banking, finance, insurance (BFSI): Money, risk and rules
Learn: The words of the product: account opening, KYC, loan steps, claims, settlement. Learn one end-to-end process in plain language.
Show: A one-page walk-through of one real customer journey with the steps where things go wrong.
Healthcare and pharma: Records, claims and care steps
Learn: How a patient or claim moves between hospital, insurer and records. Care with private data is part of the job.
Show: A process note on one admission-to-billing flow, with anything personal removed.
Retail and e-commerce: Orders, returns and delivery
Learn: Cart, payment, fulfilment, returns, refunds. Most pain sits at handoffs between teams.
Show: A funnel or returns analysis with a requirement list that follows from what you found.
ERP and enterprise systems (SAP and similar): Finance, supply and people processes inside one system
Learn: Core flows such as buy-to-pay and order-to-cash, and how a change request travels through configuration and testing.
Show: A gap note: what the business does today, what the system standard does, and the difference.
Pick one sector first. A long list of sectors reads as no sector. You can change later, but each switch costs some trust, so choose where you can get access to real people and real processes.
Behavioural skills, and the English you really need
People describe a solution ("add a button") when the need is a problem ("approvals take too long"). Ask what happens before and after, what goes wrong, and what the cost of waiting is. Then say it back in one sentence and ask if you got it right.
IIBA lists "stakeholder" as one of six core ideas of the whole profession, next to change, need, solution, value and context. In practice: write down who is affected, who decides, who can block, and talk to each in the way that suits them.
A sponsor asks for "one more small thing". The skill is to restate the goal, show the trade-off in time or cost, and offer a later release. You are not saying no. You are making the choice visible.
Meeting notes that list decisions, owners and open questions. An email that opens with the ask. A requirement with one meaning only. If a busy manager can act on it in two minutes, it works.
Keep a workshop on topic, make quiet people heard, and close with agreed next steps. You will be asked to present findings long before you are asked to lead a team.
On English: one fresher guide puts it well, saying strong communication does not necessarily mean using complicated English. Use short sentences, one idea each, and put the decision or the ask first. Practise by writing a one-page summary of any artifact and then saying it aloud in two minutes. Written English is the skill most analysts under-train, and every document you produce is a sample of it.
Core skill + multiplier skill + visible proof
A skill list does not set you apart. A stack does. Pick the three parts below and build in that order.
Core skill
Turning a vague need into a clear requirement
Elicitation plus requirements writing. This is the work itself, so it has to be strong.
Multiplier skill
One skill that makes the core worth more
SQL with a BI tool, or one domain such as BFSI, or ERP process knowledge. Pick one first. A second multiplier comes later.
Visible proof
Something another person can check
A requirements pack or case note that a working analyst has reviewed. Not a course certificate.
Fits banks, NBFCs and insurers. Proof: a loan-onboarding or claims process note reviewed by someone who has worked in it.
Fits product companies, startups and e-commerce teams. Proof: one analysis that tests a business claim, plus the requirements that follow from it.
Fits IT services and consulting teams that implement enterprise systems. Proof: a gap note between current process and system standard.
If you are unsure which multiplier fits your background, your time and your money, a conversation about continuous career guidance can help you make the skill choices that unlock high income opportunities, before you spend on courses.
How the skill mix changes by employer type
The same title asks for a different mix depending on who hires. This table is our reading of postings and fresher guides. Open three live postings for your target employer type and compare.
| Employer type | Skills weighted most | How you may be tested | Watch out |
|---|---|---|---|
| IT services and delivery firms | Requirements writing, Jira and Confluence, client-facing communication, fast learning of a new client domain. | Often a scenario or case exercise, plus a light tool check. | Breadth is easy to get here. Depth in one domain is what you must add on purpose. |
| Banks, NBFCs and insurers | Domain vocabulary, SQL and data models, testing support (test cases, UAT), strict documentation. The senior bank posting we read lists SQL, JIRA, Confluence, Visio, Excel and stakeholder management together. | Domain questions come early. Rules and process knowledge are checked. | The domain bar is higher, and moving sector later means rebuilding trust. |
| Product companies and startups | SQL, a BI tool, comfort with numbers, short written specs, agile ways of working, ability to work with little supervision. | Expect a data task or a metric question, not only a documentation task. | Fewer roles carry the pure "business analyst" title. Look for product analyst and business systems analyst titles too. |
| Consulting and advisory firms | Structured problem solving, clear slides and memos, workshop skill, speed in new industries. | Case discussions, written summaries and communication under pressure. | Long hours and a steep climb. The next stage of advancement is a separate and harder filter. |
The proof-of-skill checklist
For each skill, build one thing, show it in a form others can check, and aim for the strong column. For the step-by-step build of a full mock project, use the entry guide linked above. This checklist is about judging the strength of each piece.
| Skill | Build | Show it as | Weak proof | Strong proof |
|---|---|---|---|---|
| Excel and data checking | A small workbook that answers one business question from a real or public data set. | The file, a one-paragraph note on the method and a list of what you could not check. | A course certificate or a screenshot of a pivot table. | A working file a stranger can open, follow and challenge. |
| SQL | Five to ten queries on one data set that test a claim. | The query text with a plain sentence under each saying what it proves. | Completion badge from a practice site. | Queries that found something a spreadsheet glance would miss, with the data source named. |
| Requirements writing | A requirements document and stories for one real process you can observe. | The document with scope and out-of-scope clearly marked. | A template with the names changed. | A document a working analyst or developer has read and marked up, with your fixes. |
| Process modelling | Current-state and future-state maps of the same process. | Both maps on one page, with pain points circled. | A tidy diagram of an invented process. | A map of a real process where the owner agreed the steps are right. |
| BI tool | One dashboard that supports one decision. | A link or PDF and three lines: the decision, the metric, the limit. | A page with ten charts and no question. | A page that someone used to change what they did. |
| Domain depth | A walk-through of one process in your chosen sector, in plain words. | A one-page note with terms explained. | A list of industry buzzwords. | A note a person who works in that sector says is correct. |
| Elicitation | An interview with one real person about a real problem in their work. | Your question list, what they said, what you first misunderstood and how you found out. | A role-play with a friend who agrees with everything. | A write-up where the real need was different from the first request. |
| Negotiation and stakeholder handling | A short case note on a time priorities clashed (college club, family shop, internship). | The options you set out and the choice that was made. | A claim of "good stakeholder skills" on a resume. | A named example with the trade-off written down. |
| Written and spoken communication | A two-minute spoken summary of one of your artifacts, plus a one-page written version. | A recording or live demo and the page. | Long text with no ask. | A summary that ends with the decision it supports, delivered without notes. |
When one piece is done, turn it into a truthful resume line with the Resume Skills Evidence Builder. Remove anything you could not explain in an interview.
The 3 Gates, applied to business analyst skills
Move to job applications only when all three gates are passed for your core skill and your multiplier skill.
One artifact for your core skill and one for your multiplier skill. Each must be something a stranger can open and judge.
Explain each artifact in 30 seconds to two minutes, in plain English, ending with the decision it would change.
Show the work to three people who do this job or hire for it. Write down their exact words on whether they would shortlist it and what is missing.
AI and business analyst skills: what it speeds up, what stays yours
- Turn a meeting recording into notes, decisions and open questions.
- Draft first-pass user stories and acceptance criteria from those notes.
- Suggest test cases and edge cases you may have missed.
- Draft a SQL query and explain it line by line.
- Make a first rough process diagram from a written description.
- Rewrite a long paragraph into short, clear sentences.
- Deciding which stakeholder version is the real need when they disagree.
- Noticing what nobody said because everyone thought it was obvious.
- Setting priority and holding scope when a sponsor pushes.
- Owning sign-off and being accountable for what is built.
- Checking every number and every claim before it goes out.
- Reading the politics and trust in a room.
Use it for notes, first stories and SQL drafts. Test every query on a small table where you already know the answer. Never paste private client data into a public tool, and follow your employer's rules.
More conversations with the people who do the work, earlier. This is the part a summary cannot do for you.
Build a record of contradictions found and requirements recovered. Direct AI workflows for your team, and write down how you check them.
The pressure is real but narrow. It lands first on junior work that is only notes, formatting and first drafts. It lands least on finding the need, handling conflict and owning decisions. Nobody can promise how fast tools will improve, so build the judgment layer now. Do not expect a fixed multiplier: AI raises your output only if it is pointed at a valuable problem and you can show the result.
ECBA, CCBA, CBAP and PMI-PBA: what each one asks for
| Credential | Meant for | What the issuer says | Our view |
|---|---|---|---|
| ECBA (Entry Certificate in Business Analysis) | Early-career professionals and career changers | IIBA says it needs no related work experience or professional development hours (IIBA blog, November 2023). The exam moved to include applied knowledge from 21 July 2025. The IIBA page lists a bundle price of "$395 or less" including membership, exam, practice exam and learning journey. | A reasonable signal of intent after you have real work to show. Not a substitute for it. Check the current handbook, because some chapter pages still mention 21 professional development hours. |
| CCBA (Certification of Capability in Business Analysis) | Analysts with a few years of work | IIBA: two to three years of work experience in the last seven years (3,750 hours) and 21 professional development hours in the last four years. | A step for after a first role. Not a fresher credential. |
| CBAP (Certified Business Analysis Professional) | Experienced analysts | IIBA: five or more years of work experience in the last ten years (7,500 hours), 35 professional development hours in the last four years and two professional references. The exam has 120 case-study and scenario questions in 210 minutes. You recertify every three years. | Worth planning for later in a BA career. Studying for it before you have the hours is a wasted gate. |
| PMI-PBA (Professional in Business Analysis) | Analysts on project-heavy teams | Issued by PMI. It is experience-based. We could not open PMI's own page to confirm the current hours, and other sites disagree, so check pmi.org before you plan around it. | Useful where employers already value PMI credentials. Ask the employers you want. |
| CBDA, AAC and CPOA | Specialists | IIBA also lists Certification in Business Data Analytics, Agile Analysis Certification and Certificate in Product Ownership Analysis. Check eligibility on iiba.org. | Read them as direction signals: data, agile delivery and product ownership. |
Rules and fees change. IIBA details above were read on iiba.org in October 2026. Fees are quoted in US dollars, so convert and check the current figure before you pay.
Rules for judging any business analyst course or certification
YouTube lessons, official documentation such as Microsoft Learn for Power BI, interactive SQL practice, and your own data sets. If you cannot finish the free version, a paid one will not fix that.
Most BA information is free. The paid part should give you a clear sequence, a person who marks your work, a group that keeps you going, or a credential that the target employer actually asks for.
A certificate says you attended. A reviewed requirements pack or analysis says you can do the job. Do both only if the employer wants the credential.
Check the instructor's recent real work, the last real update, the full syllabus, the exercises, who gives feedback, the refund terms and what past learners got. Avoid "best course" lists that depend on stars or affiliate pay.
Use 10% of the total education budget as a strict starting limit for any one paid credential, and treat anything above about 20% as needing course-specific evidence. A budget of Rs 10 lakh makes the starting limit about Rs 1 lakh. We found no law that requires a degree or licence to do business analysis, so avoid education loans for BA courses. A degree still helps at some campus-hiring employers, so treat it as one input, not the whole plan; skills and proof carry the rest.
Before paying, write down what you will build and who will review it. If the course cannot say, the money buys content you could find free.
Where these skills can take you, and how far each route scales
The routes are ordered by headroom, not by how common they are. Consulting leads because you control price and reach. The salaried ladder is where most people start, so it comes later on the list even though it comes first in time.
Scalable
Independent process and requirements consulting
You set the price, can repeat work with the same clients and later add other analysts. It needs years of domain trust first, so it comes after the salaried stage in time even though it has the most headroom.
Scalable with a business layer
Freelance analysis projects
Requirements packs, process maps and dashboards can be sold directly. Much of the work can be done remotely, which widens your client pool. Marketplace bidding turns into a race to the lowest price, and a new freelancer has little trust.
Scalable with a business layer
Product owner or product manager
The step often happens inside a company, from a role close to the product team. Entry is crowded.
Scalable with a business layer
Salaried analyst ladder (analyst, senior, lead)
A fixed pay ladder with steady learning. Growth beyond it comes from domain ownership and a side route.
Not so scalable
The documentation-only version of the job
Taking notes, formatting documents and passing them on is the work AI drafting tools take on first. It stays on the list because many first roles start here.
Two stages of competition
The first stage is the entry filter: a crowded pool of freshers, judged mostly on proof. The second is a separate climb later, from analyst to the person who owns a domain and is trusted with decisions. Clearing the first does not clear the second, and the move into product roles is a third, separate filter.
An ownership path exists. Once a sector trusts your work, you can sell process and requirements work to businesses directly. It scales because you set the price, repeat work with the same clients and can later bring in other analysts.
A closer fit may exist if numbers are what you enjoy. IIBA's own list of titles for people doing business analysis includes business systems analyst and data analyst, and both lean harder on SQL. The business analyst vs data analyst comparison explains the trade.
Basic sales and marketing for a business analyst who consults or freelances
In a job, your employer pays and your interviewer finds and trusts you through your proof and your communication. For consulting or freelance work, who pays changes: a small business owner, a startup, a product team short on capacity, or a larger firm that hires help. They find you through people they know, through case notes they can read, and through your past managers. The first sales skill to learn is positioning. Keep it simple, and promise no income.
Say who you help and with what, in one line. For example: "requirements and process maps for small lenders' loan onboarding". A narrow line makes referrals and pricing easier than "I do business analysis for anyone".
A set scope people can picture: one discovery conversation, a current-state map and a requirements pack. Put scope, price, timeline and revision limits in writing, take a deposit on larger work and price change requests separately.
Write short notes on problem, what you did and what changed, with names and private data removed. Do not invent numbers. If you have no measured result, describe the concrete change.
One real observation about their process, one link to relevant proof, one small question. Start with people who already know you: past managers, college seniors, family businesses. Ask happy clients for referrals while the result is fresh.
Talk about the result and the cost of leaving the problem alone before the fee. If someone hesitates, ask what is behind it before you drop the price. Raise rates as proof and demand grow.
How many of your conversations became a paid pilot. If it stays low, change the niche, the offer or the proof, not only the volume of messages.
If you freelance, check GST and Udyam rules on the official government portals. Thresholds change. If you stay in a salaried role, this layer matters mainly for the internal pitch and for a side route later.
Skill mistakes to avoid
A long tools line with no artifact looks like a course shopper. Pick the table-stakes set, then one multiplier, then prove them.
Python is optional for a first BA role. Weak requirements writing is not.
Pick a sector where you can talk to people who work in it. Access to a real process beats a fashionable name.
Elicitation and negotiation cannot be built without another person. A college club, a family business or a volunteer project counts.
Credentials help most when they sit behind real work, and only when the employer you want asks for them.
Your first test
Run a short test for as long as it genuinely takes. Some people need a few weeks, others a couple of months.
Open three live postings for the employer type you want and tally the skills that repeat.
Pick one core skill and one multiplier. Build one artifact for each, and pass the 3 Gates above.
Pay for a course or credential only after you can say what it adds beyond free material.
Each skill matters more at a later step. See the business analyst career path for titles, years and next moves.
For ERP and enterprise systems, read is SAP a good career.