Manual QA Analyst

Magmalabs

1d•Remote

About The Position

Join MagmaLabs, a leading provider of expert software engineers dedicated to helping companies achieve their goals across diverse, high-impact industries. We are actively seeking a seasoned Manual QA Analyst to join our fully remote team. In this role, you will own the human-judgment side of quality across legaltech, fintech, e-commerce, and other sectors where a single incorrect permission or a lost document version is a business problem, not a cosmetic one. Are you a QA Analyst who decides what gets tested, not just someone who runs the cases another person wrote? Join our fully remote team and take ownership of test strategy, exploratory testing, and production triage on a product with deep permission hierarchies, long configurable workflows, and a large volume of documents that different people are allowed to see in different ways. This is the role that finds what a script never will. You will design the test cases and the test data that make complex scenarios reproducible, investigate what breaks in production and drive it to closure, and be the person who can say what was not tested and what risk is still open when a release is on the table. If you believe that knowing what to skip is as much a skill as knowing what to check, we want to hear from you!

Requirements

Minimum of 5 years of software quality assurance experience, with at least 3 years testing complex, business-critical web applications.
Strong command of test design techniques: equivalence partitioning, boundary value analysis, decision tables, and state transition testing.
Demonstrated experience with exploratory testing as a disciplined practice, not as unstructured clicking.
Experience triaging production issues, including the judgment to separate technical severity from business priority.
Experience designing test data for scenarios with multiple roles, permissions, and states.
Working knowledge of SQL to validate data at the source rather than trusting the interface.
Experience validating APIs with Postman or an equivalent tool.
Proficiency with Jira and a test management tool such as TestRail, Zephyr, Xray, or an equivalent.
Excellent written and spoken communication skills in English. Your defect reports are a primary deliverable and will be read asynchronously by people who did not see your screen.
Experience working in Agile environments (Scrum, Kanban, etc.) and collaborating effectively across time zones, with overlap with United States Pacific business hours.
Ability to hold a quality position under schedule pressure, and to explain a technical risk in terms of its business consequence.

Nice To Haves

Ability to read, run, and interpret an existing automated suite (Playwright, Cypress, or Selenium) without owning it.
Experience testing document-heavy or highly configurable SaaS platforms.
Experience in a regulated industry such as legal, healthcare, or financial services.
Familiarity with audit trails, access controls, and data retention requirements.
ISTQB Foundation certification or equivalent formal training in test design.
Experience with accessibility testing against WCAG guidelines.
Experience using AI-assisted tools to draft test cases or summarize exploratory sessions, with the judgment to validate what they produce.

Responsibilities

Analyze requirements and acceptance criteria before development starts, and raise the ambiguities and edge cases that are cheaper to find at that stage.
Design, document, and maintain test cases and test plans, keeping them traceable from requirement to case to result to defect.
Run exploratory testing with a defined charter and scope, and report findings that go beyond the scripted path.
Own the manual regression scope: decide what is worth checking each release based on risk, not on habit.
Triage production issues: reproduce, isolate, assign severity, escalate, and follow through until the fix is verified.
Design and produce complex test data for scenarios involving multiple roles, permission levels, states, and high document volume.
Validate permission hierarchies and tenant-level data isolation, verifying that each role sees exactly what it should and nothing more.
Write defect reports that someone in another time zone can reproduce without asking a follow-up question, with steps, evidence, and environment details.
Report quality status and residual risk to stakeholders so release decisions are made with the full picture.
Partner with automation engineers to hand off the cases that have stabilized, and to keep the automated suite aimed at what actually matters.