QA test: Shooting Draft: End-to-End Creative Exploration — 2026-09-16

Before you apply

• Access to a device that can open https://app.shootingdraft.com/
• Filmmaking, content creation, or generative AI video creation experience (professional, indie, or hobbyist) — verified against LinkedIn profile or uploaded resume
• Familiarity with screenwriting concepts and workflow
• Access to a desktop or laptop with a screen recording tool

Task

You are a creative tester with a real screenplay idea - bring it. You'll receive free AI writing credits and media generation credits as a test user (no card, no password required), so use them freely and go as far as you want. Sign in using the magic-link email sent to you after acceptance. From there, explore the app however you like. The one anchor: take your own screenplay idea as far as possible through the full pipeline. **Core journey to attempt:** 1. Sign in via magic-link email (no password, no card needed) 2. Start a new project and develop your screenplay idea - write or generate a draft using the AI-assisted screenwriting tools 3. Build out your cast and world (characters, locations, tone) 4. Storyboard scenes 5. Generate media: images, video clips, voices, and/or music 6. Try an export of your work Beyond that: click anything, break anything, and tell us what happened. No flow is off-limits. **Evidence to submit:** - A full screen recording of your entire session. Please narrate out loud as you go - talk through what you're doing, what confuses you, what delights you, and any errors or unexpected behavior. Silent video is accepted but narration is the most valuable thing you can provide. - A short written report covering: what confused you, what you'd pay for, what you'd never use, and one thing you'd change. - Screenshots of anything broken, unexpected, or worth highlighting. Report all bugs with clear reproduction steps: what you did, what you expected, and what actually happened.

Submission requirements

Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.

1. 1Sign in via magic-link emailUse the magic-link email sent to you after acceptance to sign in. No password or card required. Evidence should show successful sign-in and access to the app dashboard.
2. 2Start a project and write or generate a screenplay draftCreate a new project using your own screenplay idea. Use the AI-assisted writing tools to draft or develop your script. Evidence should show the project created and meaningful writing or generation progress.
3. 3Build out your cast and worldDevelop your characters, locations, and world details within the app. Evidence should show the cast and world-building features in use.
4. 4Storyboard at least one sceneUse the storyboarding tools to map out at least one scene from your screenplay. Evidence should show a storyboard created or in progress.
5. 5Generate at least one media assetUse the media generation tools to create at least one asset — an image, video clip, voice, or music track. Evidence should show a generation attempt and its result, including any errors.
6. 6Attempt an exportExport your work in any available format. Evidence should show the export flow and the resulting file or confirmation, or any error encountered.
7. 7Submit written report and bug screenshotsInclude a short written report covering: what confused you, what you'd pay for, what you'd never use, and one thing you'd change. Attach screenshots of anything broken or unexpected, with reproduction steps.
8. 8Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
9. 9Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
10. 10Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
11. 11Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot.
12. 12Map 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.
13. 13Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
14. 14Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.