How to hire a QA or test engineer in Mumbai

On this page

  1. What kind of QA engineer do you need?
  2. Skills and tools to ask for
  3. What to put in the job description
  4. How to check real testing skill
  5. Office, hybrid and commute in Mumbai
  6. Common mistakes when hiring a QA engineer

Start here

What kind of QA engineer do you need?

A QA or test engineer finds problems before your customers do. The job can look quite different from one team to another. Decide which of these is closest to yours.

  • Manual testing

    Using the product by hand, screen by screen, like a customer.

  • Automation testing

    Writing scripts that run the same checks on every release.

  • API testing

    Checking that the server returns the right data and errors.

  • Bug tracking

    Reporting problems clearly and following them until fixed.

Most small teams need a careful manual tester first. Ask for automation only if you will give the person time to build it.

Skills

Skills and tools to ask for

Name what the person will do from week one. Use the same words candidates use on their resumes.

  • Test cases

    Writing clear steps and expected results, including edge cases.

  • Bug reports

    Steps to repeat, what happened, what should happen, and a screenshot.

  • API testing

    Using an API testing tool to send requests and read the replies.

  • Automation tools

    A browser or mobile automation tool, if you need automation.

Also useful, depending on your product:

  • Basic SQL, to check that data was saved correctly.
  • A bug tracking tool and a simple way of tracking test work.
  • Testing on different phones, browsers and screen sizes.
  • Re-testing after fixes and checking old features still work.
  • Clear writing and calm talks with developers.

The job description

What to put in the job description

A clear description gets you the right people. Keep it short and include these points. More on this in how to write a job description.

  • The title and the area the office is in.
  • What the product is: web, mobile app or both.
  • Manual, automation, or a mix, in plain words.
  • The tools you use for bugs and test work.
  • Minimum experience, and whether you will consider a fresher.
  • Working mode: office, hybrid, and the days in the office.
  • Your pay range, to be given honestly on the first call.
Title
QA Engineer
Location
Our office in [your area], Mumbai
Experience
2 to 4 years in software testing. Freshers with strong testing basics may apply.
Skills
Writing test cases, clear bug reports, manual testing of web and mobile apps, API testing, basic SQL. Automation is a plus.
The work
Test new features before each release, report bugs clearly, re-test fixes and keep our test cases up to date.
Working mode
[Office or hybrid, and days]
Salary
[Your range], to be discussed on the call.
To apply
We will call you if your profile matches.

This is an example only. Replace the brackets with your own details, and delete any skill you do not need.

Check

How to check real testing skill

Testing skill shows in how someone thinks and writes. You can check both without being technical.

  • Ask them to walk you through how they tested one feature in their last job.
  • Ask for an example of a serious bug they found and how they reported it.
  • Ask what they do when a developer says it is not a bug.
  • Ask what they check when there is little time before a release.
  • Ask which tools they used for bugs, APIs and automation, and what they did in each.
  • If they say automation, ask what they automated and what they left manual.

Then give a short practical task. For example, show a login form or a simple page and ask for six to ten test cases and one bug report. Look for clear steps, odd cases such as empty or wrong input, and plain writing.

Use our first-call questions to keep the first call short. See also how to check candidate experience.

Where

Office, hybrid and commute in Mumbai

Testers and developers talk many times a day, so sitting close helps. If you offer hybrid work, say it clearly and say which days you need them in. Commute still decides who accepts and who stays.

Search the locality of your office first, then the next stations along the same line, for example Andheri, Goregaon, Malad and Borivali on the western side, or Thane, Mulund and Ghatkopar on the central side. For Navi Mumbai offices, try Vashi, Nerul and Kharghar. See hiring by Mumbai locality.

Search in plain words, for example “QA engineer in Malad with API testing”. How to use the resume database.

Building the team? See the guides for a software engineer and a full stack developer.

Avoid these

Common mistakes when hiring a QA engineer

Mistake

Better

  • Mistake

    Asking for manual and automation experts in one

    It is a long list for one person.

    Better

    Decide which matters most and ask for the other as a plus.

  • Mistake

    Not naming the product

    Better

    Say if it is web, mobile or both, so you get the right testers.

  • Mistake

    Judging only by tool names

    Better

    Ask what they tested and how they found problems.

  • Mistake

    Skipping the practical task

    Better

    A few test cases and one bug report show more than a resume.

  • Mistake

    Keeping testers apart from developers

    Better

    Seat them close, or agree on shared days.

FAQ

Common questions

Do I need a manual tester or an automation tester?

A manual tester uses the product like a customer and finds problems by hand. An automation tester writes scripts that run checks again and again. Small teams with a changing product often start with a strong manual tester. Add automation when the same checks repeat every release.

Does a QA engineer need to know coding?

For manual testing, not much. For automation, yes. Basic SQL and API knowledge help in both. Say in the job description how much coding you expect.

How do I test a QA engineer before hiring?

Give them a small screen or form from your product, or a simple public site, and ask for a few test cases and one bug report. Keep it to an hour or less. A clear, specific bug report says a lot.

Should the QA engineer sit with the developers?

It helps. Testers and developers talk many times a day, and sitting close makes that easy. If your team is hybrid, agree on shared days in the office.

Related reading

  • Resume database for recruiters
  • Pricing
  • Hiring by Mumbai locality
  • Search from a job description
  • Hire an accountant
  • Hire telecallers
  • Hire sales executives
  • Hire a receptionist
  • Hire warehouse staff
  • Hire a GenAI developer
  • Hire a forward deployed engineer (AI)
  • Hire a software engineer
  • Hire a DevOps engineer
  • Hire a data analyst
  • Hire an Android developer
  • Hire an iOS developer
  • Hire a full stack developer
  • Shortlist without HR
  • First call questions
  • Check experience
  • Set a fair salary
  • Fresher or experienced
  • Fill an urgent vacancy
  • Replace someone who quit
  • Seasonal hiring
  • First-week onboarding
  • Offer letter basics
Search Resumes