GIFT City, Gandhinagar. Full-time, on-site, up to ₹1,28,500 a month. Seven years of hands-on QA experience gets you in the door for this Senior QA Engineer opening, and the team is hiring because release velocity has outpaced their current testing bandwidth. Two developers were added to the team this quarter, and QA headcount hasn't kept pace, which is why this seat exists right now. The last senior QA hire left for a role closer to home, not because of dissatisfaction with the work itself, which the hiring manager mentions upfront because it tends to come up anyway.
The work
- Design test cases that actually cover edge cases, not just the happy path a feature was demoed with
- Execute both manual and automated test suites across releases
- Log defects with enough detail that a developer can reproduce them without pinging you first
- Verify fixes before anything ships, and push back if a fix only addresses the symptom
- Sit with developers early in a feature's build, not just at the handoff point
Expect ownership over at least one major product area rather than rotating across everything the team ships. Deep familiarity with one part of the product, tested well and understood thoroughly, catches more real bugs than shallow coverage spread across ten. New hires typically inherit whichever area has the largest outgoing coverage gap, so the specific product area isn't fixed until closer to the start date. That's a deliberate choice on the team's part, not an oversight, since it lets the assignment match wherever the risk is highest at the time.
Skills you'll actually use
Test case design and defect tracking are the daily bread here, alongside a working split between manual testing for exploratory work and automation for anything repetitive enough to script. Attention to detail matters constantly, since the bugs that make it to production are usually the ones that looked fine on a quick pass. Reviewers on this team have a habit of asking "what happens if this field is empty" about nearly everything, and that instinct is exactly what the role is looking for.
- Test case design, covering functional, edge-case, and regression scenarios
- Manual testing for exploratory work and automation testing for repeatable suites
- Defect tracking and clear, reproducible bug reports
- Attention to detail, applied consistently rather than only when a release feels high-stakes
On the bonus side: experience with Selenium, Playwright, or Cypress for browser automation, some comfort writing SQL to validate data directly rather than trusting the UI alone, and familiarity with a test management tool like TestRail or Zephyr. API testing experience with something like Postman rounds this out nicely, since a growing share of bugs show up at the API layer before they ever reach a screen. None of these bonus items are dealbreakers if you're missing one or two, but a strong candidate usually brings at least half the list already.
Certification and experience
A bachelor's degree is the expected baseline, and an ISTQB certification or an equivalent testing credential is required alongside it. Seven years of hands-on QA experience is standard for this seat, most of it spent testing production software rather than academic exercises. A candidate coming purely from a manual testing background will need to show real automation exposure too, since this role expects both rather than a strong lean toward one. The ISTQB requirement is checked at the resume stage, so make sure it's listed clearly rather than buried in a certifications appendix.
How the team works
QA reports into engineering here rather than sitting in a separate department, which means test planning happens inside the same sprint as development instead of trailing a release by a week. One of the two current QA engineers came in through Naukri Mitra last year, and the team has mentioned wanting this new hire to eventually take the lead on automation strategy once they're settled in. Release cadence runs roughly every two weeks, so expect a rhythm of build-up toward a release followed by a quieter stretch right after. That quieter stretch is when most automation writing happens, since there's rarely enough slack during an active release cycle to build new test coverage from scratch.
Some releases are cleaner than others. A recent one shipped with a payment reconciliation bug that surfaced only under a specific currency-conversion edge case, and it took two days of digging to isolate. That kind of work is routine here, not an exception worth flagging separately. GIFT City's client base skews toward financial services, so edge cases involving currency, rounding, and cross-border transactions come up more often here than they would at a typical consumer product company.
Compensation and benefits
- Salary up to ₹1,28,500 per month
- Health insurance
- Paid time off
- Performance-linked bonuses
- Relocation assistance and accommodation support for candidates relocating to Gandhinagar
Compared with other QA engineer salary figures in Gandhinagar per month, this one lands on the higher side, largely because GIFT City's finance-heavy client base raises the bar for QA rigor across the board. Bonus payouts here track defect escape rate, meaning how many bugs slip past QA into production, more than any single subjective metric.
Getting hired
This is an on-site role in GIFT City, so relocation support matters if you're coming from outside Gandhinagar. Bring examples of test plans you've written and defects you've caught that would have been genuinely costly if they'd shipped. Specific numbers help: defects caught per release, automation coverage percentage, or whatever concrete data you can point to from a past role. Candidates exploring qa engineer jobs for experienced professionals in Gandhinagar should expect a practical testing exercise as part of the interview, not just a conversation about methodology. The whole process usually runs about two weeks from application to offer, and the team tries to give feedback within a few days of each round rather than leaving candidates waiting. If you're weighing multiple offers, mention that early, since the hiring manager has shown flexibility on the timeline before for the right candidate.
