techrastaPRE-LAUNCHManual testing, API testing and automation roles can share a title while requiring different work. Read the responsibilities first, then choose the QA path your evidence supports.
For aspiring testers, manual QA professionals and engineers moving into test automation.Reviewed 27 October 2026 · Search guidance and external resources, not a live job feed. Openings and eligibility change; verify them with the employer.
Skills to compareTest analysis, test cases, exploratory testing, defect reporting and regression testing.
Evidence you can showA concise test plan, boundary cases and bug reports with steps, expected results and actual results.
Skills to compareHTTP, request and response validation, authentication basics and relevant SQL queries.
Evidence you can showAn API collection with positive and negative checks, documented test data and assertions.
Skills to compareA programming language, a browser-testing framework, reliable selectors and test maintenance.
Evidence you can showA small suite with repeatable setup, meaningful assertions and a CI run showing the results.
Skills to compareCoding and test architecture alongside debugging, automation and engineering practices required by the role.
Evidence you can showA test harness with clear structure, fixtures, failure diagnostics and an explanation of trade-offs.
These links lead to official employer or learning resources. They are not TechRasta partners, confirmed vacancies or endorsements.
Use the official careers routes and search for testing-related responsibilities. This link is not a claim of a current QA vacancy.
Search quality and engineering titles; verify country, experience and responsibilities for each result.
A structured reference for testing fundamentals. Use the syllabus to organise learning; a certificate is not a substitute for practical evidence.
Official setup and learning material for a browser-testing portfolio project.
Use these as starting phrases on your preferred search engine or job board. Adjust the language, seniority and location to your needs.
"manual tester" "India" "junior""QA automation" "Playwright" "India""API testing" "QA engineer" "India""SDET" "India" "Java"Document the main user journeys, risks, expected behaviour and test data. Include invalid inputs and boundary conditions, not only successful cases.
For each genuine issue, record the environment, minimal reproduction steps, expected and actual results, and supporting evidence. Avoid inventing defects to fill a portfolio.
Choose a few important checks, keep them independent and add clear assertions. Document setup and known limitations. Expand only after the basic suite is reliable.
Link the relevant test work and explain what you tested and why. If a required skill is missing, name a practical learning step instead of claiming it on your résumé.
Track the original link, role, résumé version and next action in a free CSV template.
Titles vary. Automation roles often focus on implementing and maintaining tests; SDET openings may expect deeper coding, tooling and test architecture. Assess the actual responsibilities and interview expectations.
The requirement depends on the opening. Manual testing can focus on analysis and defect reporting, while API, SQL or scripting may still be requested. Automation and SDET roles commonly ask for programming skills.
There is no single requirement across employers. Check each opening. The syllabus can structure your study, while a portfolio shows how you apply testing concepts.
No. TechRasta is in pre-launch. AI matching and supported auto-apply are planned features. You can use these resources now and join the free waitlist for launch updates.
We’re building AI job search and supported auto-apply for India’s tech and IT professionals. Join the free waitlist for launch updates and early access invitations.
Just your email to join. No payment or résumé needed. Product in development.