MyInternships.in
Talent Data

TypeScript Is on 2,226 Profiles, JavaScript on 11,695: Reading the Gap

For every candidate on MyInternships.in who lists TypeScript, about five list JavaScript. The ratio varies by city, with Delhi and Kolkata ahead. What it means for web teams.

M
MyInternships.in Research Desk
4 min read849 words
Share this:
TypeScript Is on 2,226 Profiles, JavaScript on 11,695: Reading the Gap

Most modern web codebases we see in job descriptions are written in TypeScript. Most candidates who apply to them list JavaScript. Among candidates registered on MyInternships.in, JavaScript is on 11,695 profiles and TypeScript on 2,226.

That is a little over five to one. For engineering leads, the question is whether to treat TypeScript as a gate or as something a JavaScript developer learns on the job. Our numbers make a strong case for the second.

The ratio nationally and in the big cities

From 55,557 candidate profiles that list skills, counted on 1 Oct 2026, JavaScript appears on 21.1% and TypeScript on 4.0%. The TypeScript count is 19.0% of the JavaScript count. Our tally is per label, so anyone who writes both is in both columns.

WhereJavaScriptTypeScriptTypeScript as share of JavaScript
All India11,6952,22619.0%
Bengaluru1,31421816.6%
Pune98816616.8%
Hyderabad95913614.2%
Chennai73713918.9%
Delhi63415524.4%
Mumbai4398820.0%
Kolkata2255424.0%

Delhi and Kolkata are ahead of the national ratio

The spread between cities is wider than we expected. In Delhi the TypeScript count is 24.4% of the JavaScript count, and in Kolkata 24.0%. Both are well above the national figure.

Hyderabad is at the other end, at 14.2%, with Bengaluru and Pune a little under 17%. Bengaluru still has the most TypeScript profiles in absolute terms, 218, but relative to its large JavaScript base it is below average.

Delhi is worth a second look. It has fewer JavaScript profiles than Chennai yet more TypeScript ones, 155 against 139. A team there looking for typed-code experience has a denser pool than the city's overall size implies.

Why most JavaScript listers leave TypeScript off

Typed JavaScript usually enters a developer's life through a team project or a framework that expects it. A student who has built college projects alone may never have needed it.

Some candidates also see TypeScript as part of JavaScript and do not list it separately. So the 2,226 figure is best read as "candidates who think of it as a distinct skill", which is itself a mild indicator of experience with larger codebases.

Gate or train?

Requiring TypeScript as a hard filter cuts your reachable pool on our platform to under a fifth of the JavaScript group. For an internship or first job, that is a steep price for a skill that a competent JavaScript developer can acquire while working.

The fundamentals carry over entirely: functions, asynchronous code, modules, the browser or server runtime. What is new is describing the shape of data explicitly and reading compiler errors. Those are habits, and habits are learnt by doing.

A reasonable policy for junior roles is to make JavaScript the requirement and TypeScript a stated preference, and to say in the JD that the codebase is typed. Candidates who dislike the idea will not apply, and those who are curious will.

Testing aptitude for typed code

You can check readiness without requiring prior TypeScript. In a short exercise or conversation, try the following:

  • Show a function and ask what could be passed to it that would break it. Candidates who think about input shapes will adapt quickly.
  • Ask how they would describe the data returned by an API to a teammate. Precision here is the essence of typing.
  • Show a simple compiler-style error message and ask what it is complaining about.
  • Ask about a bug they hit because a value was missing or of the wrong kind, and how they found it.

Someone who answers these well will be writing acceptable typed code soon after joining, whatever their profile says.

You can also set a tiny take-home step: give a short JavaScript function and ask the candidate to write down, in plain words, what each input and the output should look like. That is a type annotation in everything but syntax.

When a hard requirement is justified

There are cases for insisting. If the hire must contribute to a large, strictly typed codebase immediately, with little mentoring available, prior experience saves real time. The same applies where the framework in use leans heavily on types.

If that is your situation, widen something else. Consider remote candidates so that the national pool of 2,226 is open to you, or look closely at the cities where the ratio is most favourable.

Keep the data in perspective

All figures are skills as listed on MyInternships.in profiles. They are neither a test of anyone's code nor a measure of what Indian developers at large know. Because listing habits vary, the true number of candidates who have used typed JavaScript is unknown to us; the count shows how many a keyword will find.

Setting the requirement for your next web hire

Require the foundation, prefer the superset, and test for the habit of thinking about data shapes. More comparisons are on recruiter intelligence and JD support is in employer resources.

When the role is defined, post your web developer opening on MyInternships.in, and see how similar roles are presented to candidates on the jobs page.

#typescriptvsjavascript#typescriptdevelopersindia#javascriptinterns#webdeveloperhiring#frontendskillsupply#talentdata

Ready to land your internship?

Create a free profile and get AI-matched with verified internships & fresher jobs across India.

Share this: