About the Role
NOTE: This position will be one of the first selected. You will have a say in the members accepted to the programming team, so you will need to be available to review applications with HR and the Project Manager.
As the Team Lead for the programming aspect of our projects, you will be responsible for taking the concepts, ideas, and plans discussed with the Project Manager and transforming them into manageable tasks and delegate them between yourself, and your team.
At initial project start, you can expect to have 2 to 3 team members under your supervision. You will be partially responsible for ensuring they have tasks, are making consistent progress, and have the tools they need to succeed.
Compensation: (IMPORTANT: PLEASE READ) Altered Form of Revenue Share
VALUE OF WORK:
Tasks will be assigned a dollar value. After completion of a task, that value will be added to the developer’s balance. The values will be determined after the task is completed, accounting for the following:
Time it took to complete the task
Collaboration requirements (adding some value to collaborator's balance)
Complexity of the task
Quality of final outcome
The value of the task should always be considered overly generous. The idea behind this is to create a functional, flexible alternative to revenue share. With that in mind, the idea of a hard-working, long-term team member having a functionally indefinite balance is perfectly reasonable.
HOW THE BALANCE WILL WORK:
The balances of the team members will work very similar to traditional revenue share. The main difference between this method and traditional rev share, is we can bring on members for short-term purposes as needed and allow them to still get paid out for their work without having to permanently bring down the split of long-term members. As balances are accrued, any revenue the game generates will be equally split among all current balance holders.
As an example, let’s say there were 5 total team members over the course of development, and team member #5 was only around for one week. The balances are as follows:
Team Member #1 - $50,000
Team Member #2 - $75,000
Team Member #3 - $40,000
Team Member #4 - $200,000
Team Member #5 - $1,000
The first month of revenue the game generates is $5,000. All team members will then be paid out $1,000 (5,000 / 5)
The next month of revenue is another $5,000. Since Team Member #5 has been paid out his full balance, the split will be applied equally to the remaining member’s balance, regardless of the difference in balance. (Team Members 1-4 will get $1,250)
DISCLAIMER:
This is AS NOTED PREVIOUSLY an alternative to traditional revenue share. It is still under the umbrella of revenue share. That being said, the balances SHALL ONLY and WILL ONLY be paid out based on revenue the project itself generates. Master Work Studios and its subsidiaries are under no obligation to pay out these balances should there not be enough revenue to do so. However, absolutely ZERO revenue will ever be withheld from paying out balances 100% equally. Any operating costs will come out of the Project Manager’s cut directly.
Requirements
These are definite requirements needed to fill this particular role.
Demonstratable knowledge of a majority of the following concepts (NOTE: It's okay to not have all of these skills, that is why we will have a team. But as a team leader you should be expected to have the knowledge to direct your team and understand the work they are doing):
Unreal Engine API knowledge. C++ (OR experience with a C# translation layer)
Gameplay Programming
AI Programming (NPC programming)
Unreal Engine Networking knowledge
Environmental Programming
UI Programming
Audio Programming
Graphics/FX Programming
Animation Graph Knowledge
Experience with GitHub or similar file sharing systems
SQL or similar database knowledge
Inventory and Crafting Systems
These are additional pluses:
Base building system experience
City builder/city manager game design experience
RPG game design experience
As a team leader, you may be expected to have wider availability to be able to answer the questions of your team. However, as this is a revenue share project, we are committed to making sure everyone including team managers do not feel obligated to provide more time than they would like. If you believe that you are overdedicating time, or have concerns with any aspect of the position, we encourage you to reach out to Arctic@MasterWorkStudios.org to clear anything up or find a solution.
Ability to, or confidence in your ability to, manage multiple team members, determine strengths and weaknesses, and delegate tasks that fit their strengths. You are welcome to do as much hands on work as you like, but it is important to ensure the team is being utilized efficiently.
Willing to sign a Non Disclosure Agreement, and 'Employment' contract. Both of which you will be given ample time to review and discuss with the Project Manager to answer questions or concerns.
These are preferred skills that will be of great use to the team.
Detailed knowledge of the use of GitHub or proposed similar team collaboration system. Inlcuding best practices of using branches, push and pull requests, and ensuring people can collaborate on the same systems with minimal conflicts.
Experience with voxel systems is a plus.
Experience with grid-based building systems is a plus.
About the Company
Master Work Studios LLC is a passion project of Shaun's/Arctic's. I've been doing game development as a hobby since 2016, and have an extreme love of video games and want to see them returned to the quality they once had. Instead of money grubbing and forcing out incomplete games, I want to see games made with love and passion behind them. I look forward to working with you to make this dream a reality.