QA Engineering Intern

Company:

Gametime Hero Location:

Oakland, CA office /

Remote Type:

Internship Duration:

3 months

Compensation:

$1,000 stipend upon successful completion

Time Commitment:

10-15 hours/week About Gametime Hero Gametime Hero helps organizers run active communities — from recurring events and RSVPs to forms, waivers, payments, tournaments, coaching, and public community sites. We launched early, learned from real users, and have spent the last year building out the core platform. Many of our major features are now working and being used, but we are entering an important new phase: making the product more reliable, tested, polished, documented, and ready for broader adoption. We are looking for a Technical QA Intern to help test our product, find bugs, document issues clearly, and support our launch-readiness process. This is a good role for someone who is interested in QA, software engineering, product quality, or startup product development. You do not need to be a senior engineer, but you should be comfortable testing web apps, using browser developer tools, reading basic code, and learning how real software teams improve product quality. The Role As a Technical QA Intern, you will help make sure Gametime Hero features actually work for real users. You will test product flows across key areas like: – Events and RSVPs – Forms and waivers – Public sites – Communities – Tournaments – Coaching tools – Payments and organizer workflows Your work will help the team answer: – Does the feature work from start to finish? – Does it work on mobile and desktop? – Does it work for the right user roles? – What breaks when users make mistakes? – Are there console errors or broken network requests? – What bugs should block launch? – What needs to be fixed, polished, or documented? What You'll Do – Test new and existing product features – Run through user flows as organizers, members, coaches, and admins – Create clear bug reports with steps to reproduce, screenshots, videos, expected behavior, and actual behavior – Use browser developer tools to inspect console errors, network requests, and page behavior – Help identify whether issues are related to UI, data, permissions, or user flow – Test mobile, desktop, and different browsers – Help create QA checklists for major features – Verify bug fixes after developers complete them – Help track bug severity: P0, P1, P2, and P3 – Support launch-readiness reviews for major features – Document edge cases, confusing user flows, and product issues – Pair with developers to reproduce bugs and confirm fixes – Optionally help write or update simple automated tests if you have the skills Example Testing Areas You may test questions like: – Can an organizer create an event, publish it, and see RSVPs? – Can a member RSVP, cancel, or join a waitlist? – Can an organizer create a form and attach it to an event? – Do forms save responses correctly? – Can users access only what they are allowed to access? – Does the product work on mobile Safari? – Are there errors in the browser console? – Are failed network requests handled correctly? – Do public community pages and sites display correctly? – Do error messages make sense? – What happens if a user refreshes, clicks twice, or enters invalid information? What Success Looks Like By the end of the internship, you will have helped create: – QA checklists for major Gametime Hero features – Clear bug reports that developers can act on – Regression test lists for core user flows – Launch-readiness notes for features moving toward beta or public launch – Better visibility into bugs, console errors, edge cases, and broken flows – A stronger, more reliable product experience for real users Requirements – Strong attention to detail – Clear written communication – Comfortable testing websites or web applications – Basic understanding of HTML, CSS, and JavaScript (Angular/Firebase would be a BIG plus) – Comfortable using browser developer tools to inspect pages, view console errors, and understand basic network requests – Able to write clear bug reports with steps to reproduce, screenshots, expected behavior, and actual behavior – Familiarity with GitHub or willingness to learn – Reliable and able to complete weekly testing assignments – Interest in QA, software engineering, product quality, or startup operations Nice to Have – Experience with TypeScript, Angular, Firebase, or modern web development – Experience with testing tools like Cypress, Playwright, Jasmine, Jest, Vitest, or similar – Experience writing simple automated tests – Experience using Git/GitHub for issues, pull requests, or project boards – Basic understanding of authentication, user roles, forms, payments, or event workflows – Experience testing mobile web apps, especially on iOS Safari or Android Chrome – Interest in sports, events, community building, or coaching You Might Be a Good Fit If – You notice details other people miss – You like figuring out how things break – You can clearly explain what went wrong – You are comfortable looking at console errors or basic code – You are patient, organized, and curious – You care about users having a smooth experience – You want hands-on startup experience – You are interested in QA, software engineering, product management, or product operations You Are Probably Not a Fit If – You do not like repetitive testing – You struggle to document details clearly – You are not comfortable giving honest feedback – You only want to write code and do not want to test user flows – You are not interested in learning how software quality works – You need every task perfectly defined before starting What You'll Learn – How software teams test real products before launch – How to write strong bug reports – How to use browser developer tools during QA – How to think through user flows and edge cases – How QA fits into product, engineering, and launch readiness – How startups move from "working" to "reliable" – How to work with developers, product leads, and founders – How technical QA can lead into software engineering, QA engineering, product, or solutions engineering roles Internship Details –

Duration:

3 months –

Compensation:

$1,000 stipend upon successful completion –

Time Commitment:

10-15 hours per week –

Location:

Remote, with optional access to our Oakland, CA office –

Start Date:

Flexible How to Apply Send us: 1. Your resume or LinkedIn 2. A short note about why you are interested in technical QA or product quality 3. Any relevant experience testing software, building projects, reporting bugs, coding, or working on a technical team

Bonus:

include an example of a bug report you have written, a project you tested, or a simple coding project you have built.