1,212
edits
Changes
no edit summary
* Give a rough idea of the technical knowledge and experience of each applicant to the existing team
* Enable the applicants to develop technically as well as non-technically, even if they don't get selected
* Get completed within a short period of time and not interfere much with the technical work of the team members
* Ensure suitable knowledge transfer across the old and new team members
* Develop a strong bonding between the incoming recruits and the existing team members
There is no single correct recruitment process. A number of processes could meet the requirements listed above and you are free to design your own. Pratham's recruitment process is described in the next section for illustration purposes.
== Pratham's Recruitment Process ==
For most part, this distinction appears only on paper and the culture of the team is so good that the existence of this hierarchical structure is hardly felt though it is present. The hierarchical structure helps for official purposes and during the dissemination of responsibilities in emergency situations. It can remain dormant for the remaining times. <br /> <br />
This page would have made it clear that building a satellite is as much of a non-technical challenge as it is a technical one!<br \>----If you are done reading this page, you can go back to [[Starting a Student Satellite Project]].
