The gist
A QA team in Ganeshguri, Guwahati, needs an Associate Selenium Automation Tester who can take over existing test suites and continue expanding them as the product grows. This one's full-time and on-site, no hybrid stretch to it.
Pay tops out around ₹61,500 per month, which is close to what other Selenium automation tester salary figures in Guwahati look like for someone stepping into an associate role rather than a fresher slot.
The QA group here is five people working across two product lines, and this hire slots into the smaller of the two, a team of two that ships updates roughly every three weeks. The existing test suite already covers most of the core flows, but coverage of newer features has fallen behind, which is a big part of why this seat is open. Whoever takes it will spend the first few weeks closing that gap before settling into a steadier rhythm alongside the rest of the release cycle.
What you'd actually be doing
- Design test cases from feature specs and run them before every release
- Track down software defects, write them up clearly, and hand them off to the right developer
- Re-verify fixes once they land, rather than assuming a closed ticket means the bug is actually gone
- Work alongside developers early enough in the cycle that testing isn't the last thing bolted on before a release
- Sit in on sprint planning to flag which upcoming features will need the heaviest test coverage before they ship
A checkout button that silently stops firing in one specific browser is exactly the kind of thing this team wants caught before a customer notices. That kind of bug rarely shows up in a quick manual pass, which is a big part of why the automated suite matters as much as it does here.
What gets you in the door
A bachelor's degree is the starting point, ideally in computer science, IT, or a closely related field where the fundamentals transfer. Two years of hands-on QA experience is expected, with real exposure to test case design, defect tracking, and some automation work rather than manual testing alone.
Naukri Mitra sees a fair number of applicants here who spent their first couple of years doing manual QA and picked up Selenium on the side, and that path works just as well as someone who started in automation from day one. What tends to stand out on a resume isn't the number of tools listed but whether the candidate can talk through why a particular test failed and what they did about it, rather than just that it passed on the second try.
- Selenium for browser automation
- Java or Python for writing and maintaining test scripts
- Experience with at least one test framework, such as TestNG or PyTest
- Comfortable tracking defects in a ticketing system like Jira
The team also expects someone who can read an existing test script written by a previous tester and figure out what it does without needing a walkthrough, since much of the first month is spent familiarizing themselves with what's already there before adding anything new.
Bonus points for
None of this is required, but it helps your case. Some exposure to API testing tools like Postman speeds up onboarding, since a decent chunk of the test suite directly touches backend endpoints. Basic Git skills matter more than people expect going in, since test scripts live in the same repo as everything else. A bit of SQL for checking what actually landed in the database after a test run comes in handy weekly, not just occasionally. Familiarity with running tests in a CI pipeline, even with a simple Jenkins setup, reduces the hand-holding needed once you're past the first month. An ISTQB certification isn't going to make or break an application, but it's a nice signal if you've got one. People who pick up these skills on the job tend to move toward an SDET title within a couple of years, since the line between testing and light development work here is thinner than the job title suggests. A couple of past hires have already gone that route, picking up more scripting responsibilities as their comfort with the codebase grew.
Pay and benefits
- Health insurance
- Paid time off
- Provident fund contributions
- Relocation assistance for candidates moving to Guwahati
- Accommodation support while you settle in
That last pair matters here since a good number of applicants for this kind of opening in Guwahati aren't already living in the city. The relocation piece covers a fixed lump sum toward moving costs, and the accommodation support runs for the first month while someone finds a permanent place.
Where you'll be working
The office sits in Ganeshguri, and this is a fully on-site role, five days a week, with no remote days built in. Release cycles run about every three weeks, so the pace shifts noticeably in the days leading up to a push compared to the quieter stretch right after one ships.
Ganeshguri itself is a fairly central, well-connected part of Guwahati, with enough rental housing nearby that most people relocating for this role end up finding a place within a couple of weeks of arriving.
Getting in touch
Send over your resume, and if you've got one, a sample bug report or test case document you're proud of. The first round is a short call about your testing background, then a hands-on round where you'll walk through writing a test case for a sample feature. Most people hear back on next steps within a few working days of that second round. Candidates from outside Guwahati are welcome to have the first call on video, though the hands-on round works better in person once travel can be arranged. There's no written test beyond that hands-on session, and the whole process usually wraps up within two to three weeks from the first call.
