This is a fully remote Quality Assurance Analyst position, open to candidates anywhere in the world, paying $65,000 a year for full-time work. The role sits closer to the compliance side of QA than the bug-hunting side. The analyst in this seat spends less time chasing crashes and more time confirming that what actually shipped matches what was specified in the first place. Requirements drift over the course of a project more often than anyone likes to admit, and this role exists to catch that drift before a customer does.
That distinction matters for anyone deciding whether this is the right fit. A QA engineer optimizing for speed and coverage is solving a different problem than an analyst making sure a release meets its stated requirements before it goes out the door. Both jobs matter. They just pull on different skills, and someone who's genuinely good at one isn't automatically good at the other. This role rewards patience with documentation and a willingness to read the fine print of a spec twice before signing off on anything.
Core Responsibilities
- Develop test cases directly from product requirements and execute them against each release
- Document defects in enough detail that a developer can reproduce and fix them without guessing
- Verify that a release actually meets its functional and quality requirements before it goes to deployment, not just that it technically works
- Flag gaps between what a requirements document says and what the shipped product actually does
A recent release passed every functional test cleanly but was still pulled back at final review because a required disclosure notice was missing from the checkout page. Nobody had broken anything in the technical sense. The page simply didn't meet the compliance requirements, and catching that kind of gap before launch is a large part of this role. Finding it a week earlier would have taken one extra pass through the requirements doc; finding it after launch would have meant a scramble and, potentially, a regulatory headache nobody wanted.
Skills and Background
The role leans more analytical than purely technical, though both matter.
- Comfort building test cases directly from a requirements document, not just following a checklist someone else already wrote
- Experience logging and tracking defects inside a bug tracking tool
- The ability to write process documentation clear enough that another person can follow it without extra explanation
- A naturally careful eye, the kind that catches a small mismatch between what was specified and what actually shipped
- Basic SQL, enough to pull or confirm data while verifying a release
A bachelor's degree is the education floor for this role, in computer science or a closely related field. In terms of experience, the team is asking for 18 months spent testing software specifically for quality and requirements compliance, not general QA work more broadly. Someone with a couple of years in a broader QA role that included this kind of requirements-checking would likely still be a strong fit, even if the job title on their resume read differently. What matters more than the exact title is whether the daily work actually involved comparing a finished product against a written standard.
Beyond the Basics
None of these are required, but they help an application stand out. They also tend to be the things that separate someone who tests software from someone who actually understands why a given requirement exists in the first place.
- Some background in regulatory or compliance-driven testing, such as accessibility standards or industry-specific requirements
- Experience preparing documentation for an external audit or formal review
- Familiarity with a structured quality framework, even at a basic level
- A track record of working from detailed specs rather than loose feature descriptions
The workload tends to spike right before a release and settle down after, which is fairly typical for this kind of role. What's less typical is how much of the job runs on written documentation rather than live testing sessions. Someone who enjoys reading a spec closely and comparing it line by line against a real product will likely enjoy this work more than someone who's mainly drawn to exploratory testing. Naukri Mitra lists this position under full-time, though the documentation-heavy rhythm of the work leaves more room for planning your own hours than a typical release-driven QA job would. Deep focus blocks matter more here than constant availability.
What's Included
The role pays $65,000 a year.
- Health insurance
- Paid time off
- Remote-work flexibility, open to candidates anywhere
- Periodic performance reviews that translate directly into pay increases when they're earned
Reviews happen on a set cadence rather than only when someone asks for one, which takes some of the uncertainty out of knowing where things stand and when the next conversation about pay is coming. There's no separate bonus structure layered on top, just the standard review cycle tied directly to actual performance.
To Apply
Send a resume along with an example of test documentation or a defect report you've written, something that shows how clearly you can communicate a gap between what was expected and what actually happened. There's no fixed application deadline; reviews are conducted on a rolling basis as submissions come in. Candidates whose experience leans more general QA than strict compliance testing shouldn't rule themselves out, provided the underlying skill of comparing actual results against a written standard is genuinely there. A short cover note explaining how that skill showed up in a past role is often more useful here than a lengthy list of tools and certifications.
