This is a remote manual QA tester position, open to applicants anywhere, paying $55,000 a year for full-time work. The role sits on a small QA team that covers both the web product and its companion mobile apps, and the person hired will spend most of their time moving between the two.
Manual testing still matters here even as automation grows elsewhere in the company. Some kinds of problems, especially ones tied to layout, timing, or how something actually feels to use, only show up when a person is looking at the screen and paying attention. A script can confirm that a button exists and responds to a click. It can't tell you that the button sits in an awkward spot, or that a confirmation message flashes by too fast to actually read.
The Work
- Run through planned test cases on both the web product and the mobile apps, checking that features behave the way the spec says they should
- When something's broken, write it up clearly enough that whoever picks it up doesn't need to come back with follow-up questions
- After a fix goes in, check the surrounding areas of the product to confirm nothing else got knocked loose in the process
- Keep clear notes on what's been covered and give the manager and the rest of the team a regular sense of where things stand
A recent example: a signup form looked fine on every device tested until it hit a five-year-old Android tablet, where the submit button sat just past the edge of the visible screen. Nobody had thought to test that particular model, and it turned out to be a fairly common one among the company's older users. That's the kind of gap this role exists to catch, the sort of thing that never shows up in a bug list generated by an automated script running against a handful of standard screen sizes.
Requirements
The role asks for a working mix of technical care and clear communication.
- The ability to build test cases from a feature spec, not just run through ones someone else already wrote
- Comfort logging and tracking issues inside a bug tracking tool
- An understanding of how to check that a fix didn't quietly break something nearby
- Genuinely close attention when comparing what a feature is supposed to do against what it actually does on screen
- Basic SQL, enough to look up or double-check data in a database when a bug report needs it
An associate degree is the minimum educational requirement, ideally in computer science or a related field. On the experience side, the company is asking for at least 12 months of manual testing of real software applications, not coursework or a personal project. Someone coming from a QA internship that ran close to a year would likely still qualify, depending on how hands-on that internship actually was. What matters more than the exact title on a past resume is whether the work involved real users, real releases, and real consequences when something got missed.
A Plus, Not a Requirement
None of the following will make or break an application, but they help, and they're the kind of thing that tends to come up naturally once someone's a few months into the role anyway.
- Experience testing across a wider range of devices and screen sizes, not just one phone and one browser
- Some exposure to accessibility testing, like checking screen reader behavior or keyboard-only navigation
- Comfort working inside a sprint-based process, with regular standups and planning sessions
- A first look at test automation, even without deep hands-on expertise there yet
The pace of the work varies by week. When a release is close, there's more to check in less time, and turnaround for bug verification tightens. Between releases, the schedule loosens, and there's more room to dig into edge cases that don't usually get much attention, the kind of testing that's easy to skip when things are busy but tends to pay off later. This particular team runs small, just a few testers covering the whole product between them, which means less specialization and more variety in what a single person covers day to day. Naukri Mitra lists it as a full-time position, though the actual working rhythm has some flexibility built in regarding when hours are logged.
Compensation
The role pays $55,000 a year.
- Health insurance
- Paid time off
- Remote-work flexibility, with the position open to candidates anywhere
- Stock options or profit-sharing, depending on how the company structures that part of the offer
That last piece isn't guaranteed at a fixed amount and can shift depending on the specific offer, but it's a real part of total compensation here rather than a line added just to round out the list. Base pay is reviewed on a set schedule as well, so it's not something a tester has to bring up unprompted to find out where things stand.
How to Apply
A resume works to get started, though a short note about a tricky-to-pin-down bug and how it eventually got traced to its source tends to say more about how someone actually works. Applications are reviewed as they come in, with no set closing date. Given that the position is open worldwide, there's no need to worry about time zone overlap with the hiring team during the application stage; that gets sorted out later, once there's an actual conversation. Candidates who are still building their experience but feel close to the mark shouldn't count themselves out before applying, since the listed requirement describes a reasonable starting point rather than a strict cutoff.
