Remote QA Manual Engineer Every product has a moment right before launch where something small — a broken flow, a missed edge case, a form that fails on the third try — either gets caught or gets shipped. This role exists to catch it. We're hiring a Remote QA Manual Engineer who can sit with a feature, poke at it the way a real user eventually will, and flag what needs fixing before it ever reaches them. It's a fully remote position, so your workday doesn't need to match anyone else's clock. What matters is the quality of what you find and how clearly you write it up. You'll be testing new builds, chasing down reported bugs, and confirming that fixes actually hold — not just once, but under conditions nobody thought to script for. Annual salary for this position is $98,500. The Work, Day to Day This isn't a job where you follow a checklist and call it done. Test plans need judgment behind them. Some of what fills your week: Writing manual test cases for new features, patches, and fixes, then running them Reproducing bugs that support or users have flagged, tracing them to their root cause Reading through requirements before development starts, so gaps get caught early rather than late Writing up defects and test documentation that a teammate can pick up without needing you to explain it Sitting in on conversations with developers, PMs, and support to help decide what gets fixed first Doing exploratory testing — going off-script to find the things a written test case would never think to check Keeping Jira tickets current, Notion docs updated, and Slack threads useful rather than noisy Passing along what you learn to teammates so the whole team's testing gets sharper over time What You'll Need Good testers tend to have a slightly suspicious streak — they don't trust that something works just because it looks like it does. A few specifics we're looking for: Experience: At least 2 years in hands-on manual QA Education: Bachelor's degree, minimum Test cases and bug reports you've written that other people could actually follow The ability to explain a bug to an engineer and its impact to someone non-technical, without losing either audience Comfort working solo for long stretches, since remote work means fewer built-in check-ins A habit of raising concerns about a requirement before it turns into three days of rework Good to Have, Not Required Some background with sprint planning, backlog grooming, or other agile rituals Time spent in Jira, Notion, Confluence, or similar tools Any exposure to cloud testing platforms or real device labs Curiosity about automation, even if you haven't built anything yet Why This Team, Specifically QA here isn't a rubber stamp applied after the real decisions are already locked in. Testers sit in on planning, push back on risky requirements, and have a real say in what ships and when. Candidates browsing roles on Naukri Mitra often ask what that looks like in practice — in this case, it means your name is attached to the calls you make, not buried in a ticket queue. Because the setup is remote-first, you're judged on what you catch and how you communicate it, not on green dots next to your name in Slack. Standups run over Zoom, docs live in Notion, and Jira keeps the whole pipeline visible, so nothing quietly falls between design and delivery. Benefits Remote work with flexible hours, regardless of time zone Health coverage for you and eligible dependents Paid time off, plus standard holidays Budget and support for QA certifications or relevant courses Performance-based bonus A real path toward senior QA, QA lead, or broader process ownership How the Team Actually Works Bug reports here don't disappear into a queue nobody reads. Developers, PMs, and QA are in the same threads, and feedback runs both directions — someone questioning your test case is normal, not a slight. When something breaks, the instinct is to figure out why, not who. Given the spread of time zones on this team, most communication is written down rather than said out loud in a meeting. A clear Slack message or a well-documented handoff usually does more than a call ever could. Applying If you tend to notice what's slightly off before anyone else mentions it, send us your application. Include a couple of test cases or bugs you're genuinely proud of — the kind that made a difference. We welcome applicants from the United States, Canada, the United Kingdom, the European Union, Australia, India, and other regions that support remote employment.