Browse jobs 🎯
14 open gigs · newest first
RecipeRelay: generic runthrough and report for report export
Looking for practical, no-fluff feedback on RecipeRelay. The session should answer: does checkout make sense, does report export work reliably, and does settings feel polished enough for launch? Device coverage: OnePlus 12 (Android 14).
LearnLoop: bug hunt for settings
QA brief for LearnLoop: bug hunt. Begin with the intended happy path, then spend most of the time around settings, search, permissions. I want issue titles that an engineer can scan and reproduce without a follow-up call. Use Pixel 8 (Android 15) and Galaxy S24 (Android 14).
ClipCart: UX feedback for profile setup
Sanity-check ClipCart before more users arrive. Priority areas: profile setup, settings, subscription flow, login. For anything you report, separate launch blockers from polish notes and mention the exact device/browser used. Target coverage: Windows 11 laptop (Chrome / Edge) and Ubuntu workstation (Firefox).
BoardBloom: release smoke test for checkout
This is a founder-facing release smoke test for BoardBloom. Try the happy path first, then intentionally stress checkout and accessibility. We care more about three actionable findings than a long vague list. Cover Samsung tablet (Android 14).
LearnLoop: gameplay and onboarding for report export
LearnLoop has a gameplay and onboarding slot open. Please behave like a slightly impatient real user: skim copy, try the obvious route, and see where onboarding, sharing, report export slow you down. Note device/browser context from OnePlus 12 (Android 14).
BoardBloom: bug hunt for checkout
Release check for BoardBloom: - Test style: bug hunt - Main areas: checkout, first-run tutorial, offline states, onboarding - Devices: Pixel 8 (Android 15), Galaxy S24 (Android 14) - Outcome wanted: concise issues, severity, and what you would fix first.
RecipeRelay: UX feedback for permissions
RecipeRelay needs a skeptical pass before we invite customers. Walk through offline states normally, then revisit error handling and permissions with bad inputs, slow network assumptions, or edge-case behavior in mind. Note what happened on Samsung tablet (Android 14) and OnePlus 12 (Android 14).
FitForge: Accessibility pass for mobile layout
We want a concise release-readiness report for FitForge. Cover accessibility, profile setup, notifications, record device/browser details, and separate critical bugs from product feedback. Include one practical next step for every major finding.
BudgetBridge: Launch QA for privacy
Use BudgetBridge as if you were evaluating whether to keep it installed. Focus on privacy, onboarding, subscription flow, mobile layout, then report bugs, friction, missing states, and any copy that creates hesitation.
ClipCart: feature validation for file upload
Run ClipCart like a customer who will not forgive rough edges. Cover report export, file upload, mobile layout, then write a short "would I keep using this?" verdict with the bugs or UX issues that most influenced it. Device set: Pixel 8 (Android 15).
PetPath: First-session test for notifications
Pre-release QA request for PetPath. Run the feature validation pass as a normal user first, then list the top five risks you found across offline states, notifications, mobile layout. For each risk, say how serious it is and whether you could reproduce it on Low bandwidth 4G profile, OnePlus 12 / Android 14 and Steam Deck / SteamOS.
GreenCart: UX teardown for checkout
We need a grounded feature validation pass for GreenCart, not a generic checklist. Follow the app's main promise, then branch into mobile layout, error handling, checkout and write down the exact moments where reality doesn't match expectation. Use Samsung Tab S9 / Android 14, Pixel 8 / Android 15 and Samsung A54 / Android 13.
BudgetBridge: Launch QA for onboarding
A small release is going out for BudgetBridge. Validate subscription flow and privacy first; only go deeper into onboarding if the basics are stable. Mark findings as blocker, should-fix, or nice-to-fix. Devices: Low bandwidth 4G profile, OnePlus 12 / Android 14 and Steam Deck / SteamOS.
HabitHarbor: Human QA for settings
HabitHarbor needs a practical human QA pass before the next release. Start with offline states, then push on onboarding and settings. Include severity, repro steps, expected vs actual behavior, and the fastest changes that would improve confidence.