Customer Experience Test Automation Intern

• Be a Champion Team
• Prioritize Ruthlessly
• Ship fast, Quality Follows
• Obsess over customers

Be a part of this exciting journey with us!

About the Role

OpusClip is hiring a CX Test Automation Intern: a software-developer-in-test who sits inside the Customer Experience team and turns real customer tickets into automated UI end-to-end tests. You will be the first person in a new lane we call customer-originated requirements: the thousands of support conversations we handle each month are a rich record of how OpusClip actually gets used and where it breaks, and nobody has yet turned that record into a repeatable test battery.

This is a 4-month co-op based in Vancouver, starting January 7, 2027, with the option to extend for a further 8 months. The first 4 months hold a bounded, well-defined backlog that is valuable on its own; the extension is a decision we make together, not an assumption.

You will work with AI coding tools (Claude Code, Codex) every day, ship real automation into a real product, and leave with a portfolio of tests that protect paying customers. CX at OpusClip is built as a talent nursery: people who start here move into data, engineering and customer-facing technical roles. This role is designed as one of those on-ramps.

This role suits a student or early-career engineer who has already built and shipped something with AI assistance, likes finding the edge cases others miss, and cares about the people on the other side of the product as much as the code.

Key Responsibilities Turn customer tickets into automated tests Your core output is a UI end-to-end test battery grounded in real customer reports. You will mine support conversations and bug tickets for the workflows customers actually run and the moments where they fail, reproduce those failures, and write automated tests that catch them before the next customer does. Each test traces back to a ticket, so the battery grows in the direction of real user pain rather than hypothetical coverage. Success here is measured by the share of customer-reported regressions your tests would have caught, and by how much faster CX can confirm a reported issue is real.

Map user workflows into testable moments Before a test exists, someone has to break a workflow like "upload a video, get clips, export to TikTok" into its discrete steps, decision points and failure modes, and rank them by how many customers they touch. You will do this mapping with the CX team, who hold the ticket data, and document it so that Product and Engineering can reuse it. Over time this becomes a living map of how OpusClip is used, maintained from the customer side.

Work AI-native You will build with Claude Code or Codex as your primary tool: scoping a task, giving the model the right context, breaking the work into steps, reviewing and iterating on the output, and knowing when the first answer is wrong. You will also help the CX team adopt the same habits, sharing patterns and small tools that let non-engineers verify issues and query data on their own.

Bridge CX and Engineering You sit in CX but your work lands in Engineering's repositories and CI. You will open pull requests, respond to code review, follow branch and merge conventions, and report flaky or failing tests with clear reproduction steps. When a test exposes a product gap, you will write it up with the customer context, the business impact and a proposed priority, so that the people who own the fix can act on it without a second round of questions.

Qualifications and Requirements

Hands-on vibe coding experience: Must-have. You have built and shipped something real with AI assistance (a side project, internal tool or script) and can walk through how it was built: what you asked for, what the model got wrong, and how you fixed it.

Can read Python and JavaScript/TypeScript: Must-have. You can explain what a short snippet does and spot an obvious bug. You do not need to write either language from scratch.

Testing mindset: Must-have. Given a feature such as "upload a video, get clips", you list the happy path, edge cases and failure modes, then rank them by user impact rather than by how easy they are to test.

Customer empathy: Must-have. You want to understand what the user was trying to do, not just what broke. You read a ticket and see a person with a deadline, not a bug ID.

Clear communication and cross-functional collaboration: Must-have. Your write-ups are short, specific and readable by someone who was not in the room. You ask for review and take feedback without friction.

Grasp of business impact: Must-have. You can reason about ROI and opportunity cost: why fixing a bug that hits 2% of paying exports beats one that hits a rarely used free feature, and what it costs to test the wrong thing.

Breaks user workflows into discrete moments: Must-have. You can take "upload a video, get clips, post to TikTok" and name each step, each decision the user makes and each place it can go wrong.

Curiosity or background in video editing and media: Nice-to-have. You have made, edited or published video, or follow creators closely enough to know what a good clip looks like and why someone would pay for one.

Proficient with Claude Code or Codex: Nice-to-have. You give the tool the right context, break a task into steps and iterate on the output rather than accepting the first answer.

Basic web tooling and Git: Nice-to-have. You are comfortable in browser DevTools (Network and Console tabs, element selectors) and with branches, commits and pull requests, including taking review feedback.

What We Offer

You will own a real test battery that protects paying customers, with your name on every pull request. You will work with AI coding tools as a daily practice, not a demo, and build a track record that is unusual for an intern: automated tests traced to customer evidence, shipped into a production product.

You will have direct access to the CX, Product and Engineering teams at a fast-growing AI video company, and a manager whose explicit goal is to move strong CX people into technical roles across the company.

How to Apply Send a link to something you built with AI assistance (GitHub, a deployed app, a script, an internal tool) and two or three sentences on what it does and what the model got wrong along the way. A resume is helpful but the project matters more.

EEO

OpusClip is proud to be an equal opportunity employer. We do not discriminate in hiring or any employment decision based on race, color, religion, national origin, age, sex (including pregnancy, childbirth, or related medical conditions), marital status, ancestry, physical or mental disability, genetic information, veteran status, gender identity or expression, sexual orientation, or other applicable legally protected characteristics. OpusClip considers qualified applicants with criminal histories, consistent with applicable federal, state and local law. Opus Clip is also committed to providing reasonable accommodations for qualified individuals with disabilities and disabled veterans in our job application procedures.