Full 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