The Associate QA Engineer role in Bhubaneswar is a full-time, on-site position based in Infocity, Chandrasekharpur, with a salary up to ₹63,000 per month.
It's an entry point into structured QA work rather than a role that assumes years of testing experience already. Someone coming from a smaller, less formal testing background can do well here, provided the fundamentals are solid. The role sits within a dedicated QA function that supports a handful of product teams, rather than a single QA person embedded in a single development team.
Background and experience
A bachelor's degree meets the educational bar for this role, typically in the computing or IT space, though the department a degree is from tends to matter less here than whether someone can actually design a test case. Alongside that, candidates should have 21 months of practical experience writing test cases, tracking defects, and working with at least one automation tool, even if that exposure came from a smaller company or a less formal QA setup. Internship time counts toward this if the work was genuinely hands-on rather than shadowing someone else's process.
Direct experience with whatever specific tools the team uses is preferred but not assumed. A candidate who's used a different bug tracker or automation framework elsewhere usually adjusts within the first few weeks, since the underlying testing logic carries over even when the specific interface doesn't.
What the job covers
The work centers on catching problems before they reach a customer, not writing the code that might have caused them.
- Write test cases and actually run them against each new build rather than just filing them away
- Log defects with enough detail that a developer doesn't need to ask a follow-up question just to reproduce the issue
- Confirm a fix genuinely holds before a release goes out, not just that the original steps no longer reproduce it
- Work directly with developers when a bug's root cause isn't obvious from the initial report, which happens often enough on a growing product that it's worth building a working relationship with the development team early on.
A fair amount of the job comes down to noticing small inconsistencies other people miss. A button that's a few pixels off, a dropdown that resets when it shouldn't, an error message that fires under the wrong condition: catching that kind of detail before a customer does is most of what the role is about. None of those issues break the product outright, which is exactly why they're easy for a developer moving fast to miss.
Skills
- Solid test case design skills, including knowing what to test and, just as importantly, what to skip
- Comfort with both manual testing and at least basic automation testing
- Working knowledge of a defect tracking tool
- Genuine attention to detail, the kind that shows up in how carefully a bug report gets written, not just in finding the bug itself
That last one is harder to teach than the others, which is part of why it gets called out on its own rather than folded into a general "strong communicator" line.
Nice to have
Some exposure to a specific automation framework, such as Selenium, counts in a candidate's favor, and so does any experience reading API documentation well enough to test an endpoint directly rather than only through the user interface. Neither is required at this level, but both shorten the learning curve once someone is actually on the team. A basic comfort with SQL also helps on the rare occasion a bug turns out to be a data issue rather than a display one.
Where you'd be working
The office sits in Infocity, Chandrasekharpur, one of Bhubaneswar's established IT clusters, with a reasonable concentration of tech employers nearby. Naukri Mitra regularly lists qa engineer jobs in Infocity, Chandrasekharpur, Bhubaneswar, and the area tends to draw candidates already based in the city rather than people relocating from elsewhere in Odisha. The cluster has grown enough over the past several years that public transport connections to it have improved, making a daily commute from most parts of the city fairly manageable.
Pay and benefits
Pay for this role goes up to ₹63,000 per month, roughly in line with what a QA engineer salary in Bhubaneswar looks like at the associate level. The package includes health insurance, paid time off, and provident fund contributions, with the usual annual review tied to performance rather than a fixed schedule.
Because the role is on-site, relocation assistance and accommodation support are also available for candidates who need to move to Bhubaneswar specifically to take the job. That kind of support tends to matter more at the associate level, where the salary itself leaves less room to absorb upfront moving costs.
Team and pace
Work tends to pick up noticeably in the days leading up to a release, when the whole team is running regression passes and chasing down last-minute issues before sign-off. Between releases, the pace is steadier, with more time going toward writing new test cases for upcoming features and cleaning up test documentation that fell behind during the last crunch. It's a fairly predictable rhythm once someone's been through one or two release cycles and knows roughly when the busy stretch is coming.
New hires generally start by testing against an existing test plan before writing their own from scratch, which gives a working sense of how the team structures its testing before being asked to design it independently. After a year or so of consistent work, most associates take ownership of a full feature area rather than picking up only the test cases assigned that week.
Applying
Applicants should be ready to walk through a bug they found that wasn't obvious at first glance, and how they figured out the steps to reproduce it consistently. A resume alone doesn't say much about that kind of troubleshooting instinct. It also helps to mention which testing tools you've used most recently and whether that work leaned more toward manual testing, automation, or a mix of both. Applications are reviewed on a rolling basis, and shortlisted candidates are contacted directly for the next step.
