The Role
We are looking for a detail-obsessed QA Engineer to own quality across PlaySuper's core product surfaces: the in-game SDK touchpoints, the studio-facing console, and the end-to-end integration flow. You will be hands-on — playing games on physical devices, clicking through studio workflows, finding what breaks, and documenting it with precision.
This is our first dedicated QA hire. You will build the test case library and regression checklist from scratch, work directly with engineers, and your sign-off will gate every SDK release that goes to our studio partners.
What You Will Do
In-Game SDK & Placement Testing
● Install PlaySuper-integrated game builds on physical Android and iOS devices and verify that commerce touchpoints appear on the correct screens, at the correct moments in the game flow.
● Validate placement visuals against the game's style: correct colours, fonts, sizing, asset quality, no overlapping UI elements, no z-index or clipping issues.
● Test across a device matrix — low-end (2GB RAM), mid-range, and flagship devices — and across screen sizes and resolutions.
● Validate all touchpoint states: first impression, repeat impression, coin balance too low, post-purchase, dismissed state, and error fallback.
● Test edge cases: no internet connection, mid-session app backgrounding, language/locale switching, first-time user flow.
● Regression test every SDK build before it is shared with studios. Maintain a signed-off build log.
Studio Console Testing
● Test the end-to-end studio onboarding flow: screenshot upload, game fingerprint extraction,
placement recommendation display, revenue forecast range, placement selection, and one-click
deploy.
● Verify placement mockup previews render correctly across different game visual styles (flat,
cartoon, material, dark/light theme).
● Test error and empty states: failed uploads, unsupported file types, missing data from analytics
connectors, slow network conditions.
● Validate form inputs, validation messages, loading states, and responsive layout across Chrome,
Safari, and Edge.
Integration & Data Validation
● Manually verify that data from connected analytics tools (AppsFlyer, Firebase, GameAnalytics)
appears correctly in the PlaySuper console after studio connects their accounts.
● Spot-check that cohort breakdowns, event counts, and session metrics in the console are
consistent with what the studio sees in their own tools.
● Test the game code integration flow: verify that Claude-generated Unity integration code, when
applied to a test game project, produces placements that render correctly.
Bug Reporting & Documentation
● Write clear, reproducible bug reports with: steps to reproduce, expected vs. actual behaviour,
device/OS/build version, and annotated screenshots or screen recordings.
● Maintain a structured test case library in Notion or Linear covering all product surfaces.
● Run and document regression suites before every release. Provide a written QA sign-off
summarising coverage and any known issues.
● Participate in sprint planning to flag testability concerns early — before features are built.
What We Are Looking For
Must-Have
● 2–4 years of manual QA experience on mobile applications.
● Experience testing on physical Android devices — not just emulators.
● Strong visual eye: you notice a misaligned button, a font weight change, an image that rendered
at half resolution.
● Structured, precise bug reporting. Engineers should be able to reproduce your bugs on the first
try, every time.
● Familiarity with bug tracking and test management tools (Linear, Jira, Notion, or equivalent).
● Basic understanding of how mobile apps and APIs work — you do not write code, but you know
what a network request is, what a build version means, and how to read a crash log.
Strong Plus (Nice to Have)
● Experience with mobile games — even as a regular player. Understanding what feels native vs.
intrusive in a game UI is directly applicable.
● Experience testing third-party SDKs or integrations in mobile apps.
● Exposure to Charles Proxy or similar tools for inspecting HTTP traffic.
● Familiarity with Android Developer Options (layout bounds, GPU overdraw, animation speed).
● iOS testing experience.
Follow Cutshort