Hire QA Support Intern in India

None professionally, and that is the point. What you should expect is evidence: something built, run or fixed involving Jira or Azure DevOps or TestRail or Xray, that they can talk about in depth. Screen on writing a defect report that a developer can reproduce without asking a single question and explaining a technical cause to a non-technical person without condescension; treat everything else on the list as trainable during the term.

Yes, within a scoped brief. Build the regression suite for the flow that keeps breaking, and get it running before every release is achievable in a term with weekly review, and it is genuine output rather than a training exercise. What does not work is open-ended ownership of anything with production consequences — keep the judgement calls with the reviewer and the execution with the intern.

It is the bottom of the working band, and appropriate for a smaller city or a shorter commitment. In Bengaluru, Hyderabad, Pune, Mumbai or the NCR, expect to be closer to ₹27,000 for the same skills — you are competing with every other employer for the same few candidates. Decide where in the ₹11,000–₹27,000 band you sit before the first interview rather than during the offer call.

For a first pass, yes. Ask "You have two days and a hundred test cases. What do you run?" and judge whether the answer is specific and consistent — you are checking for risk-based prioritisation rather than sequential grinding, which does not require you to know the subject. A Quality Assurance practitioner should still take the second round, because at that point you are assessing depth rather than authenticity.

One finished, reviewed piece of work that someone on the team would otherwise have done — not a side project nobody adopts. The deliverables above are sized for eight to twelve weeks of supervised work by a student with the fundamentals but no production experience. If they can demo it and the team keeps using it after they leave, the hire paid for itself.

The "QA" qualifier means the deliverable is confidence, not code. Decide who acts on the findings before you post — a QA intern whose defects sit untriaged stops raising them by week four. In screening terms, that means adding one specific check: writing a defect report that a developer can reproduce without asking a single question.

A support brief attracts fewer applicants and retains them better — provided the queue is real and the escalation path is named. Put the escalation contact in the listing; vagueness here reads as "you will be alone with angry users". In screening terms, that means adding one specific check: explaining a technical cause to a non-technical person without condescension.

First applications typically arrive within about two hours of the listing going live, and most employers hiring a Quality Assurance intern have a workable shortlist inside a week. Speed depends more on how specific the brief is than on the stipend — a listing with a named project and named tools consistently outperforms a generic one at the same money.

Specificity does most of the work. A listing that names the project, the tools and the deliverable filters itself, because candidates can tell whether they fit. Adding one screening question to the application — from the set above — removes most of the rest without adding a review round.