Full Time
PHP 50,000–65,000 per month
40
Sep 11, 2026
ABOUT THE ROLE
We are a growing U.S.-based software company seeking a meticulous, experienced Manual QA Analyst to join our product-development team full-time.
You will be embedded in the development workflow. You will review requirements, prepare test coverage, test exact staging and TestFlight builds, report defects in Jira, verify fixes, maintain regression coverage, and provide evidence-based release-readiness recommendations.
This is a manual testing position. You will not be expected to work as a software developer.
Company and product details will be shared with shortlisted candidates.
WHAT YOU WILL DO
Development workflow and Jira
- Review feature requirements and acceptance criteria before development is completed.
- Identify unclear requirements, missing edge cases, and areas that may be difficult to test.
- Prepare or update manual test cases while features are being developed.
- Pick up work in Jira when a developer moves it to Ready for QA.
- Move assigned work into QA In Progress when testing begins.
- Record all testing against the exact staging URL, TestFlight build, application version, device, and operating-system version used.
- Return failed work to Changes Required with complete supporting evidence.
- Retest fixes when the developer submits a new build.
- Move passing work to Ready for Release with a concise QA summary.
- Keep Jira statuses and defect records current without needing repeated reminders.
Manual mobile and web testing
- Manually test iPhone, iPad, and browser-based application workflows.
- Test complete end-to-end processes that cross between the mobile application and web platform.
- Install and test prerelease iOS/iPadOS builds through TestFlight.
- Perform functional, frontend, usability, exploratory, regression, integration, and release testing.
- Verify screens, buttons, forms, navigation, loading states, permissions, validation, error handling, and responsive layouts.
- Test different account states, user roles, network conditions, permissions, devices, and operating-system versions.
- Look beyond the happy path and actively search for edge cases and unintended behavior.
- Run smoke and regression testing before releases.
- Perform limited post-release verification using authorized test accounts and fictional data.
Bug reporting and verification
Every bug report should include:
- A concise, descriptive title
- The exact build and environment tested
- Device model, browser, and operating-system version
- Preconditions and relevant account state
- Numbered steps to reproduce
- Expected versus actual results
- Frequency or reproducibility
- Severity and likely customer impact
- Screenshots, screen recordings, or other supporting evidence
You will also:
- Distinguish release-blocking defects from minor issues.
- Reproduce and investigate inconsistent problems.
- Verify reported fixes rather than assuming they work.
- Reopen defects that are incomplete or cannot be verified.
- Create separate linked bugs when testing reveals an issue outside the original feature’s scope.
- Maintain regression cases so previously fixed problems do not return.
Release readiness
For each release candidate, provide a clear written result:
- PASS
- PASS WITH KNOWN RISKS
- FAIL
- BLOCKED
The report must identify:
- The exact build tested
- Devices, browsers, and operating systems covered
- Test cases completed
- Tests that failed or could not be completed
- Open defects
- Known limitations
- Remaining release risks
- Your GO/NO-GO recommendation
QA provides the evidence and recommendation. Final merge, deployment, and production decisions remain with the authorized release owner.
REQUIRED QUALIFICATIONS
- At least two years of professional manual software QA experience.
- Experience testing both mobile applications and web applications.
- Experience testing complete end-to-end workflows.
- Strong knowledge of functional, regression, exploratory, usability, and release testing.
- Experience using Jira or a similar issue-tracking platform.
- Ability to create organized test plans, test cases, checklists, and release summaries.
- Excellent written English. Bug-report clarity is extremely important.
- Strong spoken English for meetings and defect discussions.
- Excellent attention to detail and analytical judgment.
- Ability to work independently and take ownership of assigned testing.
- Comfortable collaborating with developers, product owners, and customer-support staff.
- Reliable computer, stable high-speed internet, backup internet or power plan, and screen-recording capability.
- Ability to handle confidential information and follow security and test-data procedures.
TESTING-DEVICE PREFERENCE
Preference will be given to applicants who already own an iPhone Pro or iPad Pro with LiDAR capability.
Applicants must state the exact model and current iOS/iPadOS version of every Apple device they can use for testing. Do not provide a serial number or IMEI.
Owning a compatible Pro device is strongly preferred but is not an absolute requirement. A company-owned testing device may be provided to an exceptional candidate after successful completion of the interview, reference-check, and paid-assessment process.
Candidates will never be required to purchase company equipment using their own money.
PREFERRED EXPERIENCE
The following experience is helpful but not required:
- TestFlight and prerelease iOS application testing
- SaaS or business-software testing
- Role and permission testing
- File upload, camera, sensor, scanning, or LiDAR-based application testing
- Testing workflows that cross between a mobile application and administrative web portal
- Basic API or application-log inspection
- Working directly with remote U.S. development teams
SCHEDULE
- Full-time, 40 hours per week
- Monday through Friday
- Consistent daily schedule
- At least four working hours must overlap with U.S. Eastern business hours
- Exact schedule will be agreed upon before employment begins
- Additional coordination may occasionally be needed during major releases