What will happen if someone breaches the Beyond the Cloud Code of Conduct?
Each breach of the code of conduct as listed below is considered a strike. We believe in second chances. However, any individual who receives three “strikes” throughout their time will be removed from the program, and will not be able to participate in any future Beyond the Cloud project.
A breach of the Beyond the Cloud terms and conditions may result in immediate removal from the program.
Participants
Criteria for getting a strike | How to avoid getting a strike |
Ghosting/unresponsiveness
| Regularly communicate!
Be sure to stay in touch throughout the project to fully understand the project scope and ensure the work is on track. (Recommendation: respond to all communication within 72 hours.) |
Lack of commitment/incomplete work
| Once a participant team has been connected with an employer project, it is the responsibility of both the team and the employer to stay in frequent contact. Any changes or delays in the project should be clearly communicated in advance. |
Late submissions
| Beyond the Cloud projects should be completed within 4 weeks. Projects should be submitted on time, or the participant team and employer should reach out to the Beyond the Cloud team before the deadline to request an extension. |
Lying or falsely reporting work complete
| Keep track of your working hours and the list of deliverables which has been agreed by the participant team and the employer. You may also use the worklog on the Riipen platform. |
Reference Riipen as an employer on your CV or LinkedIn profile. .
| See this guide of how to reference your project on your CV and LinkedIn profile. FYI if you list Riipen as your employer for your Beyond the Cloud project and a recruitment office reaches out to Riipen to verify the validity of your CV, we will have to tell them you were not an employee of Riipen and this may nullify your application as invalid |
Any breach of the program terms and conditions | Read and understand the terms and conditions outlined for Beyond the Cloud.
A breach of these conditions may result in immediate removal from the program. Any misrepresentation of identity or eligibility will lead to suspension from the Riipen platform, and participants will not receive their Beyond the Cloud certificate. |
Employers
Criteria for getting a strike | How to avoid getting a strike |
Ghosting/unresponsiveness
| Be sure to stay in touch throughout the project to fully share the project scope and ensure the work is on track. (Recommendation: respond to all communication within 72 hours.) |
Lack of commitment
| Once a participant team has been connected with an employer project, it is the responsibility of both the team and the employer to stay in frequent contact. Any changes or delays in the project should be clearly communicated in advance. |
Not providing feedback on project submission | By providing feedback, you are helping the Beyond the Cloud participants build their Riipen profile and provide them with valuable insights to take forward in their tech career. |
Taking on too many projects
| Be mindful of the number of projects you match on the Riipen platform for Beyond the Cloud. Each project will be completed by a team of 3-5 participants. You are required to provide a minimum of 5 hours of mentorship to each participant - please ensure that you can manage all of the projects you are posting. |
Not providing the minimum 5 hours of mentorship to each participant. | Mentorship is an important component of the program and gives the participants the chance to grow and complete the tasks assigned. |
Any breach of the program terms and conditions | Read and understand the terms and conditions outlined for Beyond the Cloud.
A breach of these conditions may result in immediate removal from the program. Any misrepresentation of identity or eligibility will lead to suspension from the Riipen platform.
|