← Exit 🧪 Beta Tester
Before you begin
Watch the introduction video
This explains what REC.ZONE is and what we expect from staff. You must watch it in full — open on YouTube if the player doesn't load.
Personal Info
What's your name? 👋
Your full name or the name you'd like us to call you.
Personal Info
What's your email address?
We'll send a 6-digit verification code here after you submit.
Personal Info
What's your phone number?
Used for identity verification only — never shared publicly.
Personal Info
How old are you?
This role requires you to be at least 16 years old.
Personal Info
What's your Discord username?
Personal Info
What's your Discord User ID?
Enable Developer Mode in Discord → right-click your name → Copy User ID. It's a long number.
Question 1
What platforms and devices do you own and regularly use for gaming? If you game on PC, list your full specs (CPU, GPU, RAM, OS, storage). Include any peripherals that could be relevant to testing (controllers, VR headsets, etc.)
💬 Follow-up ✦ based on your answer Optional
Interesting — which platform do bugs tend to show up on most for you, and why do you think that is?
Question 2
Describe your experience with QA testing, bug reporting, or structured playtesting. This includes professional work, indie game testing, beta programs, or systematic personal testing. Be specific about the games/products, your process, and the outcome.
💬 Follow-up ✦ based on your answer Optional
No formal QA experience — that's fine. Tell us about a time you found a bug, glitch, or exploit in ANY game. What was it, how did you find it, and what did you do about it?
💬 Follow-up ✦ based on your answer Optional
What is the single best bug you have ever found? Walk us through how you discovered it and how you reported it.
Question 3
Write a complete, professional bug report for the following scenario: "While playing the game, you discover that pressing Escape during the respawn countdown causes the character to respawn immediately without the timer, skipping the normal delay. This works every time and in all game modes." Write the report exactly as you would submit it.
💬 Follow-up ✦ based on your answer Optional
Good report — now, if a developer read that and said 'I can't reproduce it,' what extra info would you give them?
Question 4
What separates a good QA tester from someone who just plays a lot of games? What mindset, habits, and skills define professional-quality testing?
💬 Follow-up ✦ based on your answer Optional
Interesting — describe the last time you were just trying to enjoy a game but couldn't stop noticing bugs. What did you spot?
Question 5
SCENARIO: During a closed beta session you discover a critical exploit — players can duplicate their in-game currency by performing a specific sequence of actions. Other testers have not found it. The exploit works 100% of the time. What do you do? Who do you tell, how, and when?
💬 Follow-up ✦ based on your answer Optional
Solid — what if reporting that exploit meant your own high score or progress would get wiped? Do you still report it?
Question 6
Describe your personal testing methodology. How do you approach covering edge cases, reproducing issues, and stress-testing systems? Do you use any specific frameworks or checklists?
💬 Follow-up ✦ based on your answer Optional
Get specific for us — pick one feature of any game and describe exactly how you'd test it to try to break it.
💬 Follow-up ✦ based on your answer Optional
Interesting — what's a weird edge case or input most testers would never think to try, that you would?
Question 7
What genres of games do you have the deepest knowledge of and why? How does that expertise make you a better tester for a game like REC.ZONE?
💬 Follow-up ✦ based on your answer Optional
Nice — which game do you know so deeply you could spot even a tiny change or regression in it instantly?
Question 8
How many hours per week can you commit to scheduled testing sessions? Are you available for real-time testing calls with developers? What is your timezone?
💬 Follow-up ✦ based on your answer Optional
Testing often needs quick turnaround around a build — realistically, how fast could you jump on a new test build when we ping you?
Question 9
Why should we trust you with this role? What makes you accountable and reliable when nobody is watching?
💬 Follow-up ✦ based on your answer Optional
Interesting — now the flip side: what's a genuine reason we might hesitate to trust you, and how would you prove us wrong?
Question 10
Describe how you work in a team. What do you do when you strongly disagree with a teammate on how something should be done?
Question 11
How do you handle harsh or blunt criticism of your work? Tell us about a time you received tough feedback and what you did with it.
Question 12
This is a passion project — what motivates you to contribute your time and skill to something like REC.ZONE?
Question 13
What real-life commitments (school, work, family, other projects) could affect your availability, and how will you balance them?
💬 Follow-up ✦ based on your answer Optional
You said not much would get in the way — be realistic with us: what would actually pull you away, and how would you give us a heads-up?
Question 14
Are you currently part of any other teams, servers, studios, or projects? If so, which ones and in what capacity?
💬 Follow-up ✦ based on your answer Optional
Noted — how would you balance REC.ZONE with those other commitments if both needed you at once?
Question 15
What is your greatest strength for this role, and what is one genuine weakness you are actively working on?
💬 Follow-up ✦ based on your answer Optional
Good self-awareness — what are you actively doing right now to work on that weakness?
Question 16
Where do you see yourself within REC.ZONE six months from now if accepted?
💬 Follow-up ✦ based on your answer Optional
Interesting vision — what's the first concrete step you'd take in week one to head toward that?
Question 17 Optional — skip if you want
How did you find REC.ZONE? Did someone refer you? If so, who?
Question 18 Optional — skip if you want
Anything else you want us to know about you — personality, work style, or anything that sets you apart?
Almost done
One last video before you sign
Please watch this before signing your application — open on YouTube if the player doesn't load.
Final step — Contributor Agreement
Read the agreement, then sign your application
1. Ownership of Work Product, Intellectual Property, & Confidentiality (a) Sole and Exclusive Ownership: You hereby acknowledge and agree that any and all assets, materials, designs, software, source code, music, scripts, concepts, media, or other work product created, developed, or contributed by you (collectively, the "Work Product") for, on behalf of, or in connection with RECZONE shall be considered the sole and exclusive property of RECZONE. You irrevocably assign all rights, titles, and interests in and to such Work Product, including all intellectual property rights, copyrights, and trade secrets therein, to RECZONE immediately upon creation. (b) Project Assets and Data: Any data, files, software tools, documentation, or project materials provided to you by RECZONE or its team members remain the exclusive property of RECZONE. Your access to these materials is a limited, revocable license solely for the purpose of contributing to the project. (c) Strict Confidentiality: You agree to maintain the absolute confidentiality of all non-public information regarding RECZONE, including but not limited to unreleased game features, development plans, financial information, internal communications, and proprietary methods (collectively, "Confidential Information"). You shall not copy, distribute, disclose, leak, or share any Confidential Information, or any part of the Work Product, with any third party without explicit, written authorization from RECZONE leadership. This obligation survives your departure from the project. (d) Remediation and Enforcement: You acknowledge that unauthorized disclosure or misuse of Confidential Information or Work Product will cause irreparable harm to RECZONE. In the event of a breach of this agreement, RECZONE reserves the right to immediately terminate your access, remove your involvement from the project, pursue the removal of any leaked assets via legal takedown notices (such as DMCA), and seek all available legal and equitable remedies to protect the integrity of the project. 2. Team Membership Status, Disciplinary Action, & Termination (a) At-Will Participation: You understand and agree that your participation, role, and membership within the RECZONE development team is entirely voluntary and at-will. RECZONE leadership reserves the absolute right to terminate your membership, remove you from the team, alter your role, and revoke your access to any and all team platforms, servers, repositories, and tools at any time, with or without prior notice, for any reason or no reason at all. (b) Grounds for Immediate Termination: While RECZONE may terminate membership at-will, certain actions will result in immediate removal, asset revocation, and potential blocklisting from the community. These include, but are not limited to: * Policy Violations: Any breach of RECZONE guidelines, codes of conduct, or community standards. * Inactivity and Neglect: Prolonged, unexcused inactivity, failure to communicate with leadership, or a persistent failure to meet project deadlines and quality standards. * Conduct Detrimental to the Project: Engaging in toxic behavior, harassment, leaking internal discussions, or acting in a manner that harms the reputation, morale, or progress of RECZONE and its team members. * Discretion of Leadership: Any other reason determined by RECZONE Staff to be necessary for the health and security of the project, whether explicitly listed in this document or not. (c) Effect of Termination: Upon termination or removal from the RECZONE team for any reason, your license to use or access RECZONE assets, tools, and internal communication channels is immediately revoked. You must immediately cease all use of RECZONE-owned property. Termination of your team membership does not release you from your ongoing obligations regarding Intellectual Property and Confidentiality as outlined in Section 1. 3. Binding Agreement, Minor Status, & Execution (a) Acknowledgement and Acceptance: By signing below, electronically executing this document, or continuing to participate within the RECZONE team, platforms, or development environments, you affirm that you have read, fully understood, and expressly agree to be legally bound by all the terms, conditions, and obligations outlined in this Agreement. You acknowledge that this agreement constitutes a binding contract between yourself and RECZONE. (b) Minor Status and Parental/Guardian Consent: If you are a legal minor under the laws of your place of residence, you represent and warrant that you have reviewed this Agreement with your parent or legal guardian. For a minor's participation to be valid and authorized, a parent or legal guardian must sign below on your behalf, thereby consenting to all terms, assuming full responsibility for your compliance, and guaranteeing your obligations under this Agreement. (c) Severability: If any provision of this Agreement is found by a court or authority to be invalid, illegal, or unenforceable, the remaining provisions of this Agreement will remain in full force and effect.
Sign here — by typing your full legal name below you agree to the agreement above and certify that everything in this application is truthful. If you are a minor, a parent or legal guardian must type their name on your behalf. This signature is required.
press Enter ↵
Join Discord