Open Bardeen and try one template/playbook/scraper using free credits only
Stop if it demands a card before any playbook can run
What counts as a problem: cannot start without paying, install failure, first playbook blocked, unclear onboarding.
Deliverable:
Record a narrated screen-and-microphone video of the complete test. Talk through what you are doing, every error, and anything confusing.
Submit written findings. For every issue include a short title, severity (critical/high/medium/low), exact reproduction steps, expected vs actual, and a video timestamp.
Include at least one concrete observation even if you find no bugs.
Do not use production credentials or secrets. Do not enter a credit card or payment method. Do not OAuth GitHub, GitLab, or Bitbucket. Do not connect personal work accounts.
Stop at the first paywall, waitlist, sales-demo-only trap, or identity/OAuth gate and report it. That is a valid complete result.
Use a tester-owned email if signup is required. Never expose passwords, one-time codes, or payment information in the video or writeup.
Send video evidence for every issue in the accepted tester chat.
Record your screen and microphone audio for the full test. Narrate your actions, every error you find, and anything confusing, poor, or worth improving.
Attach the narrated video as an MP4, MOV, or WebM no larger than 512 MB, plus at least one representative screenshot.
For each issue include a short title, a severity (critical/high/medium/low), and exact steps to reproduce.
Submissions are reviewed automatically. $10.00 is released per accepted submission.
Tester requirements:
Access to a device that can open the target URL
Record a narrated screen video plus written findings with repro steps
What you must do to be paid
Before you apply
Access to a device that can open https://www.bardeen.ai/start
Access to a device that can open the target URL
Record a narrated screen video plus written findings with repro steps
One-time outbound QA of Bardeen.
Start at https://www.bardeen.ai/start (not the homepage). Product is largely a Chrome extension. About 100 free credits/month. Use free credits only.
Journey:
1. Open https://www.bardeen.ai/start
2. Get the Chrome extension (Chrome Web Store is OK)
3. Install the extension
4. Open Bardeen and try one template/playbook/scraper using free credits only
5. Stop if it demands a card before any playbook can run
What counts as a problem: cannot start without paying, install failure, first playbook blocked, unclear onboarding.
Deliverable:
- Record a narrated screen-and-microphone video of the complete test. Talk through what you are doing, every error, and anything confusing.
- Submit written findings. For every issue include a short title, severity (critical/high/medium/low), exact reproduction steps, expected vs actual, and a video timestamp.
- Include at least one concrete observation even if you find no bugs.
- Do not use production credentials or secrets. Do not enter a credit card or payment method. Do not OAuth GitHub, GitLab, or Bitbucket. Do not connect personal work accounts.
- Stop at the first paywall, waitlist, sales-demo-only trap, or identity/OAuth gate and report it. That is a valid complete result.
- Use a tester-owned email if signup is required. Never expose passwords, one-time codes, or payment information in the video or writeup.
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
1Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
2Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
3Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
4Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot. Speak your findings aloud while recording whenever you can: narration is strongly encouraged and makes your report far more useful, but it is not required and a quiet recording will still be reviewed on its merits.
5Map every attachment to the reportIn the same chat message as each upload, explain what every attached file shows and which tested step or finding it supports.
6Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
7Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
β’
Access to a device that can open the target URL
β’
Report every issue with a severity and exact reproduction steps
β’
Only submit evidence you captured yourself during this run
β’
Access to a device that can open the target URL
β’
Record a narrated screen video plus written findings with repro steps
SKILLS NEEDED
Access to a device that can open the target URLRecord a narrated screen video plus written findings with repro steps