🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Quality Assurance Engineer (Manual + Automation | SaaS) – Remote Position Type: Full-Time, Remote Working Hours: U.S. Business Hours (flexibility for releases and sprints) About the Role At Pavago, one of our clients is hiring a Quality Assurance Engineer (QA Tester) to ensure software products are thoroughly tested, reliable, and production-ready before release. This is a hands-on QA role combining manual testing, test automation, defect management, API testing, and close collaboration with engineering teams . You’ll act as a critical quality gate throughout the software development lifecycle — identifying bugs, validating fixes, testing edge cases, and helping prevent issues from reaching production. If you naturally look for what could break, think through edge cases, and care deeply about delivering reliable software, this role is a strong fit. What You’ll Own Test Planning & Coverage Create and maintain: Test plans Test cases Test scenarios Acceptance criteria Define appropriate test coverage across new features, integrations, and regression flows. Review requirements and identify potential gaps or risks before development is completed. Collaborate with Product and Engineering teams to ensure requirements are testable and clearly understood. Manual Testing – Core Responsibility Execute: Functional testing Regression testing Integration testing UI/UX validation Cross-browser testing Cross-device testing Identify bugs, inconsistencies, and edge cases before release. Log and manage defects using Jira, Azure DevOps, or similar platforms. Provide developers with clear: Reproduction steps Expected vs. actual behavior Screenshots or recordings Environment details Retest fixes and perform regression testing on impacted functionality. Automation Testing Build, maintain, and improve automated test scripts using tools such as: Selenium Cypress Playwright Automate repetitive and high-value regression scenarios. Integrate automated tests into CI/CD workflows using: GitHub Actions Jenkins GitLab CI Investigate failed automated tests and distinguish product defects from test-script issues. API & Performance Testing Test APIs and backend functionality using Postman or similar tools. Validate: API responses Status codes Data integrity Error handling Integration behavior Conduct performance, load, and stress testing using tools such as: Apache JMeter Locust Support security and vulnerability testing where required. Defect Tracking & Release Validation Track bugs from discovery through resolution. Prioritize issues based on severity, impact, and release risk. Validate builds before production deployment. Conduct regression and release-readiness testing. Clearly communicate critical defects and potential release risks to stakeholders. Documentation & Quality Reporting Maintain organized documentation for: Test plans Test cases Test results Defects Regression suites Track quality metrics including: Defect density Test coverage Pass/fail rates Production defects Provide stakeholders with clear visibility into product quality and release readiness. Engineering Collaboration Work closely with developers to reproduce and investigate defects. Participate in: Sprint planning Daily standups Retrospectives Release discussions Collaborate with Product and Engineering teams throughout the SDLC. Advocate for quality without unnecessarily slowing down delivery. What Makes You a Strong Fit You’ll likely succeed in this role if you: Naturally identify edge cases others overlook. Write clear, structured, and repeatable test cases. Are methodical without becoming a bottleneck. Can clearly explain technical issues to developers. Understand when automation adds value and when manual testing is more effective. Take ownership of bugs through validation and resolution. Care about the overall user experience, not simply whether a test passes. Required Experience & Skills 2+ years of professional QA or software testing experience. Strong hands-on manual testing experience. Experience with functional and regression testing. Experience documenting and tracking defects using Jira or similar tools. Familiarity with test management platforms such as: TestRail Zephyr Familiarity with at least one automation framework: Selenium Cypress Playwright Strong understanding of: Software Development Life Cycle (SDLC) Agile development QA methodologies Defect lifecycle management Strong analytical and problem-solving skills. Clear written and verbal English communication. Nice to Have Experience testing SaaS or enterprise software products . Strong API testing experience using Postman or RestAssured. Experience integrating automated tests into CI/CD pipelines. Familiarity with performance testing using JMeter or Locust. Exposure to security or vulnerability testing. Experience working within compliance-heavy software environments. Familiarity with Git and modern engineering workflows. What a Typical Day Looks Like Your day may start by reviewing new requirements and writing test cases for an upcoming feature. You’ll execute manual tests, run regression suites, investigate failed automated tests, and document any defects you uncover. Throughout the day, you’ll work directly with developers to reproduce issues, validate fixes, test APIs or integrations, and assess whether builds are ready for release. In short: you find and help resolve problems before customers encounter them. Key Metrics for Success High percentage of defects caught before production. Strong regression test coverage. Low number of critical production defects. Fast and accurate defect validation. Reliable automated test suites. Clear and actionable bug documentation. Efficient bug resolution turnaround. Strong stakeholder confidence in release quality. Why This Role Stands Out Direct impact on software and release quality. Hands-on exposure to both manual and automation testing . Close collaboration with Product and Engineering teams. Opportunity to improve QA processes and automation coverage. Fully remote environment. Career growth opportunities into: Senior QA Engineer QA Automation Engineer Software Development Engineer in Test (SDET) QA Lead Quality Engineering Manager Interview Process Initial Phone Screen Video Interview with Pavago Recruiter Practical QA Assessment Client/Technical Interview Offer & Background Verification Apply Now If you have hands-on QA experience, enjoy finding edge cases, and know how to combine manual testing with automation to deliver reliable software, we’d love to hear from you. This is a strong opportunity to build your career in SaaS quality assurance, test automation, and software quality engineering . #QualityAssurance #QAEngineer #SoftwareTesting #ManualTesting #AutomationTesting #Selenium #Cypress #Playwright #SaaS #Jira #RemoteJobs #QualityEngineering
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.