Nationally, Python edges out SQL on MyInternships.in by just seventy profiles: 21,874 against 21,804. In Pune the order flips, with 1,933 candidates listing SQL and 1,778 listing Python. Delhi shows the same reversal.
If you are hiring a data analyst intern, that near-tie matters. SQL is not a niche skill you must hunt for. It is one of the two most common words on fresher profiles on our platform, which shifts your problem from finding candidates to sorting them.
The analyst toolkit, counted
All figures here describe candidates registered with us as of 1 October 2026 and what they wrote in their skills section. Nothing below has been verified by a test, and one candidate can appear under many skills.
| Skill listed on profile | All India | Pune | Bengaluru | Hyderabad | Delhi | Mumbai |
|---|---|---|---|---|---|---|
| SQL | 21,804 | 1,933 | 2,440 | 1,974 | 1,223 | 891 |
| Excel | 16,153 | 1,364 | 1,549 | 1,239 | 1,074 | 839 |
| MySQL | 9,411 | 952 | 1,088 | 883 | 526 | 416 |
| Power BI | 9,275 | 919 | 1,022 | 765 | 623 | 445 |
| Tableau | 4,054 | 404 | 502 | 336 | 269 | 229 |
| Data Analysis | 3,390 | 250 | 290 | 217 | 193 | 175 |
Excel is on 16,153 profiles, about 29 per cent of the 55,557 that list skills. Power BI is on 9,275 and Tableau on 4,054; dividing the first by the second gives about 2.3, so Power BI is listed more than twice as often. "Data Analysis" as a phrase appears only 3,390 times. Far more students name the tools than name the job.
That last point is useful. A candidate who lists SQL, Excel and Power BI but has never framed themselves as an analyst may still be exactly who you want. Search by tool, not by title.
Tableau shop or Power BI shop?
If your dashboards live in Power BI, the supply on our platform is comfortable in every large city in the table. If you use Tableau, the pool is under half the size, and you should decide in advance whether prior Tableau use is a requirement or a preference.
In practice, a student who has built a sensible dashboard in one tool learns the other quickly. What does not transfer is judgement: choosing the right chart, knowing when a total is misleading, noticing that a filter has silently removed a third of the rows. Hire for that and let the tool follow.
Profile signals worth your time
- A question, not a dataset. "Analysed which product categories drive repeat purchases" is better than "performed EDA on a retail dataset".
- A finding stated in words. Analysts are paid to say what the numbers mean. A project description with no conclusion is a warning.
- Evidence of dirty data. Anyone who mentions handling duplicates, missing values or inconsistent categories has done real work at least once.
- A dashboard you can open. Screenshots are acceptable; a public link is better.
Be cautious with profiles where every project uses the same famous practice datasets. They show the candidate can follow along, not that they can start from a blank page.
The practical test: one dirty sheet, three questions
Prepare a spreadsheet of invented sales records with a few thousand rows. Plant four problems in it: some duplicated orders, a city spelt three ways, a handful of negative quantities, and one month with missing data.
Do not tell candidates about the problems. Ask only this:
- Which city had the highest revenue last quarter?
- Which product category is growing fastest?
- What is one thing in this data the sales head should worry about?
Allow two hours and any tool: Excel, SQL, Power BI, Python. Ask for a single page with the answers, one chart and a list of assumptions.
What separates the top submissions
Weak candidates answer question one with the wrong city, because the city spelt three ways has been split into three smaller totals. Average candidates get the right answers but say nothing about the data. Strong candidates open with a line such as "I removed duplicated order IDs and merged three spellings of one city; the missing month makes the growth figure unreliable."
The third question is the real interview. There is no planted answer. Some will point to the negative quantities, some to dependence on one category, some to the missing month. You are looking for a defensible observation explained in plain language.
Then check the chart. Is it the simplest chart that makes the point? Are the axes labelled? A cluttered dashboard with a dozen visuals is a worse answer than one clean bar chart.
Finish with a short conversation. Ask the candidate to write, live, a query or formula that answers a fourth question on the same sheet. Grouping, joining and filtering are enough; you do not need window functions from an intern.
After the offer
Give an analyst intern one recurring report to own within the first fortnight. Ownership of a small real output teaches more than shadowing, and it gives you something concrete to assess at the mid-point review.
Also give them access. Many analyst internships stall because database permissions take weeks. Sort that out before day one.
To see how analyst supply compares in your city, look at recruiter intelligence, and for role templates see employer tools. When you are ready, start hiring analyst talent on MyInternships.in and send every shortlisted applicant the same sheet.


