As an Applications Manager at Senior Team, it will be your responsibility to review and answer all incoming applications for your specific department, either accepting or denying the applicants, based on criteria outlined here.
- Work Quality: The most important criteria when reviewing a specific applicant, this consists of the quality shown on their portfolio and on the specific trials you give them during the application process. For department-specific portfolio requirements, go to this page.
- Behaviour: Another important aspect when it comes to possible Senior Team freelancers, applicants must not be rude, impatient, childish, or immature in any way; otherwise, you can deny them for inappropriate conduct.
- Knowledge: All freelancers must show they are dedicated and that they took the time to go through our guidelines and rules, showing they have common sense and good knowledge of how our systems work and what their job will be once they get accepted (you must make sure they read our operations book and fully understood it)
- Activity: Since most commissions and projects have a fixed deadline, all the freelancers must be organized and able to finish within the timeframe agreed on with the client, otherwise a partial refund can be issued. Their activity can be determined by how fast they answer during the normal interview, in the trial, or simply by how many updates they provide to you during their trial and overall application process.
- Language: All our freelancers should be able to speak English to an acceptable level. We don't require absolute fluency, but they should be able to have a full conversation with the client and understand all their requirements properly, with no room for confusion. They should also maintain mature, professional language at all times when talking to a client. Applicants for the Writer position are the only ones who have a language requirement; they must be able to speak and write English to a 12th grade/upper 6th form level.
- Experience: Since Senior Team is one of the leading service teams on the Minecraft service scene, we are only accepting the best of the best. You must make sure the applicants have at least 6 months of background experience in the role they are applying for. This doesn't necessarily mean that they have to have worked at service teams for 6 months.
- Attitude: As a secondary criteria when reviewing an application, you should also observe the applicant’s communication skills, willingness to learn from their mistakes, and overall efforts to be a positive person who takes your constructive feedback to improve themselves and work on their weaknesses.
It is your duty as an Application Manager to evaluate each individual on relevant criteria, not based on personal, biased motives such as your experience with them, whether they are your friends or not, them already being a freelancer on a well-known team, etc. If you believe you may have biases towards an applicant you are reviewing, please contact the Head of Applications.
We strongly support fairness, thus all applicants must be treated the same, with no favoritism or exceptions.
Portfolio & MCM checks + Basic Trial Commission/Request
- First of all, you’ll review the Applicant’s Portfolio to check their work quality and experience. Use this page to evaluate applicant portfolios. Then you’ll move to the other pieces of information provided in the application.
- You will check their MCM to see if they have any negative reputation, open scam reports, etc. If they are clear, proceed further; otherwise, if there is any scam report or negative reputation, you should ask them first about it and give them a chance to explain. However, if they fail to provide a valid argument with proof, you can deny them and ban from opening further applications in the future.
- Lastly, after the applicant’s information has been checked and they’ve been cleared to go further, you will give them a small, basic trial commission they need to complete within 48 hours (e.g.: basic logo, plugin, bot, website page, document, etc.)
- In case the applicant fails to post anything within those 48 hours and they don’t say anything or don’t provide any updates, you can deny them.
- If they ask for a short time extension (1-2 days), you can accept their request, as long as they have a valid reason on why they need more time, such as exams, electricity outage, PC not working, etc.
- If the work quality is poor and far below our standards, you can deny them for a failed trial.
- If you are unsure about the work quality (work is decent, but not that impressive), you can give them one more small trial to double check if they should pass to the next stage.
- After they finish the request, you should ask them a few key questions about how they did the trial, in order to see if they really created it or just copied the work off the internet (e.g.: ask them how they added shadows, velocity, how they created a specific build, how they added a specific page to a website, how the bot runs a specific process, etc). You can (and should) also ask them to provide proof of ownership of the work.
If the applicant passes this initial stage, they will move on to the training phase. During this time, the applicant will be given various tests and quizzes, as well as interviews and simulated conversations with clients. This is not done by Application Managers, and is handled by Senior Team's Training Team. To accept an applicant into the training phase, run the
-trial @applicant command.
If an applicant is denied for any of the following reasons, you will not be paid for managing the application. The applicant must be denied for these reasons before they are given a trial commission.
- Previously banned from applying
- Left the server