MyInternships.in
Employer Guides

React interns: 5,729 list it, half as many as JavaScript. A screening guide

On MyInternships.in, JavaScript is listed about twice as often as React and TypeScript far less than either. What that gap means, and a two-hour build task for choosing a front-end intern.

M
MyInternships.in Research Desk
5 min read879 words
Share this:
React interns: 5,729 list it, half as many as JavaScript. A screening guide

Among candidates on MyInternships.in, CSS is listed more often than HTML: 9,160 profiles against 8,939. Nobody learns the first without the second, so the gap is a small reminder that a skills line is a piece of self-description, not an inventory.

Keep that in mind when you hire a front-end intern. The profile tells you which words a student associates with themselves. Your process has to find out what sits behind the words.

The front-end funnel in our data

The figures below are from our own candidate base, counted on 1 October 2026 across 55,557 profiles with at least one skill. A candidate with five skills appears in five rows, and none of this is a measure of competence.

Skill listed on profileAll IndiaBengaluruPuneHyderabadDelhi
JavaScript11,6951,314988959634
CSS9,1601,068756873464
HTML8,9391,058740869437
React.js5,729623487400324
TypeScript2,226218166136155
Bootstrap70864606036
Angular38038473021

Read from top to bottom, the table is a funnel. JavaScript is on 11,695 profiles. React.js is on 5,729, so 11,695 divided by 5,729 gives roughly two JavaScript listings for every React one. TypeScript appears on 2,226, which is about 39 per cent of the React figure. Angular is far smaller at 380; React is listed about fifteen times as often.

What follows for an employer? If your product is built in React, you have a healthy pool. If it is written in TypeScript, expect to teach it, or expect to search harder. If it is an Angular codebase, treat prior Angular exposure as a bonus and hire for solid JavaScript instead.

Why JavaScript fundamentals decide the hire

Most front-end bugs an intern creates are not React bugs. They are misunderstandings of asynchronous code, of how arrays and objects are copied, or of what the browser does when a request fails. A student who learnt React from a single course can assemble components and still be lost when a promise rejects.

So in the first conversation, ask two plain questions and listen to how the answers are built.

  • "A list on your page shows stale data after the user adds an item. Where do you look first?"
  • "Your API call takes four seconds. What does the user see during those four seconds, and what if it never returns?"

There is no trick here. You are checking whether the candidate thinks about state and about the person using the screen.

What to look for on the profile

A deployed link is the strongest signal a front-end fresher can offer, because front-end work is visible by nature. Open it on your phone. A project that looks fine on a laptop and collapses on a small screen tells you the candidate never tested it the way your users will.

Then check for these:

  1. A repository whose history shows work over time, not one bulk upload.
  2. At least one project that is not a to-do list, a weather widget or a clone of a famous streaming site. These are course exercises. They are fine as a start but they do not distinguish anyone.
  3. Any mention of accessibility, form validation or loading states. Rare, and worth a great deal.

The practical test: one component, three states

Give candidates a static image of a simple card list, say a list of internship postings with a title, a company and a location, plus a small JSON file or a mock endpoint. Ask for the following within two hours:

  • Render the list from the data in React.
  • Add a text filter by location.
  • Show a loading state, an empty state and an error state.
  • Make it usable on a narrow screen.

Any styling approach is allowed. No design polish is expected. Say so explicitly, or the conscientious candidates will spend the whole time on shadows and gradients.

Scoring it fairly

Use a short written rubric and have the same person score every submission.

  • Three states present: most weak submissions handle only the happy path.
  • Filter behaviour: does it ignore case and stray spaces? Does an empty result show a message?
  • Component boundaries: one giant file is acceptable for a two-hour task; copy-pasted blocks are not.
  • Narrow screen: shrink the window and see.

Follow with a short call in which the candidate shares their screen and adds one feature, such as sorting by title. Watching someone make a change for ten minutes is more informative than an hour of questions, and it settles any doubt about who wrote the code.

Set the internship up to succeed

Front-end interns do best with a design to implement, a reviewer who answers within a day, and a first ticket that reaches production. Plan those three before the joining date.

Be clear in the posting about your stack, including whether TypeScript is required from day one. Given how much smaller the TypeScript pool is on our platform, "willing to learn TypeScript" will bring you far more applicants than "must know".

You can compare front-end supply by city with our recruiter intelligence pages and find templates under employer tools. When the role is defined, post your front-end internship and send the build task to every shortlisted applicant on the same day.

#hirereactintern#frontendinternhiring#reactdeveloperfresher#javascriptinterntest#typescriptfreshers#front-endscreening

Ready to land your internship?

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

Share this:
Hiring a React front-end intern: data and a build test | MyInternships.in