Copy-ready JD · Manual and automation QA

Software Tester Job Description for Manual and Automation QA

A copy-ready software tester JD for manual, automation or mixed QA roles in product companies, IT services firms and startups. It covers test design, bug reporting, regression, API and mobile testing, tools and pay placeholders. Below it: variants for interns, freshers and experienced testers, screening questions, a bug-hunt task and India-specific test areas.

Free JD templateReady to postScreening questionsSkills to test

Free listing for paid roles from ₹8,000/month (live within 2 working days after review) · Paid plans go live instantly after company verification · GST invoice

Software developer working at a desk with multiple monitors
Quick answer

What are the roles and responsibilities of a software tester?

A software tester checks that an application behaves as intended before users see it. They study requirements, write test scenarios and cases, test web or mobile builds, log reproducible bugs with steps, evidence, severity and priority, retest fixes and run regression before every release. Automation testers also script repeatable checks in tools such as Selenium or Playwright and run them in the build pipeline. The JD should name the product, the manual-to-automation mix, tools and pay.

Copy-ready job description

Replace every [placeholder] before sending. Copy the text or download it as a .txt file and paste it into your letterhead or email.

Software tester job description (manual and automation QA)
Job Title: Software Tester – [Manual / Automation / Manual and Automation] ([Internship / Full-time])
Company: [Company Name] – [what your product does and who uses it]
Team: QA team of [Number] working with [Number] developers; reporting to [QA Lead or Engineering Manager Name]
Location and work mode: [City] – [On-site / Hybrid / Remote]
Hours: [Start Time]–[End Time] IST, [Number] days a week; [release-night or weekend testing, if any, with comp-off as per company policy]
Compensation: Stipend ₹[Amount] per month (internship) / CTC ₹[Amount] per annum (full-time)
Experience: [Final-year student / Fresher / [Number] years in software testing]

About the role
You will test [web application / Android and iOS apps / APIs / enterprise software] used by [type of users]. Your job is to find problems before our customers do, describe them so clearly that developers can fix them fast, and help the team release with confidence every [sprint length / release cycle].

Key responsibilities
- Review user stories, requirement documents and designs, and flag unclear or untestable requirements before development starts.
- Write test scenarios and test cases in [Jira / TestRail / Excel / your test management tool], with test data and expected results.
- Run functional, integration, smoke, sanity and regression tests on [browsers / devices / environments].
- Log bugs in [Bug Tracker] with steps to reproduce, expected and actual results, screenshots or screen recordings, logs, severity and priority; retest fixes and close them.
- Test APIs with [Postman / Rest Assured] and verify data in the database with SQL queries.
- [Automation roles] Build and maintain automated tests in [Selenium with Java / Playwright with TypeScript / Cypress / Appium] using page objects or a similar structure, and run them in [Jenkins / GitHub Actions / GitLab CI].
- Join sprint planning and stand-ups, and share a test summary with known risks before each release.
- Use only dummy or masked test data; never copy real customer data into a test environment without written approval.

Requirements
- [B.E. / B.Tech / BCA / MCA / B.Sc IT, or any graduate with software testing training]; [Year] pass-outs eligible.
- Clear understanding of the software development life cycle, the software testing life cycle and the bug life cycle.
- Test design techniques such as boundary value analysis, equivalence partitioning and negative testing.
- Basic SQL; for automation roles, programming in [Java / Python / JavaScript or TypeScript].
- Precise written English for bug reports, patience and a sharp eye for detail.

Good to have
[ISTQB Foundation Level], [performance testing in JMeter / testing on real mobile devices / accessibility testing] and Git basics.

What we offer
[Training plan], a mentor in the QA team, [benefits as per company policy], [internship certificate and pre-placement offer opportunity, for interns] and a path to [Senior Tester / Automation Engineer / QA Lead].

How to apply
Apply on MyInternships.in with your resume and, if you have them, sample test cases, a bug report or an automation project on GitHub. Selection: [short written test] → [practical testing task] → [technical interview] → [HR discussion]. We never charge candidates any fee at any stage of hiring.

This template is general guidance for employers in India, not legal advice. Adapt it to your company policies, the offer you actually made and the rules that apply to your organisation, and have contracts reviewed by a qualified adviser.

Adapting the JD for interns, freshers and experienced testers

The template works at every level, but the title, the must-haves and the interview change a lot between a student and an automation engineer. Decide the level before you post: a fresher listing that asks for 'framework design experience' attracts copied resumes and puts off honest applicants.

State the manual-to-automation split truthfully. If most of the work is manual regression with some scripting, say so, or the people who wanted pure automation will start looking elsewhere as soon as they see the real work.

LevelTitle to useAsk forLeave out or teach
Intern (student)QA intern, software testing internTesting basics, curiosity, clear writing, part-time hours around classesFramework design, tool experience, certification
Fresher (0–1 year)Software tester, junior QA engineer, trainee test engineerSTLC and bug life cycle, test case writing, basic SQL; one coded project for automation rolesYears of tool experience, deep domain knowledge
Experienced manual testerQA engineer, test analystDomain knowledge such as banking or e-commerce, test planning, defect triage, API testingAutomation, unless the role really needs it
Automation engineer or SDETAutomation test engineer, SDETCoding in your framework's language, CI pipelines, fixing flaky tests, code reviewsLong lists of tools your team does not use

Screening questions for software testers

  • 'Write five test cases for a login screen that uses a mobile number and OTP.' Strong answers cover invalid numbers, expired and reused OTPs, resend limits and the message shown for each error, not just a successful login.
  • 'A developer says your bug cannot be reproduced. What do you do?' Look for retesting on the same build, adding environment details, logs or a recording, and sitting with the developer instead of arguing.
  • 'What is the difference between severity and priority? Give an example where they differ.' A spelling mistake in the company name on the home page is low severity but high priority.
  • 'You have two hours before release and two days of regression tests. What do you run?' Listen for risk-based choices: changed areas, login and payment flows, and the journeys most users take.
  • For automation roles: 'Your test passes on your laptop and fails in CI. How do you investigate?' Good answers mention waits, test data, environment differences and the screenshots and logs the pipeline saves.
  • 'Tell me about the most interesting bug you have found.' Freshers can answer from a college project, an open-source app or a course exercise.

A practical bug-hunt task to run before the interview

Testing resumes look alike, so ask shortlisted candidates to test something. Use a small staging build of your product, or a simple form you control, with a few bugs planted in advance: a field that accepts an invalid PIN code, an amount that rounds wrongly, a button that submits twice, an error message that exposes technical details.

Allow 45 to 60 minutes. Ask for ten test cases, the three most serious bugs written as full reports, and one sentence on what they would test next with more time. For automation candidates, add a short take-home: automate the login flow plus one negative case, with a README that explains the locator strategy and how to run the tests headless.

Score every submission on the same scale: coverage of risky paths, clear steps to reproduce, sensible severity, and whether a developer could act on each report without asking a follow-up question. Never use the task to get free testing done on a live product.

See also: Interview scorecard template Hire QA test engineers

India-specific areas your testers should cover

Apps built for Indian users break in predictable places. Name the ones that matter to your product in the responsibilities, so candidates know what they will be testing.

  • UPI and card payments: success, failure, pending and refund states, tested only in the payment gateway's sandbox or test mode, never with real money or real cards.
  • OTP and SMS: delays, resend timers and auto-read on Android. Sender IDs and message templates must be registered with telecom operators under TRAI's rules, so an edited message text can stop OTPs arriving; catch this in staging.
  • Indian formats: +91 mobile numbers, PIN codes, free-form addresses, names with initials only, DD/MM/YYYY dates and rupee amounts grouped in lakhs and crores.
  • Languages and devices: Hindi and regional-language text, font rendering, budget Android phones with little memory, and slow or patchy mobile data.
  • Test data: made-up records only. Never put real Aadhaar, PAN, bank or customer details into test environments; careless handling of personal data is a real risk under the Digital Personal Data Protection Act, 2023.
  • Accessibility: work for government departments may have to meet the Guidelines for Indian Government Websites and Apps (GIGW), so confirm the version your client follows.

Posting your QA opening on MyInternships.in

Open the AI hiring assistant at /hire-talent#post-internship and tell it about the role, with this JD beside you: the product, manual or automation focus, tools, release rhythm, location and pay. In about two minutes it drafts the title, description and skills list, and the live preview lets you check the draft against your JD before you submit. MyInternships.in verifies your company before the listing goes live, and you can post an internship or a fresher job for office, hybrid or remote work in any Indian city.

A free listing is available for one paid role offering ₹8,000/month or more; it is reviewed and goes live within 2 working days, while applicants' contact details and resumes need a paid plan, as the plans table on this page shows. To approach testers directly, describe the profile in plain English in the candidate database and let the AI rank the matches.

See also: Post a software tester role Compare plans Search QA candidates Hire IT and software interns

Frequently asked questions

What is the difference between a software tester and a QA engineer?

Many Indian companies use the titles interchangeably. Strictly, a software tester runs tests and reports defects, while a QA engineer also improves the process that produces quality: reviewing requirements, defining the test strategy, setting release criteria and adding automation. Use the title candidates search for and let the responsibilities show the real scope.

Can a fresher be hired straight into an automation testing role?

Yes, if the fresher can already code. Look for a project that automates a real application, with readable code, proper waits instead of fixed sleeps and a README explaining how to run it. Expect to teach your framework, CI set-up and coding standards, and pair the new hire with an automation engineer who reviews their tests during the first months.

Is manual testing still worth hiring for?

Yes. Exploratory testing, usability checks, features that change every sprint and one-off scenarios are usually cheaper to test by hand than to automate. Automation pays off for stable checks that run again and again, such as regression suites. Most teams need both, so describe your actual split instead of advertising an automation role that is mostly manual work.

Which degree should a software tester have?

Testing is open to many backgrounds. B.E., B.Tech, BCA, MCA and B.Sc IT graduates are common, but a B.Com or BBA graduate who has learnt testing well can be excellent on business-heavy software such as accounting or banking applications. Ask for programming only in automation roles, and test reasoning and writing rather than relying on the degree name.

Should we ask for ISTQB certification?

Treat it as a plus, not a filter. The ISTQB Foundation Level shows that a candidate knows standard terms and techniques, but it does not prove they can find bugs, and many capable testers have never taken it. A short practical task tells you far more, so list certification under 'good to have' rather than under requirements.

Which automation tool should the JD mention: Selenium, Playwright or Cypress?

Name the tool and language you actually use, because that is what the new hire will work in from day one. If you are choosing or migrating, say so. Candidates who know one tool can usually learn another once they understand locators, waits, assertions and test structure. Listing every tool on the market suggests you have not decided.

How should we measure a software tester's performance?

Look at outcomes, not bug counts alone: serious bugs caught before release compared with those reported by customers, how clear and reproducible the reports are, how well tests cover the riskiest requirements and, for automation, how stable and fast the suite is. Counting bugs on its own rewards trivial reports and sours the relationship with developers.

Can software testers work remotely?

Yes, for web applications and APIs, provided testers have secure access to staging environments, test accounts and an easy way to share recordings and logs. Mobile testing needs devices, so supply them or use a device cloud. Interns and freshers pick up the product faster with some time in the office, so a hybrid arrangement often suits them best.

What should a QA intern work on in the first month?

Start with using the product as a customer would, then running existing test cases and logging bugs that a senior reviews before they reach developers. By the end of the month the intern should be writing test cases for a small feature and taking part in one regression cycle. Give a written plan and weekly feedback, and real work rather than only training videos.

Should testers have access to real customer data?

Generally no. Use masked or synthetic data in test environments, and give production read access only to named people, for a specific purpose, with approval. Testers do need realistic data, so invest in generating good test data. This supports your obligations under the Digital Personal Data Protection Act, 2023 and limits the damage if a test environment is ever exposed.

What is an SDET, and should our JD use the title?

A software development engineer in test is a developer who builds test frameworks, tools and automated checks, often inside the product codebase. Use the title only if the role really involves that level of coding and code review. For a role that mostly runs and maintains existing automated tests, 'automation test engineer' sets more accurate expectations.

Plans and pricing for employers

Free
₹0
1 listing
  • 1 internship or job listing
  • Live for 30 days once approved
  • Reviewed by our team, live within 2 working days
  • Only for paid roles offering ₹8,000/month or more
  • Applicant contact details and resumes need an upgrade
Most popularStarter
₹999
incl. GST · 30 days
  • 5 internship or job postings
  • Goes live instantly after company verification
  • Full applicant contact details and resumes
  • Email support
Growth
₹1,999
+ GST · 30 days
  • 15 internship or job postings
  • Goes live instantly after company verification
  • Priority support and AI candidate matching
  • Full applicant contact details and resumes
Enterprise
Custom
volume hiring
  • Custom volume hiring and campus drives
  • Unlimited resumes
  • Dedicated sourcing team
  • SLA and GST invoice

Prefer to search candidates yourself? The candidate database lets you search, then unlock resumes and contact details with credit packs of ₹999 (incl. GST) or ₹1,999 (incl. GST), each valid for 30 days. Describe the role in plain English and the AI ranks matching candidates.

Prices in INR as of 21 November 2026. Pay securely by Razorpay; a GST invoice is issued for every paid plan (add your GSTIN at checkout). Enterprise pricing on request.

Post your software tester role

Describe the product, testing mix, tools and pay to the MyInternships.in AI hiring assistant, check its draft against this JD in the live preview, and publish once your company is verified.

Post a jobPricing