VA - Product Testing Assistant

Start your application with MANGO.

We need a part-time VA / product testing assistant for Carby, a carb-conscious meal planning app. This is practical user-flow testing and evidence organization, not generic design opinions.

Paid test assignment:
- Submit the test here: ----------
- First record a 3 minute web app tech check on a phone browser with microphone audio.
- Then record a separate iPhone app review if you have real iPhone access.
- Use the test web app URL: ---------- and start from the beginning of the normal funnel. Do not skip directly to checkout.
- If checkout asks for payment, use Stripe test card ---------- with any future expiry, any CVC, and any ZIP/postal code.
- Follow instructions exactly, think out loud while testing, organize your findings clearly, and include a Google Doc with video links, repro steps, severity, and what confused you.
- Test in two modes: robot mode follows the exact normal flow; chaos mode tries to break real-user intent with realistic cases like in-app browser, old account, already subscribed account, app already installed, reinstall, slow connection, double taps, refresh, app switch, and kill/reopen.
- Focus on previously unknown issues that could hurt quiz completion, checkout trust, payment, activation, retention, meal-plan use, grocery-list use, or trust.
- Paywall clarity: do not answer whether you personally would buy. Narrate what you believe is happening: am I paying today, when will I be charged, how much, can I cancel, and what happens after I install?
- Paid handoff/sign-in is critical: after checkout/trial, test app install/open/sign-in/access. If possible, cover iOS Safari, Instagram browser, TikTok browser, already-installed app, and not-installed app.
- Vague reports like 'it did not work' need exact screen/action, repro context, and session ID or account identifier if available.
- Include one final answer: what is the single ---------- nt most likely to make a real user quit before getting a useful meal plan/grocery list?
- Include the word crispy in the severity section so we know you read the instructions.

Good assistants are detail-oriented, can follow a checklist, record narrated evidence, organize links/docs cleanly, and explain exactly where a user got confused or stuck.
Bad submissions are broad opinions, silent recordings, old portfolio samples, skipped instructions, or minor polish with no user-flow impact.