open summer of code
HomeWebsiteGitHub
  • Welcome to osoc!
  • Code of Conduct
  • The osoc Way of Work & Play
    • Working Together in a Remote Setting
  • Students
    • Applying as a student at osoc
      • Privacy Policy for Open Knowledge Belgium
    • Being a student at osoc
      • Practical: When, where, how long, food
      • Health, COVID, Insurance, Sick Days
      • Study material
    • The Student Job
    • Salary & Reimbursements
  • Coaches & Student coaches
    • Being a coach at oSoc
    • The Coaching Job
      • Soft Skills & Expectations
      • Tasks
      • How to Manage a Team: Techniques
      • Coaching Cases
      • Battle Prep
      • Student Coaches
      • Screening students
    • Projects
    • Partner Communication
    • Practical
  • partners
    • Being a partner at oSoc
      • Apply
      • Attend
    • The Partner's Job
    • Projects
  • Tools & Resources
    • Discord
      • Basics
      • Discord etiquette
      • Setting your nickname & description
      • Managing notifications
      • Offering and Receiving Help
      • Find Your Discord Username
    • NextCloud
    • The #osoc Emoji
    • Big Blue Button: Video Calls
    • Deployment
    • Maps & Cartography
  • Tutorials
    • Create Crests
    • Pitching
      • Pitch and Interview Tips
      • Pitch on Discord
      • Pitch Content Tips
    • Interviews
    • Hosting
    • Deliver Like a Pro
      • Publish a Github Page
    • Conduct (Remote) Tests and Interviews with Real People + Archetypes
  • Organisers
    • How to set up oSoc for your country
      • Preparation
      • Selection
      • Practical
        • Setting Up a Remote Edition
      • Informing people
    • On-site editions: 4 weeks of well-organised serendipity
      • Calendar Example Remote Edition (BE)
        • Week 1: Explore
          • Day 1: Welcome (to the Madness 😏)
          • Day 2: Meet the Client + Prepare for Hackathon
          • Day 3: Hackathon & Pitching
          • Day 4: Pitch & Battle Plan
        • Week 2: Build
          • Day 1: Build, test, document + Learn how to vlog
          • Day 2: Build, test, document
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 3: Build more
          • Day 1: Build, test, document + How to deploy
          • Day 2: Day off!
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 4: Deliver
          • Day 1: Ship ship ship
          • Day 2: Pitch pitch pitch
          • Day 3: Delivery Day
          • Day 4: Demo Day
      • Kick-off day 1 (or chaos day)
      • Hackathon day 2 — 4
      • Build — week 2
      • Build — week 3
      • Delivery week — week 4
      • Evaluation — follow-up
    • Taking over the world
    • Salary & Reimbursements
    • Managing teams
  • test
Powered by GitBook
On this page
  • What are the qualifications?
  • How do I apply?
  • What if I can't join this year?
  • What if I didn't make it through the applications?

Was this helpful?

  1. Students

Applying as a student at osoc

What are the qualifications?

If you meet the following requirements:

  • First of all, you’re a student eligible to work under a student contract for 16 full days (128 hours).

  • Secondly, you study or have experience in tech/marketing/bizdev (front- or back-end development, design, UX, graphic, communication, business modelling, ....)

  • Thirdly, you should be able to express yourself in English.

  • And last but not least, bring heaps of enthusiasm & motivation. We need that energy!

Do you meet these requirements? You could be an oSoc student!

How do I apply?

In order to apply you need to submit a letter of motivation, explaining why you would like to join the movement and what you will bring to the table to make oSoc great. Make sure to include your portfolio or some examples of your work as well. Based on your motivation, portfolio and your CV, a group of experienced oSoc volunteers will match your unique set of skills and experiences with partner’s desired student profiles.

During the month of May we go over all the applications and match the right students with the right projects. After that, we’ll let you know whether you've been selected.

What if I can't join this year?

That's too bad! You can always apply again next year as a student — or even as a coach. You're also welcome to join us during the demo day — which will take place on the last Thursday of osoc. And keep an eye on our Twitter account to see what we're up to!

What if I didn't make it through the applications?

Don't worry, you can always apply again next year as a student — or even as a coach. Just keep working on yourself and your resumé. We will review your application like it's the first time you applied. Don't forget to visit us during the demo day ;-).

PreviousWorking Together in a Remote SettingNextPrivacy Policy for Open Knowledge Belgium

Last updated 3 years ago

Was this helpful?