The application period is now over.
Since the release of R^3, the concept of new content has, for the most part, been alien. Without the intervention of PrawnSkunk, things around here would still be completely stagnant. The development team is finally stepping up to the challenge of creating a new, user-oriented FFR. We have a plan which is ambitious enough to recruit a new team of proficient designers and developers. If you'd like to be a part of our team, please consider applying!
Before you apply, understand that:
• You must be present to attend three (ten minute) group meetings each week. Meetings will be held via Skype/Google Hangouts each Sunday, Wednesday, and Friday evenings. If you are unable to accommodate time for these group meetings, you should not apply.
• You will be expected to complete your assigned weekly tasks. Although we will try to uphold our ambitious targets, we also understand that you have real-world obligations that take precedence.
• You must be prepared to receive constructive feedback, and be willing to process it to make changes. We are all in this to create the best possible result.
Positions
Applications will close October 11th @ 11:59pm (server time). Please take your time to write an application that reflects your enthusiasm to help design the future of FFR. You will be contacted regardless of the outcome of your application. We will invite you for a group video call, in which we will talk about what we want to do and discuss the work that you’ve sent us. Getting invited to a video call does not guarantee that you will be offered the position, we want to meet you first.
We will not be looking for programmers until the full design for FFR has been completed and is ready to be implemented.
Since the release of R^3, the concept of new content has, for the most part, been alien. Without the intervention of PrawnSkunk, things around here would still be completely stagnant. The development team is finally stepping up to the challenge of creating a new, user-oriented FFR. We have a plan which is ambitious enough to recruit a new team of proficient designers and developers. If you'd like to be a part of our team, please consider applying!
Before you apply, understand that:
• You must be present to attend three (ten minute) group meetings each week. Meetings will be held via Skype/Google Hangouts each Sunday, Wednesday, and Friday evenings. If you are unable to accommodate time for these group meetings, you should not apply.
• You will be expected to complete your assigned weekly tasks. Although we will try to uphold our ambitious targets, we also understand that you have real-world obligations that take precedence.
• You must be prepared to receive constructive feedback, and be willing to process it to make changes. We are all in this to create the best possible result.
Positions
User Experience Designer
What am I responsible for?
• Wireframing the flow of any user interface that a user will use while exploring FFR.
• Designing what you believe a user should experience from the time they arrive on the homepage, to the time they begin engaging with other members of the community.
• Deciding what the first things a user should see, and how they might react to that. What does a new player not want to see?
What am I not responsible for?
• Creating art assets that might be considered to be used for the final versions of the UI.
User Interface Artist
What am I responsible for?
• Being, or becoming, aware of modern UI practices. You will have to locate the material yourself and learn from it if you are not up to speed yet.
• Reviewing the UX designs with the UX designer and creating mock-up art assets which more accurately represent what a user might be looking at while using FFR.
• Receiving feedback on your mockups and adjusting them as the grand vision of FFR changes.
• Taking final and fully tested UX designs and creating fully usable art assets for the elements.
What am I not responsible for?
• The sole creative design for the final look and feel of FFR. That will be a fully collaborative effort between all members of the development team, and with heavy influence from comments of the testers and community.
Feature Designer
What am I responsible for?
• Collaborating with the existing design team to document practical features and tools. Designing how existing features should be changed, and what new features should be created.
• Determining the viability of each feature you have designed to create prototypes, and interactive or static wireframes of these features (excel, visual examples, elaboration). A UX, UI, and Programmer must be able to look at your documentation and understand what they will be implementing.
What am I not responsible for?
• The programmatic implementation of these ideas.
• Determining if the feature is actually useful or fun. There is no way for us to know this until it has been prototyped and given to users to test.
Want to apply?
Send me a private message answering the following questions:
• How long have you been an active member of FFR? In this time, how have you made yourself involved within the community?
• What position are you applying for? What makes you a good fit for the position? Include examples of your relevant work. If you have no examples, then include what skills you possess that are relevant in us choosing you.
• Give us a new design idea or way to improve on an existing concept, relevant to the position you are applying for.
What am I responsible for?
• Wireframing the flow of any user interface that a user will use while exploring FFR.
• Designing what you believe a user should experience from the time they arrive on the homepage, to the time they begin engaging with other members of the community.
• Deciding what the first things a user should see, and how they might react to that. What does a new player not want to see?
What am I not responsible for?
• Creating art assets that might be considered to be used for the final versions of the UI.
User Interface Artist
What am I responsible for?
• Being, or becoming, aware of modern UI practices. You will have to locate the material yourself and learn from it if you are not up to speed yet.
• Reviewing the UX designs with the UX designer and creating mock-up art assets which more accurately represent what a user might be looking at while using FFR.
• Receiving feedback on your mockups and adjusting them as the grand vision of FFR changes.
• Taking final and fully tested UX designs and creating fully usable art assets for the elements.
What am I not responsible for?
• The sole creative design for the final look and feel of FFR. That will be a fully collaborative effort between all members of the development team, and with heavy influence from comments of the testers and community.
Feature Designer
What am I responsible for?
• Collaborating with the existing design team to document practical features and tools. Designing how existing features should be changed, and what new features should be created.
• Determining the viability of each feature you have designed to create prototypes, and interactive or static wireframes of these features (excel, visual examples, elaboration). A UX, UI, and Programmer must be able to look at your documentation and understand what they will be implementing.
What am I not responsible for?
• The programmatic implementation of these ideas.
• Determining if the feature is actually useful or fun. There is no way for us to know this until it has been prototyped and given to users to test.
Want to apply?
Send me a private message answering the following questions:
• How long have you been an active member of FFR? In this time, how have you made yourself involved within the community?
• What position are you applying for? What makes you a good fit for the position? Include examples of your relevant work. If you have no examples, then include what skills you possess that are relevant in us choosing you.
• Give us a new design idea or way to improve on an existing concept, relevant to the position you are applying for.
Applications will close October 11th @ 11:59pm (server time). Please take your time to write an application that reflects your enthusiasm to help design the future of FFR. You will be contacted regardless of the outcome of your application. We will invite you for a group video call, in which we will talk about what we want to do and discuss the work that you’ve sent us. Getting invited to a video call does not guarantee that you will be offered the position, we want to meet you first.
We will not be looking for programmers until the full design for FFR has been completed and is ready to be implemented.
Think it's the first time I've seen comments off for a front page announcement.
Comment