Only 70 profiles separate the two most-listed skills among candidates registered on MyInternships.in. Python appears on 21,874 profiles and SQL on 21,804, out of 55,557 candidate profiles that list skills, counted on 1 Oct 2026.
A gap that small is effectively a tie, and for employers a tie is more informative than a runaway winner. It tells you that the language people associate with programming and the language people associate with databases are now equally common entries on an early-career profile.
How close the two really are
Each skill sits on roughly 39% of the profiles we counted: 39.4% for Python and 39.2% for SQL. Nothing else comes near them. Excel, in third place, is listed by 16,153 candidates, and JavaScript, in fourth, by 11,695.
One point about method before reading further. A candidate who lists five skills is counted five times, once under each skill, so these shares overlap and do not add up to a whole. Our count also does not tell us how many people list Python and SQL together, so we will not guess at that.
| Where | Python | SQL | Which leads |
|---|---|---|---|
| All India | 21,874 | 21,804 | Python, by 70 |
| Bengaluru | 2,458 | 2,440 | Python |
| Hyderabad | 1,968 | 1,974 | SQL |
| Pune | 1,778 | 1,933 | SQL |
| Chennai | 1,550 | 1,487 | Python |
| Delhi | 1,162 | 1,223 | SQL |
| Mumbai | 899 | 891 | Python |
| Kolkata | 414 | 378 | Python |
The lead changes hands from city to city
The national tie hides small local differences. In Pune, SQL is clearly ahead: 1,933 profiles against 1,778 for Python. Delhi leans the same way, 1,223 to 1,162. Hyderabad is almost perfectly level, with SQL ahead by six profiles.
Chennai and Kolkata tilt towards Python, while Bengaluru and Mumbai are within a rounding error of even. The smaller cities in our data follow no single pattern either. SQL is ahead in Noida, Gurugram, Jaipur, Indore and Lucknow, and Python is ahead in Ahmedabad and Nagpur.
We would not read a grand theory into this. The practical point is narrower: wherever you hire, neither skill is the rarer one. If your shortlist is thin, the cause is unlikely to be that you asked for Python or for SQL.
What a tie at the top does to your job description
When about four in ten profiles carry a keyword, that keyword stops filtering. A job description that says "Python and SQL required" describes a very large part of the pool, and it will attract applications in proportion.
That is good news for volume and bad news for sorting. The line on your JD that feels most specific to you is, on our platform, the least distinguishing thing you can ask for. The skills that separate candidates sit further down the list, where the counts are much smaller.
Consider what the role really needs beyond the two headline languages. Does the person have to model data, write a report someone else relies on, clean a messy export, or maintain a script after the author has left? Those needs are what should shape the wording.
Screening when both keywords are on almost every profile
If a keyword cannot sort candidates, evidence has to. A few low-cost steps work well for entry-level analyst and developer roles:
- Ask for one artefact. A query, a notebook or a short script the candidate wrote and can explain is worth more than the skill tag.
- Use a small practical task. Give a tiny table and a question that needs a join and a grouped summary. Keep it short enough to finish in one sitting.
- Ask where the skill was used. A course project, a college assignment and an internship are all valid answers, but they are different answers.
- Separate reading from writing. Some roles only need a person to read and adapt existing queries. Say so, and you will widen your pool honestly.
Our employer tools and the guides in employer resources cover screening questions and JD structure in more detail.
What these counts can and cannot tell you
These figures describe what candidates registered on MyInternships.in choose to write in the skills section of their profile. They are not a test score, and they are not a measurement of the Indian labour market as a whole.
A profile that lists SQL may belong to someone who has written production queries or to someone who finished one module in a course. The count treats them alike. The same applies to Python, where a tag can cover anything from a first loop to a deployed service.
What the data does show reliably is relative supply of a label. Two labels listed almost equally often will give you applicant pools of similar size, and that is the planning input most hiring managers lack.
Using the tie when you plan a hire
Treat Python and SQL as the entry ticket, not the selection criterion. Write the JD around the task, name the one or two secondary skills that truly matter, and decide in advance what evidence you will accept.
If you are about to open an analyst or developer internship, you can hire interns through MyInternships.in and reach candidates who already list both skills, then let a short task do the sorting that keywords cannot.


