Business analysis sits at the intersection of data, business strategy, and communication. You are the person who understands what the business needs, translates that into something technical teams can build, and then confirms that what was built actually solves the original problem.
Most BA roadmaps treat this as a pure technical learning path. That is wrong. The technical skills are learnable in a few months. The business thinking and communication skills are what take longer and what actually differentiate strong BAs from mediocre ones.
If you are preparing to interview for a BA role, Intervue.io connects you with experienced business analysts for one-on-one mock interviews. Real questions, specific feedback. Visit intervue.io.
What a Business Analyst Actually Does
Before the roadmap, a grounding point that most learning resources skip.
A business analyst is not primarily a data person. You are a problem-framing person. Your job is to figure out what problem actually needs to be solved, whether it matches what the stakeholder thinks needs to be solved, and what success looks like before anyone writes code or runs a query.
The tools come second. SQL helps you pull data. Excel helps you analyse it. Power BI helps you communicate it. But none of these matter if you have framed the wrong problem or cannot translate your findings into a decision someone will act on.
This distinction changes how you learn. You do not start with SQL. You start with understanding how businesses make decisions and what data they use to make them.
Stage 1: Business Acumen and Analytical Thinking (3 to 4 weeks)
This stage has no certifications and no software. It is about building the mental model that all the technical tools sit inside.
Read about how businesses measure success. Understand what a KPI is and why different businesses use different ones. Learn the difference between a vanity metric (looks good, does not drive decisions) and an actionable metric (directly informs what to do next). Read case studies from the industry you want to work in: e-commerce, BFSI, SaaS, consulting, healthcare.
Practice structuring problems. Take a business situation, write down what is known, what is unknown, what needs to be true for the outcome to change, and what the next question to ask is. This sounds simple. Doing it rigorously is the foundation of everything a BA does.
The skill you are building here: the ability to go from a vague business complaint ("sales are down") to a structured problem statement ("sales are down 18% in Q3 in the South India region for products priced above ₹5,000, which accounts for 40% of total revenue decline").
Stage 2: Excel for Business Analysis (3 to 4 weeks)
Start with Excel because almost every company uses it and because understanding how data is organised in spreadsheets makes SQL and Power BI easier to learn.
What you need to know at the level that actually matters in interviews and on the job: pivot tables, VLOOKUP and XLOOKUP, INDEX MATCH for more flexible lookups, IF and nested IFs for conditional logic, SUMIF and COUNTIF for aggregated analysis, data cleaning functions (TRIM, TEXT, LEFT, RIGHT, MID), basic charting, and Power Query for importing and transforming data from external sources.
The practical test: take a messy real-world dataset, clean it in Excel, build a pivot table that answers a business question from it, and create a chart that communicates the finding clearly to someone who does not work with data. If you can do this without looking anything up, you know Excel at the right depth for a BA role.
Stage 3: SQL for Business Analysts (4 to 6 weeks)
SQL is the second most important skill for a BA after business thinking and the most commonly tested technical skill in BA interviews at product companies, GCCs, and BFSI firms.
The depth you need: SELECT, WHERE, GROUP BY, ORDER BY, JOINs across multiple tables, aggregate functions (COUNT, SUM, AVG, MIN, MAX), subqueries, CTEs (Common Table Expressions), and window functions (RANK, ROW_NUMBER, LAG, LEAD, PARTITION BY).
The specific thing most BA candidates underinvest in: window functions. These are the queries that appear in interviews and that distinguish BAs who can do meaningful analysis from those who can only write basic queries. Practice them deliberately.
The framing that separates strong BA SQL practice from generic SQL practice: always write queries to answer a specific business question, not to practise syntax. "Find the top 10 customers by revenue in Q3" is a business question. "Write a query using GROUP BY" is a syntax exercise. The first kind of practice builds the muscle you need in interviews.
PostgreSQL is free and standard. Use it on real-ish datasets from Kaggle or Google's public BigQuery datasets.
Stage 4: Data Visualisation and Power BI (3 to 4 weeks)
A BA who can pull data and analyse it but cannot communicate findings visually is only doing half the job. Dashboards that stakeholders actually use and trust are the output.
Pick Power BI for most BA roles in India. It is in the majority of BA job descriptions, integrates with the Microsoft ecosystem that dominates enterprise environments, and is what interviewers expect. Tableau is relevant at companies with US-facing data teams and at some large product companies. Know one well rather than both superficially.
What to learn in Power BI: connecting data sources (Excel, SQL databases), the data model and relationships between tables, DAX for calculated measures (SUM, CALCULATE, DIVIDE, time intelligence functions), building interactive dashboards with filters and slicers, and publishing and sharing through Power BI Service.
The design principle that matters more than any feature: every dashboard should answer a specific business question. The title of the dashboard should be the question it answers. "Why did North India sales decline in Q3?" not "Sales Dashboard - September." If you cannot articulate the business question your dashboard answers, the dashboard is not done yet.
Stage 5: Requirements Gathering and Documentation (2 to 3 weeks)
This is the stage most self-taught BAs skip and the one that product companies and consulting firms specifically probe in interviews.
Requirements gathering is the process of understanding what stakeholders actually need (which is often different from what they ask for), documenting it in a way that development teams can build from, and managing changes to those requirements throughout the project.
What you need to understand: user stories (As a [user], I want [feature], so that [benefit]), acceptance criteria (what does done look like), BRDs (Business Requirements Documents) and FRDs (Functional Requirements Documents) at a structural level, use case diagrams, process flow mapping with tools like Lucidchart or Visio, and the difference between functional and non-functional requirements.
The practical skill: take a real business problem (a company wants to build a customer feedback system), write 5 user stories with acceptance criteria for it, and document the data requirements. This exercise reveals whether you understand what requirements gathering actually produces.
Stage 6: Agile and Project Delivery Basics (2 to 3 weeks)
Most software projects at product companies and IT firms run on Agile. As a BA, you are not the scrum master but you work closely with one. Understanding Agile ceremonies and how BAs contribute to each one is expected at product companies and consulting firms.
What you need to know: the Scrum framework (sprints, sprint planning, daily standups, sprint review, retrospective), backlog grooming and how BAs write and prioritise stories, how requirements evolve across sprints, and Kanban as a lighter alternative to Scrum for some teams.
You do not need a formal certification at junior level. A practical understanding of how Agile teams work and your role within them is sufficient to pass BA interviews. CBAP (Certified Business Analysis Professional) matters at senior level. Entry and mid-level roles do not require it.
Stage 7: Communication and Stakeholder Management (Ongoing)
This is the stage with no end date because it develops through actual practice with real stakeholders.
What it means practically: you can take a complex analysis and communicate the key insight to a non-technical stakeholder in two sentences. You can run a structured meeting where decisions are made, not just discussed. You can push back on a requirement that is poorly defined without making the stakeholder defensive. You can write a concise, clear summary document that a senior leader reads and acts on.
The fastest way to build this before you have the job: present your data projects out loud as if you are presenting to a non-technical audience. Record yourself. Fix the parts where you use jargon, go too deep into methodology before stating the insight, or fail to connect the finding to a recommendation.
The Skills That Separate Strong BAs From Average Ones at Interviews
Product companies and consulting firms test for two specific things that most candidates underinvest in.
The first is structured thinking under ambiguity. BA interview questions are often deliberately vague: "Our mobile app's engagement dropped last month. How would you investigate this?" Strong candidates structure the problem before jumping to SQL. They ask what engagement means (DAU, session length, feature usage), what "dropped" means (how much, for which segments, on which platforms), and what else changed in the same period. Weak candidates jump straight to "I would write a query to pull the data."
The second is business framing of technical work. Not "I ran a cohort analysis on user retention" but "I ran a cohort analysis on user retention because the hypothesis was that users who completed onboarding had higher 30-day retention, and we found that was true for mobile users but not for web users, which changed our product roadmap."
The Timeline
6 to 8 months of consistent work at 2 to 3 hours per day gets most people to junior-ready. Candidates with Excel and some data background can do it in 4 to 5 months.
The variable is real projects. Building dashboards on real datasets, writing user stories for real product problems, and presenting your findings out loud are what close the gap between knowing the skills and performing them in an interview.
FAQs
Do I need a degree to become a business analyst? No. Product companies and IT firms hire BAs based on skills, portfolio, and interview performance. A relevant degree helps get through initial screening at large companies but is not required. Strong SQL, Power BI, and the ability to frame business problems clearly open most doors.
Should I learn SQL or Python first as a BA? SQL first. SQL is tested in almost every BA interview. Python is useful for more advanced analytics and data manipulation but is not required for most BA roles. Once SQL is solid (3 to 4 months), Python can be added for roles at product companies with heavier analytics requirements.
Is Power BI better than Tableau for a BA in India? Power BI for most BA roles in India. It dominates enterprise job descriptions, integrates with Microsoft Office which most companies use, and is what interviewers expect to see. Tableau is relevant for product companies with US-facing data teams.
What is the most important BA skill for interviews at product companies? Structured problem-framing. Before you demonstrate any technical skill, you need to show that you can break down a vague business problem into a clear, answerable question. Candidates who jump to SQL before framing the problem consistently score lower than those who structure the problem first.
Do I need a CBAP certification to become a business analyst in India? Not at junior level. CBAP requires 7,500 hours of BA experience before you can even apply. At entry and mid-level, employers value demonstrated skills (SQL proficiency, a Power BI portfolio) over certifications. CBAP matters at senior level and in consulting environments.
How can I prepare for a Business Analyst interview? Along with preparing SQL, Excel, Power BI, and business case questions, take a mock interview on Intervue.io with an experienced Business Analyst who is more senior than you and works at the kind of company you are targeting. This gives you a chance to practice real interview scenarios, improve your problem-framing and communication, and get specific feedback on where you need to improve before the actual interview.
