Jake wants to narrow down the recruiting pool down a little to get the right people because we don’t have the space to accommodate people in our projects
Caleb summarized the recruiting process last year: no distinction for roles and go to respective project leads for what to do. The result was lots of people were very interested but then the attention from people got diminished
A lot of the people went were a lot of freshman that didn’t have a lot of experience (majority were engineers)
The org didn’t know what to do with newbies and how to give them a good experience participating in the club works
Ruben: For API team, there were a lot of interests in the first few weeks but after several weeks later, people’s interests were diminished which is quite problematic because the retention problem can result in distraction from running the projects. One potential solution is to select a few peoples who are qualify and assigned them into a project.
Caleb: Didn’t know what to do with the newbies because they lack experience aside than letting them watch and observe. ACM also tried teaching newbies React for a month, it somewhat works but still resulted in dropoff after a few months
Jason: For me personally, I’m the type of person who wants to jump into work immediately and figure it out on my own but that’s not the case for many people. The questions boiled down to the fact that are we willing to bring in people and mentoring them for our projects
Kevin: We should probably accept people who have at least 1 year of experience.
Ruben: Partnering with ACM to let people graduates from their projects to work with Nebula Labs
David: Nebula Labs are founded under the principles of open sourced project. Pipelines are good but we should make it easier for people to join