The three labels most associated with infrastructure work are remarkably close in our data. AWS is listed by 3,806 candidates registered on MyInternships.in, Linux by 3,634 and Docker by 3,110.
None of them reaches 7% of the 55,557 profiles we counted on 1 Oct 2026. For an employer hiring a junior DevOps or platform engineer, that sets expectations: this is a mid-sized pool, not a mass one, and the order of the three skills changes depending on the city.
A cloud brand leads the operating system
AWS sits on 6.9% of profiles, Linux on 6.5% and Docker on 5.6%. It is mildly surprising that a cloud provider's name is listed more often than the operating system most cloud servers run on.
One reading is that candidates list what a course or certificate was called. Another is that Linux feels too basic to mention. We cannot tell which from a count, and overlap between the three is not something this data measures, because every tag is counted separately for each profile.
| Where | AWS | Linux | Docker |
|---|---|---|---|
| All India | 3,806 | 3,634 | 3,110 |
| Bengaluru | 450 | 482 | 360 |
| Pune | 376 | 379 | 313 |
| Hyderabad | 330 | 326 | 213 |
| Chennai | 268 | 243 | 212 |
| Delhi | 208 | 184 | 196 |
| Mumbai | 164 | 166 | 122 |
| Ahmedabad | 70 | 103 | 69 |
The order changes by city
In Bengaluru, Linux is ahead of AWS, 482 to 450. Pune and Mumbai are level to within three profiles. Ahmedabad shows the clearest Linux lead of any city in the table.
Hyderabad and Chennai follow the national order with AWS on top. Delhi is the odd one out: Docker, at 196, is listed more often than Linux there, the only city in the table where containers outrank the operating system.
Hyderabad has the widest gap between AWS and Docker. Its Docker count of 213 is well below its AWS count of 330, so a container-heavy role there draws on a noticeably smaller group than a general cloud role would.
Compare with the developer baseline
Git is listed by 10,194 candidates. Docker's count is about 30% of that. So among the people who signal that they write and share code, a minority signal that they package and ship it.
This is the gap junior DevOps hiring has to bridge. Plenty of candidates can build an application. Fewer describe themselves as able to run one. That is partly a matter of exposure: college projects seldom need a deployment pipeline.
It also means the scarce thing is not knowledge of a tool but the experience of being responsible for something that must stay up. Interns rarely get that responsibility, so employers who can offer a small, supervised piece of real infrastructure have something attractive to put in the JD.
Which of the three to require
If you must pick one hard requirement for an entry-level infrastructure role, think about which is slowest to teach on the job.
- Linux underlies the other two. Comfort at a command line, with permissions, processes and logs, takes time to develop and is hard to fake in a live exercise.
- Docker is a contained concept. A candidate with good Linux habits usually picks it up quickly.
- AWS is wide. A profile tag might reflect one service used once, or a breadth of practice. It needs the most probing.
Many teams therefore require Linux, prefer Docker and treat any cloud experience as a bonus. That ordering also happens to keep the pool reasonably large in every city we measure.
Whatever you require, write it as a task. "You will keep our staging server healthy and automate one manual deployment step" tells a candidate far more than three product names in a row, and it invites applicants who have done similar things under different labels.
A screen that reveals real operations experience
Tags are cheap to add, so ask about incidents instead of tools. Good prompts include: describe something you deployed and how you knew it was running; tell me about a time a service would not start and what you checked first; how would you find what is filling a disk?
A candidate who has operated anything, even a personal project on a small server, answers these with specifics. One who has only watched a course answers with definitions. A short hands-on terminal task settles any remaining doubt.
Keep that task close to the job. Asking someone to find a failing process, read its log and restart it cleanly is realistic and quick to assess, and it avoids trivia about commands nobody remembers without looking them up.
Caveats worth keeping in mind
We are counting what candidates on MyInternships.in write under skills. No one's command-line ability was tested, and these profiles are not representative of every engineer in India. The numbers show how many people each word will reach on our platform and how that differs across cities.
Building a junior DevOps pipeline
Require the foundation, test with a practical task, and be open about what you will teach. You will find JD and screening help in employer tools, and background reading in employer resources.
When you are ready, hire DevOps and cloud talent on MyInternships.in, or look at current openings on the jobs page to see how peers describe similar roles.


