Apply to join
We're humbled by your interest in Tech Collective.
We have a deliberately lengthy application process - but feedback will be provided to all unsuccessful applicants.
When we say that this application process is for your benefit as well as ours, that's not corporate platitude, it's genuine sentiment. Learn more: Why are there so many stages in the application process?
If you don't make our first cohort, you might well still make a future cohort. (Maybe you just weren't a good fit for the people in that first cohort!). Hopefully, it should also be fun - it'll involve some coding and working with other prospective peers.
|1. Build your own chatbot|
Purpose for us: This is to examine both how you apply your learning practically as well as gain insight into your motivations for joining Tech Collective, so that we can judge whether you could be a strong fit.
Purpose for you: You will learn to code something concrete, following an example of the pre-recorded tutorials you will receive on the programme. This will help you to understand whether you enjoy coding and whether you can learn effectively on our programme. Do you find it an enjoyable or productive use of your time?
(Maximum transparency: you should expect no more than 1-2 hours of video instruction a week. It is not intended to be the primary source of your learning.)Chatbot Submission
Tutorial: 1hr 40mins
|2. Peer prioritisation|
Description: You'll receive links to other people's chatbot applications. You will be asked to prioritise them in the order in which you'd like to work with them, and (optionally) provide feedback.
Purpose for us: This is for us to get a gauge of how you both perceive, and might be perceived by, your prospective peers.
Purpose for you: You get an insight into some of the people you might be studying alongside with.
|3. Pair programming exercise and reflection|
Description: You will complete a pair programming task with a prospective peer, using concepts from the video tutorial, then reflect on the experience together.
Purpose for us: This is primarily to examine how you work with, help and learn from a peer, as well as how you give/receive feedback. How you retain information will be a secondary consideration.
Purpose for you: Pair programming will be a mandatory part of the programme. Is it something that you can see value coming from? Are you comfortable with the feedback experience?
(Maximum transparency: from a single pair, it will be possible for neither, one or both of you to progress to the next stage. If you believe that you have been seriously impeded because of the person you happened to be paired with, you will have an opportunity to make your case.)
|4. FreeCodeCamp and bootcamp research|
Description: Go and speak to at least 1 from a coding bootcamp, and talk to them about their experiences. Go do research on the experiences of people self-studying materials like FreeCodeCamp. Submit a form detailing your conversations and reflections.
Purpose for us: The more informed you are about your options, the more confident we can be that those who continue with the process are making an informed - and therefore, more committed - decision.
Purpose for you: It is in your interest to make sure that you have seriously scrutinised other options. People who've been through these other paths of learning to code are also likely to have some advice that is useful to you.
|5. Write your user manual (*PROVISIONAL)|
Description: Write an explanation for your prospective peers of what they need to know about you to get the best out of you (see this blog).
Purpose for us: This lets us look at your self-awareness, introspection and openness.
Purpose for you: If you are a good fit for the programme, this user manual should actually be genuinely useful to your peers. Even if not, we believe that reflecting on your own behaviours is a productive and important use of time.
1-2 hours (very variable - depends on how you introspect)
|6. Speed-meet peers (*PROVISIONAL)|
Description: Group speed-meeting of peers from your prospective cohort.
Purpose for us: At this point, we think we've identified the right cohort - we're not selecting here, it's down to you.
Purpose for you: To confirm that you are happy to commit to joining Tech Collective with this cohort
|7. Trial month|
Description: The first month of the programme.
Purpose for us: We're really satisfied that you are likely to be a good fit - but the best way to confirm that is by actually checking in practice!
Purpose for you: You're optimistic about the programme - but the best way to confirm that it works for you is by actually checking in practice!
10 hours weekly