Ask ten students what a business analyst does and most will describe a data analyst. The profiles on MyInternships.in show the same confusion: Excel is listed by 16,153 candidates and SQL by 21,804, but Business Analysis by 106 and Requirement Gathering by 42.
These are counts of listed skills from 55,557 profiles on our platform on 1 October 2026. They show wording choices as much as ability, and they are about our candidates, not the country.
The job is translation
A business analyst sits between people who have a problem and people who build the solution. The sales head says the quoting process is too slow. The developers need to know exactly what to build. The analyst finds out what "too slow" means, where the delay is, and what a better process must do.
An intern's day includes sitting in meetings and taking careful notes, drawing how a process works today, writing down what a new screen or report must do, and checking with the requester that you understood correctly. You will rewrite documents several times as people change their minds.
Later in a project you help test. Does the thing that was built match what was asked for? You write the test cases, run them and log what fails.
A data analyst answers questions with numbers. A business analyst defines what should be built or changed. Both use Excel and sometimes SQL, which is why the titles blur. If a listing is mostly about dashboards and queries, it is a data role wearing a BA title. If it talks about stakeholders, requirements and user stories, it is the real thing.
What employers look for
- Structured thinking: breaking a vague complaint into specific, testable statements.
- Requirement gathering: asking questions that reveal what people need, not just what they say.
- Documentation: process maps, user stories with acceptance criteria, clear meeting notes.
- Excel: for sizing a problem and checking data.
- SQL and Power BI: helpful for verifying claims yourself.
- Jira and Agile practice: how work is tracked in sprints and what a backlog is.
Interviews usually include a case: "A college canteen has long queues at lunch. How would you approach it?" They are listening for your questions more than your answer.
Tools are everywhere; the discipline is rarely named
| Skill listed | India | Bengaluru | Hyderabad | Pune | Chennai | Delhi | Mumbai |
|---|---|---|---|---|---|---|---|
| Excel | 16,153 | 1,549 | 1,239 | 1,364 | 1,028 | 1,074 | 839 |
| SQL | 21,804 | 2,440 | 1,974 | 1,933 | 1,487 | 1,223 | 891 |
| Power BI | 9,275 | 1,022 | 765 | 919 | 667 | 623 | 445 |
| Jira | 201 | 17 | 16 | 23 | 16 | 11 | 13 |
| Agile | 125 | 23 | 8 | 17 | 12 | under 5 | under 5 |
| Business Analysis | 106 | 13 | 14 | 5 | 9 | 11 | under 5 |
| Requirement Gathering | 42 | under 5 | 5 | under 5 | 6 | 7 | under 5 |
The top three rows are among the most listed skills on our platform. The bottom four are listed by a few hundred candidates in total: Jira 201, Agile 125, Business Analysis 106, Requirement Gathering 42.
In several metros the count for Requirement Gathering is below five. Hyderabad shows the most Business Analysis profiles, at 14, narrowly ahead of Bengaluru.
The fair interpretation is that many candidates have the tools and have never described the craft. If you have gathered requirements for a college event system, a family business or a club website, that is relevant experience, and naming it properly would set your profile apart from most here.
A case study you can show
Analysts cannot upload code, so produce a document.
- Choose a real process you can observe: hostel room allotment, a shop's billing, library book returns.
- Interview two or three people involved and note where it goes wrong.
- Draw the current process and a proposed one.
- Write six to ten user stories with acceptance criteria.
- Estimate the benefit using whatever figures you can honestly gather.
Keep it to four or five pages. A reviewer should be able to read it in ten minutes and see how you think. Share it as a link on your résumé, which the resume builder supports.
Reading the listing carefully
Because the title is elastic, read every responsibility line. A genuine business analyst listing mentions stakeholders, documentation, process or product, and names the team you will support.
Be alert to roles that use the title for cold calling, lead generation or field sales with targets. Those are sales jobs, legitimate in themselves, but mislabelled. Also be wary if the listing asks for payment towards training or a certificate.
Ask in the interview what a typical deliverable looks like. If nobody can describe one, the role may not be defined yet.
Applying as a communicator
Your application is itself a writing sample. Keep the covering note to five or six clear sentences, free of jargon. Mention the case study and one thing you learned from the people you interviewed.
On the résumé, describe outcomes of coordination: "collected requirements from three departments and produced a single agreed specification". Group projects, event management and student-body roles all count when described concretely.
Analyst roles appear across consulting, technology and operations teams, and at startups where one intern may cover both business and data analysis. The Internship of the Day is another place to check regularly.
When your case study is ready to share, browse current business analyst internships and apply where the responsibilities describe real requirement work.


