← Exit 💻 Developer
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 14 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
List every programming language and framework you are proficient in. For each, rate your confidence from 1–10 and describe the most complex thing you have built with it — be specific about what the project did, the problems you solved, and the scale.
💬 Follow-up ✦ based on your answer Optional
You mentioned Unity — what Unity projects have you personally built? Describe or link them, and tell us which one taught you the most.
💬 Follow-up ✦ based on your answer Optional
You mentioned Unreal — what have you built in Unreal Engine? Do you work in Blueprints, C++, or both?
💬 Follow-up ✦ based on your answer Optional
You mentioned Godot — what have you made with it? GDScript or C#?
💬 Follow-up ✦ based on your answer Optional
JavaScript — front-end, back-end (Node), or both? What frameworks are you strongest in and what have you shipped with them?
💬 Follow-up ✦ based on your answer Optional
Python — what do you mainly use it for? Automation, back-end APIs, data, bots? Show us something you built.
Question 2
Describe your 2–3 most significant projects in detail: what it does, your exact role, the full tech stack, the hardest problem you encountered and how you solved it, and a link to the live project or repository. If projects are private, explain why and describe the architecture.
💬 Follow-up ✦ based on your answer Optional
No finished projects yet — what have you been learning or experimenting with lately, and what's stopping you from finishing something?
💬 Follow-up ✦ based on your answer Optional
Interesting — describe the nastiest bug you've ever debugged in one of those projects and how you finally tracked it down.
Question 3
Which area of development interests you most for REC.ZONE — frontend (UI/UX, design systems), backend (APIs, databases, auth), game development, DevOps/infrastructure, or security? Why? What specific things would you build or improve first?
💬 Follow-up ✦ based on your answer Optional
Good — and what part of development do you actually dislike or avoid? Be honest.
Question 4
Do you have experience with game development? If yes: which engine(s), what did you build, what was your role, and what is the current state of the project? If no, are you open to learning and contributing in this area?
Question 5
Describe your experience working in a team software project. What Git workflow did you use (branching strategy, PR reviews, CI/CD)? What project management tools have you worked with? How do you handle code review feedback?
Question 6
SCENARIO: You push a commit to production at 6 PM on a Friday. Within minutes, the site goes down for all users — 500+ active. The error traces to your commit. Walk us through your exact steps from the moment you get the alert to full resolution. What do you communicate and to whom?
💬 Follow-up ✦ based on your answer Optional
Solid — what if you pushed the fix and it made things worse? Walk us through your rollback plan.
Question 7
SCENARIO: While reviewing a pull request from a senior developer, you discover a SQL injection vulnerability that could expose all user data if exploited. The developer is more experienced than you. How do you handle this, both technically and interpersonally?
💬 Follow-up ✦ based on your answer Optional
Interesting — how would you have designed the system originally so that vulnerability could never have existed?
Question 8
Provide links to all of the following that apply: GitHub profile, portfolio site, deployed applications, open source contributions, or any other public technical work. Briefly describe the most impressive thing in each.
Question 9
How do you stay current with technology? What have you learned in the past 6 months — a new language, tool, framework, or concept — and how did you apply it?
💬 Follow-up ✦ based on your answer Optional
Give us something concrete — what's the most recent new thing you taught yourself, and how did you go about it?
Question 10
How many hours per week can you realistically commit? What is your timezone? Are you available for async collaboration and occasional real-time review sessions?
Question 11
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 12
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 13
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 14
This is a passion project — what motivates you to contribute your time and skill to something like REC.ZONE?
Question 15
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 16
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 17
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 18
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 19 Optional — skip if you want
How did you find REC.ZONE? Did someone refer you? If so, who?
Question 20 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