Hire QA Automation Internship: skills, stipend and screening

The three that matter most are Writing a defect report that a developer can reproduce without asking a single question; Framework structure and page-object design; Locator strategy that survives UI change. Beyond those, look for working familiarity with Selenium or Cypress or Playwright, Java or Python or JavaScript, TestNG or pytest. Everything else on the list above is teachable inside a term — treating it as an entry requirement shrinks your pool without improving the hire.

Build the regression suite for the flow that keeps breaking, and get it running before every release. That is sized for eight to twelve weeks of supervised work by someone with the fundamentals and no production experience. A second, smaller piece — automate the top twenty regression cases and get them running in CI — usually fits alongside it. Anything requiring independent production judgement should stay with the reviewer.

Start from ₹15,500–₹37,500 a month, then adjust for city and duration: metros at the top, tier-2 typically 25–40% lower, and six-month commitments above six-week ones. Publish the number in the listing — "as per industry standards" is read as low or undecided, and it costs you applications from exactly the candidates who had another option.

For a first pass, yes. Ask "Your suite fails randomly one run in five. What do you do?" and judge whether the answer is specific and consistent — you are checking for whether they fix flakiness or add retries and hide it — the defining question, which does not require you to know the subject. A Automation Testing practitioner should still take the second round, because at that point you are assessing depth rather than authenticity.

Twelve weeks is the practical minimum for output in this skill; three to six months is where most Indian programmes settle because it spans a semester break or a final-semester project. Under eight weeks you are paying for onboarding and getting a certificate ceremony. If the project cannot fit the time, shorten the project rather than the learning.

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.

No. The posting assistant asks a few short questions — the role, the work, the duration, the stipend — and drafts the description, the title and the skill tags for you. You review and edit everything before it publishes, and you can paste in your own description if you already have one.

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.