Manual Tester (QA)

CUBE84; Qatar; On-site; QAR 110,000 - 170,000; Full time

Job summary

CUBE84 is seeking a QA Engineer (Manual, Web & Mobile) to ensure robust, defect-free software before release. You’ll craft test plans, write cases from requirements, and push beyond happy paths into edge cases. You’ll verify across browsers and devices, including mobile apps, and validate Salesforce-backed data against the UI.

You will collaborate with PMs and clients in an agile environment. Experience with API testing (Postman) and SQL data checks is important, as is clear reporting and

Qualifications

• 3 to 5 years of manual testing across web and mobile apps.
• Fundamentals of QA: test plans, test cases, scenarios, defect lifecycle.
• Experience with cross-browser and cross-device testing in real projects.
• Ability to read console and network tabs to identify failures.
• Good English communication with clients and teammates.
• Familiarity with Salesforce-backed apps and UI data checks.
• Comfort with Postman API testing and SQL data verification.
• Experience in Agile/Scrum environments and UAT support.

Responsibilities

• Write test plans, scenarios, and cases from requirements and designs.
• Test web apps across Chrome, Safari, Firefox, Edge and various screen sizes.
• Test mobile apps on Android and iOS on real devices and emulators.
• Verify Salesforce records, profiles, permissions, and validation rules against UI.
• Test end-to-end integrations: login, payments, notifications, and third-party services.
• Log clear bugs with steps, expected vs actual, environment, and evidence; re-test fixes.
• Maintain regression suite and support UAT with project managers and clients.
• Identify risks early and communicate them before releases.

Skills

Manual testing

Cross-browser testing

Cross-device testing

Test planning

Test case development

SQL data validation

Bug reporting

English communication

Agile/Scrum

UAT support

Tools

Postman

Jira

TestRail

Zephyr

Xray

Selenium

Playwright

Cypress

Appium

TestFlight

Play Console

Salesforce

Job description

QA Engineer (Manual, Web & Mobile)

When you open a form, do you go straight to the empty fields, the 300-character name, and the double-click on Submit? Can you trace a bug from what’s on screen to the network tab, and then to the record in Salesforce? Do your bug reports get fixed without anyone coming back to ask you a question?

Then, our QA Engineer role here at CUBE84 may interest you.

In this gig,

1. You break it before the client does - You'll write test plans, scenarios, and cases from requirements, designs, and acceptance criteria. Then you'll go past the happy path into error states, empty states, boundaries, and negative cases. Your goal is to make sure nothing surprises anyone in UAT.

2. Every screen, every size - You'll test webpages and web apps on Chrome, Safari, Firefox, and Edge, at different screen sizes and text scales. You'll test mobile apps on Android and iOS, on real devices and on emulators or simulators, across OS versions. A layout that works on the latest iPhone has to work on a three-year-old Android too.

3. You check what's underneath - Many of our apps run on Salesforce. You'll check records, profiles and permissions, and validation rules, and confirm the app shows what Salesforce actually holds. You'll use Postman and SQL to compare the API responses and the data with what's on screen.

4. The integrations have to hold up - Login, payments, notifications, and third-party services are where things tend to break. You'll test each of these end to end and find the weak points before a release does.

5. Your bug reports need no follow-up - Each bug you log will have clear steps, expected versus actual, the environment, and evidence. A developer reading it at 11 PM should reproduce it on the first try. You'll re-test the fixes and run regression before every release.

6. You keep releases on track - You'll install release builds from TestFlight, Play Console, and staging, and verify them. You'll support UAT with project managers and clients until sign-off. You'll keep the regression suite current as features change.

7. You raise issues early - If a requirement is vague or a release looks risky, you'll say so early, while there's still time to fix it.

It'll be awesome if you...

• Have 3 to 5 years of manual testing across both web and mobile apps (this one's non-negotiable)

• Know QA fundamentals well: test plans, cases, and scenarios, the bug life cycle, and severity versus priority

• Have done functional, regression, smoke, sanity, integration, exploratory, UAT, cross-browser, and cross-device testing in real projects

• Use browser dev tools for responsive checks, cross-browser testing, and form validation, and read the console and network tab to find the cause of a failure

• Test on Android and iOS, on real devices and on emulators or simulators, and install builds from TestFlight and Play Console tracks

• Are comfortable testing Salesforce-backed apps, including records, profiles and permissions, and validation rules, and checking the UI against the data in Salesforce

• Test APIs in Postman, including headers and auth tokens, and check the responses against the UI

• Write SQL SELECT queries with joins and filters to verify data

• Work in Jira with a test management tool such as TestRail, Zephyr, or Xray

• Write bug reports someone else can reproduce from the steps alone, with evidence attached

• Work in Agile and Scrum sprints, from acceptance criteria

• Write and speak clear English with clients and teammates

More awesome, if you have

• Admin-level Salesforce skills: permission sets, record types, flows, and reports and dashboards

• Experience Cloud or community site testing

• Exposure to Selenium, Playwright, Cypress, or Appium, and an interest in growing into automation

• API automation with Postman collections and Newman

• Performance or load testing basics in JMeter

• Accessibility testing against WCAG, plus localization and right-to-left testing

• Awareness of the OWASP Top 10

• Experience picking up and verifying release builds from a CI/CD pipeline

• ISTQB Foundation certification

• Domain experience in nonprofit, healthcare, housing, education, or the public sector