QA Engineer

Job not on LinkedIn

🔥 3 minutes ago

Apply Now

Find Similar Remote Jobs

Set Up Email Alert For New Jobs

📊 Check your resume score for this job

Improve your chances of getting an interview by checking your resume score before you apply.

Upload Resume

Yo Mobile Games & Computer Services

WebsiteLinkedInAll Job Openings

1 - 10 employees

🎮 Gaming

Gaming • Software

Yo Mobile Games & Computer Services is a company that specializes in both mobile game development and computer services. They offer mobile game and business development services for iOS and Android devices, featuring various apps like So Tricky, So Tricky Flappy Head, T-Shirt Toss, and Hippity Hop, available on the Apple App Store and Google Play Store. Additionally, the company provides PC maintenance, spyware, malware, and virus removal services for small to large businesses. Yo Mobile also offers surveillance system services, emphasizing their comprehensive approach to addressing both gaming and computer service needs.

📋 Description

• Test the Android and iOS bench apps across a range of real devices • Test the admin console: device management, runtime settings, model catalog, releasing a new model without an app release • Verify that telemetry and logs are not just present but correct - the right events, the right values, matching what actually happened on the device • Sanity-check benchmark results (tokens/sec, thermal, battery impact) for plausibility and catch numbers that do not add up before they reach a report • Test yonc.chat (the web chat product): model selection, response rendering, chat behaviour across browsers • Write up bugs and data-quality issues clearly enough for engineers to act on without a follow-up conversation • Build test automation for the parts of this that are worth automating, starting where manual re-testing is most repetitive

🎯 Requirements

• Manual QA experience across mobile apps (Android and iOS) • Comfortable reading structured logs and telemetry, and judging whether the data is correct - not only whether the app crashed • Enough numeracy to sanity-check performance and benchmark data and flag results that look wrong • Experience testing admin/back-office tools: config changes, CRUD flows, permission-sensitive actions • Clear, precise bug reporting