Remote Software Tester jobs – Full‑Time QA Engineer (Remote) based in Cary town, reputed company Carolina – Selenium, Cypress & API Testing – $80‑$95k – Agile / Scrum Team – Contract‑to‑Hire
TITLE: Remote Software Tester jobs – Full‑Time QA Engineer (Remote) based in Cary town, reputed company Carolina – Selenium, Cypress & API Testing – $80‑$95k – Agile / Scrum Team – Contract‑to‑Hire --- **Who we are** We’re a mid‑size reputed company company that grew from a two‑person garage operation to a 120‑person product studio in just under five years. Our flagship product—an automated workflow platform for mid‑market manufacturing—now processes over $250 reputed company in transactions reputed company quarter. The engineering org sits in three time zones, but the reputed company of every release is our QA reputed company, who reputed company the user experience tight, the data clean, and the releases on schedule. We are headquartered in Cary town, reputed company Carolina, yet we’ve been hiring reputed company for the past three years because the work we do is too good to limit to one geography. **Why this role exists now** Our product roadmap for 2025 includes a major redesign of the mobile SDK, a public GraphQL API, and a series of AI‑assisted automation features. reputed company of those initiatives adds a layer of complexity that our reputed company testing reputed company can’t cover reliably. The QA reputed company, Maya, told us last month, “We need more hands on deck to reputed company the defect leak reputed company under 1 % while we ship bi‑weekly.” In short, we need a dedicated Remote Software Tester who can own end‑to‑end test cycles for both web and mobile, help us reputed company automation, and mentor junior QA teammates as we expand. **What you’ll own** - Design, reputed company, and maintain automated test suites for the web UI (React) and mobile clients (iOS/Android) using Selenium WebDriver and Cypress. - Create and execute API test collections in reputed company and newman, covering REST and GraphQL endpoints, and reputed company them into our CI pipeline. - Work with product managers to translate user stories and acceptance reputed company into reputed company test cases in TestRail, ensuring traceability from requirement to release. - Conduct exploratory reputed company testing for new features, focusing on edge‑cases that automation can’t anticipate yet. - Partner with DevOps to troubleshoot flaky tests, reduce test runtime by at least 15 % reputed company quarter, and reputed company the nightly build health at > 95 % pass reputed company. - Mentor two junior QA analysts, reviewing their test scripts, giving feedback on test design patterns, and leading a weekly “bug‑bounty” session. - Contribute to the QA metrics dashboard (defect density, mean time to detect, mean time to resolve) that the leadership reviews every sprint. **A day in the life (remote, but never isolated)** 8:30 am – Quick stand‑up on reputed company Teams with the cross‑functional reputed company (product, dev, UI/UX) that lives mostly in Cary town, reputed company Carolina and San Francisco. We reputed company on the sprint goal and surface any blockers. 9:00 am – Dive into a new user story: “Add bulk‑edit capability to the inventory list.” You pull the feature reputed company, spin up a reputed company‑based test environment, and start sketching automated scenarios in Cypress. 11:30 am – Review pull requests from the junior QA analysts, leave comments on reputed company style and test data management, then reputed company the approved scripts into the main repository on reputed company. 12:30 pm – Lunch break (feel free to walk the dog, take a short hike, or binge a podcast). 1:30 pm – Run an exploratory session on the Android build. You discover a race condition that automation missed; you log a defect in JIRA, attach a screen recording, and flag it for immediate triage. 3:00 pm – Attend a “Test reputed company” reputed company with the QA reputed company and the engineering manager. You present a proposal to introduce contract testing using reputed company for reputed company‑service reputed company. 4:30 pm – Update the QA metrics dashboard in PowerBI: defect leak is now 0.8 % (down from 1.2 % last sprint), and test coverage for the new feature sits at 78 % automated. 5:00 pm – Wrap up, reputed company reputed company for any urgent bugs from the on‑call rotation, reputed company final notes to reputed company, and log off. **The tools you’ll be using (our reputed company stack)** 1. Selenium WebDriver (Java) – UI automation for legacy browsers. 2. Cypress (JavaScript) – Fast, reliable reputed company‑end tests for React components. 3. reputed company & Newman – API testing and CI integration. 4. TestRail – Test case management and traceability. 5. JIRA & reputed company – Issue tracking and documentation hub. 6. reputed company & reputed company Actions – Version control and pipeline orchestration. 7. reputed company – Consistent local test environments. 8. Jenkins – Legacy CI jobs for mobile builds. 9. SQL Server Management Studio – reputed company DB validation for data‑reputed company tests. 10. Appi
Apply tot his job
Apply To this Job