MyInternships.in
Hiring Insights

Only 180 Candidates List Cyber Security and 56 List Cloud Computing

AWS appears on 3,806 candidate profiles on MyInternships.in but the phrase Cloud Computing on just 56. Why discipline names are rare and tool names common, and how to hire around it.

M
MyInternships.in Research Desk
4 min read865 words
Share this:
Only 180 Candidates List Cyber Security and 56 List Cloud Computing

Search our candidate base for "Cloud Computing" and you get 56 profiles. Search for "AWS" and you get 3,806. The second figure is about 68 times the first, and both describe much the same field.

Cyber Security tells a related story. Just 180 candidates registered on MyInternships.in list it by name, out of 55,557 profiles that list skills as of 1 Oct 2026. Employers who read these numbers as "nobody is available" are drawing the wrong conclusion.

Discipline words versus tool words

Cyber Security is on about 0.3% of profiles and Cloud Computing on about 0.1%. The tool-level labels around them are far more common.

Label as listedType of labelCandidates
AWSTool or platform3,806
LinuxTool or platform3,634
DockerTool or platform3,110
Cyber SecurityDiscipline180
Cloud ComputingDiscipline56

The pattern is consistent across our data. Candidates describe themselves by the thing they have installed, configured or typed commands into. They seldom use the name of the field. Any one person may show up in more than one row here, since all of their listed skills are counted.

Cloud talent exists, under another name

If a recruiter filters on the phrase "Cloud Computing", Bengaluru yields eight profiles on our platform, and Pune, Delhi and Chennai six each. Every other city falls below our reporting threshold of five.

Filter on AWS instead and Bengaluru yields 450, Pune 376 and Hyderabad 330. The people have not changed. The search term has.

The lesson for JD writing and for database searches is the same. Use the vocabulary candidates use. For cloud roles that means naming platforms and tools, and treating the discipline phrase as a heading, not a filter.

The same goes for a candidate search inside any applicant tracking tool. If your saved search uses the discipline phrase, rerun it with platform names and compare the two result sets. On our platform the second list will be many times longer.

Security is a harder case

For cyber security there is no single dominant tool tag in our data that plays the part AWS plays for cloud. The 180 profiles are spread thinly: 22 in Bengaluru, 19 each in Pune and Hyderabad, nine in Mumbai, eight in Chennai, seven in Delhi.

That makes entry-level security hiring a small-pool exercise on any keyword. The practical answer is to hire for the adjacent foundations, which are well supplied. Security work rests on understanding operating systems, networks and code. Linux is listed by 3,634 candidates and Python by 21,874.

A candidate with strong Linux habits, some scripting, and visible curiosity about how systems break is a credible security trainee, whether or not the profile carries the discipline name.

Networking knowledge is harder to spot, because our skill list has no dedicated label for it. Ask about it directly: how a request travels from a browser to a server, what a firewall rule does, why a port might be closed. Clear answers are a good sign in a trainee.

Finding the security-minded among generalists

Because the label is rare, look for behaviour instead. In applications and interviews, these signals are worth more than the tag:

  • participation in capture-the-flag events or responsible disclosure of a bug;
  • a home lab, however modest, that the candidate can describe in detail;
  • the habit of asking "what could go wrong" when shown a simple design;
  • careful, honest answers about the limits of what they know.

Put one line in the JD inviting candidates to mention such work. People who have done it are usually glad to be asked, and it gives you a self-selected shortlist from a general pool.

Be careful about what you ask candidates to demonstrate. Security testing must only ever be done on systems the person owns or has permission to test, and a responsible candidate will say so without being prompted. Treat that answer as a positive signal.

What this says about JD keywords generally

A job description is read twice: once by a person deciding whether to apply, and once by whatever search or matching step sits between you and the applicant list. Discipline words serve the first reading. Tool words serve the second.

Good JDs therefore carry both. Open with the discipline so the role is understood, then list the concrete tools and tasks so that matching works. A posting titled "Cloud Engineer Intern" that never names a platform will under-reach on our platform, and so will one that lists tools without saying what the job is.

Do not over-read small numbers

These are self-declared profile entries on MyInternships.in. A count of 56 does not mean only 56 people understand cloud computing; it means 56 people chose that phrase. Equally, an AWS tag does not certify depth. The figures are about labelling habits on our platform, not the country's talent stock.

Hiring for cloud and security roles

Name the tools, describe the work, and screen for foundations and curiosity. You can compare more skill labels on recruiter intelligence and get JD help from employer tools or employer resources.

To reach candidates who list the underlying skills, post your cloud or security role on MyInternships.in and say plainly which parts you are prepared to teach.

#cybersecurityhiring#cloudcomputingskills#securityinternsindia#awsvscloudcomputing#skillkeywordshiring#talentdata

Ready to land your internship?

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

Share this:
Why So Few List Cyber Security or Cloud Computing | MyInternships.in