GIFT City in Gandhinagar has a Junior Automation Testing Engineer opening, full time, on site, with a QA team building out automated test coverage for a growing product. One year of experience is the expectation, enough to have already written real automated test scripts, not just manual test cases described in a spreadsheet.
The role covers designing and executing test cases, identifying and reporting software defects, verifying fixes before release, and collaborating with developers to improve product quality, with a specific focus on building and maintaining automated test scripts that catch regressions before they reach a human tester. A junior automation engineer here spends real time both writing new automated coverage and fixing existing scripts that break as the application under test evolves.
Required skills are Selenium or a similar automation tool, scripting ability, familiarity with test frameworks, and defect tracking. A bachelor's degree in computer science, information technology, or a related field is expected, along with hands-on experience with test case design, defect tracking, and automation tooling.
GIFT City in Gandhinagar is a purpose-built financial and business district, and the product this QA team supports releases on a regular cadence, which means automated test coverage genuinely matters for catching regressions before they slow down that release schedule.
Naukri Mitra has listed QA roles from this employer previously, and junior automation engineers who've joined recently describe learning to write maintainable test scripts, ones that don't break with every minor UI change, as the single most useful skill they developed here, more valuable long-term than raw scripting speed.
Interviews include a practical automation exercise and a discussion of a defect you found through automated testing. Candidates who talk about writing test scripts that are resilient to minor UI changes tend to interview well.
Performance conversations here happen roughly twice a year, and for a Junior Automation Testing Engineer specifically, the focus tends to land more on judgment calls and how issues were handled than on raw output volume. A colleague who ships a lot but leaves messes for others to clean up tends to get flagged in review, even if their individual numbers look strong on paper.
The QA team's automated coverage has roughly tripled over the past year as more of the manual regression suite gets converted into scripts, and junior engineers who focus on writing resilient, low-maintenance tests tend to get trusted with broader coverage ownership faster than those optimizing purely for test count.
A test script that passes reliably in isolation can still fail intermittently when run as part of the full suite, usually due to shared test data or timing assumptions that only break under specific ordering, and junior automation engineers here learn to treat that kind of flakiness as a real bug in the test itself rather than something to just rerun until it passes.
The automated test suite here runs on every pull request, and a flaky test that fails intermittently without a real underlying bug erodes trust in the whole suite fast, which is why junior engineers are explicitly taught to treat flakiness as a problem worth fixing immediately rather than something to just rerun.
The QA team tracks test suite execution time closely, since a suite that takes too long to run stops getting run as often as it should, and junior automation engineers are expected to think about test efficiency alongside coverage rather than treating the two as unrelated concerns.
This role is based at GIFT City, Gandhinagar, pin code 382355, five days a week on site. Pay is up to ₹39,000 a month. The team hopes to fill this seat within four to five weeks.