Video Editor (CapCut/VEED/etc) Needed to Bug Hunt + QA Test Our Video Editing Web App (Satura)
Budget: $30 – $250 USD
We’re looking for an experienced video editor (not just a generic QA tester) to bug hunt inside our web-based video tool, Satura.
You’ll get free access to Satura and your job is to spend 1–2 days testing it like a real editor would, trying to break things, pushing edge cases, and documenting everything clearly.
This is ideal if you’ve worked with tools like CapCut, VEED.io, Clipchamp, Premiere, Final Cut, Descript, etc. We want feedback from someone who knows what “normal” behavior should feel like in an editing workflow.
What you’ll do
Use Satura for ~1–2 days and actively try to find bugs / broken flows
Test across common editor behaviors:
importing/uploading files
trimming/cutting
captions/subtitles
exports/renders
timeline interactions
playback, audio sync, UI glitches
slowdowns, crashes, weird edge cases
Create a very detailed Google Doc with:
Bug title
What happened (actual behavior)
What you were trying to do (intended use)
What should have happened (expected behavior, based on your experience)
Steps to reproduce
Screenshots (required) + short screen recordings if helpful
Browser/OS details (ex: Chrome on Mac, etc.)
Severity rating (Blocker / Major / Minor)
Deliverable
A single organized Google Doc (with headings + a bug list) that we can hand directly to our dev team.
Requirements
Strong experience editing videos using tools like CapCut / VEED / Clipchamp / Premiere / Final Cut / Descript
Very detail-oriented (you document things clearly, like a pro)
Comfortable writing structured bug reports with screenshots
Must be able to start quickly
Nice to have
Prior QA / product testing experience
Familiar with web apps / browser-based editing tools
Loom / screen recording for tricky bugs
To apply, include
What editing tools you’ve used most (CapCut / VEED / etc.)
Your OS + browser (Mac/Windows, Chrome/Safari, etc.)
A short example of how you’d write a bug report (even a fake one is fine)
Your availability to test in the next few days
You’ll get free access to Satura and your job is to spend 1–2 days testing it like a real editor would, trying to break things, pushing edge cases, and documenting everything clearly.
This is ideal if you’ve worked with tools like CapCut, VEED.io, Clipchamp, Premiere, Final Cut, Descript, etc. We want feedback from someone who knows what “normal” behavior should feel like in an editing workflow.
What you’ll do
Use Satura for ~1–2 days and actively try to find bugs / broken flows
Test across common editor behaviors:
importing/uploading files
trimming/cutting
captions/subtitles
exports/renders
timeline interactions
playback, audio sync, UI glitches
slowdowns, crashes, weird edge cases
Create a very detailed Google Doc with:
Bug title
What happened (actual behavior)
What you were trying to do (intended use)
What should have happened (expected behavior, based on your experience)
Steps to reproduce
Screenshots (required) + short screen recordings if helpful
Browser/OS details (ex: Chrome on Mac, etc.)
Severity rating (Blocker / Major / Minor)
Deliverable
A single organized Google Doc (with headings + a bug list) that we can hand directly to our dev team.
Requirements
Strong experience editing videos using tools like CapCut / VEED / Clipchamp / Premiere / Final Cut / Descript
Very detail-oriented (you document things clearly, like a pro)
Comfortable writing structured bug reports with screenshots
Must be able to start quickly
Nice to have
Prior QA / product testing experience
Familiar with web apps / browser-based editing tools
Loom / screen recording for tricky bugs
To apply, include
What editing tools you’ve used most (CapCut / VEED / etc.)
Your OS + browser (Mac/Windows, Chrome/Safari, etc.)
A short example of how you’d write a bug report (even a fake one is fine)
Your availability to test in the next few days
Related categories:
Software Testing
Final Cut Pro
Video Production
Video Editing
Adobe Premiere Pro
Documentation
Google Docs
CapCut