Python is the most-listed skill among candidates on MyInternships.in, yet when it comes to backend frameworks the JavaScript runtime wins. Node.js is on 4,424 profiles. Flask is on 2,281 and Django on 1,279.
So the two Python web frameworks together are still listed less often than Node.js alone. For a team choosing whom to hire for server-side work, that mismatch between language popularity and framework popularity is worth understanding.
Three frameworks, three very different pool sizes
Our count covers 55,557 candidate profiles that list skills, as of 1 Oct 2026. Node.js appears on about 8.0% of them, Flask on 4.1% and Django on 2.3%. Anyone who lists more than one framework is counted under each.
Node.js is listed nearly twice as often as Flask and about 3.5 times as often as Django. Flask, the lighter of the two Python options, is listed about 1.8 times as often as Django.
| Where | Node.js | Flask | Django |
|---|---|---|---|
| All India | 4,424 | 2,281 | 1,279 |
| Bengaluru | 426 | 318 | 167 |
| Pune | 316 | 184 | 102 |
| Hyderabad | 290 | 232 | 134 |
| Delhi | 280 | 94 | 50 |
| Chennai | 241 | 174 | 77 |
| Mumbai | 179 | 99 | 43 |
| Ahmedabad | 92 | 44 | 54 |
Most Python listers do not name a web framework
Python is listed by 21,874 candidates. Flask's count is about a tenth of that and Django's is smaller again. Whatever the overlap between the groups, the arithmetic makes one thing certain: the large majority of profiles that say Python do not also say Flask or Django.
That fits what the rest of our data suggests about how Python is used by early-career candidates. NumPy and Pandas are each listed by more than eight thousand people, far more than either web framework. Much of the Python on our platform points towards data work, not web services.
If you post a "Python developer" role expecting backend engineers, expect many applicants whose Python experience is in notebooks. Name the framework in the JD to make the role clear.
The wording works in the other direction too. A JD that says only "backend developer" and names no language will draw mostly Node.js applicants on our platform, simply because that is where the framework-level supply is largest.
The city picture is uneven
Delhi shows the strongest Node.js skew. With 280 Node.js profiles against 94 for Flask, the gap there is about three to one, much wider than the national figure.
Hyderabad and Bengaluru are the most balanced. In Hyderabad, Flask at 232 is not far behind Node.js at 290, and Bengaluru has the largest Flask and Django counts of any city.
Ahmedabad is the one city in our data where Django, at 54, is listed more often than Flask, at 44. The numbers are small, so we would not build a hiring strategy on them, but a Django team there is less disadvantaged than the national ratio implies.
Choosing whom to hire for a Python backend
A Django shop looking at 1,279 profiles nationally has a narrow pool. The practical alternatives are close at hand:
- Flask users. They already understand routing, request handling and templating in Python. The move to a more structured framework is mostly about conventions.
- Python plus SQL. A candidate comfortable with both the language and relational data has the two hardest prerequisites. SQL is listed by 21,804 candidates.
- Node.js users with some Python. The concepts of an API, middleware and authentication carry across languages.
For an internship or a first job, any of these is a sensible starting point provided you budget time for onboarding.
Screening backend candidates on evidence
Framework tags tell you little about whether someone can design an endpoint that behaves well under bad input. A compact exercise does better. Ask the candidate to describe, or build, a small API with one resource: how it validates input, what it returns on failure, and how the data is stored.
Listen for whether they mention the database unprompted. Among backend-leaning tags on our platform, MySQL is listed by 9,411 candidates and MongoDB by 3,899, so most applicants will have touched one. The ones who can explain why they chose it are the ones to shortlist.
Ask, too, how they tested the service. A candidate who mentions sending bad requests on purpose, or checking what happens when the database is unavailable, has thought past the tutorial path, whichever framework they learnt on.
Limits of the comparison
We are reporting the words candidates use on MyInternships.in profiles. Someone who built a service with Express may write "Node.js", "JavaScript" or both, and someone who followed a Django tutorial may list it after a weekend. The counts cannot tell those apart, and they are not a survey of what Indian engineering teams run in production.
Turning the numbers into a hiring plan
If you hire for Node.js, you have the widest framework pool and should invest in a sharper screen. If you hire for Django or Flask, widen the requirement to "Python with any web framework" and plan to train.
See recruiter intelligence for related supply data and employer tools for JD help. When the role is ready, hire backend talent through MyInternships.in, or browse how similar openings are worded on the jobs page.


