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 kind of project can I expect to work on?
  • Team assembly
  • Who do I report to?

Was this helpful?

  1. Students

The Student Job

What will you be doing as a student.

PreviousStudy materialNextSalary & Reimbursements

Last updated 3 years ago

Was this helpful?

What kind of project can I expect to work on?

All projects at osoc are being built open source and aim to create real-world impact. Over the last few years, students have got the opportunity to work on open innovation projects in different fields such as mobility, education, health, sports and biodiversity. Check out to see what kind of projects have been built by osoc students at the latest edition.

You can tell us what type of projects you're interested in. Your preference will be taken into account, but you might be working on a different challenge you had imagined. The organisation and coaches will pick your project for you, and you'll find out on the first day of osoc what you'll be doing. Exciting!

Team assembly

Your team will be assembled by the coaches according to the kind of people they need to build a successful project. We'll be matching devs, designers, marketers, researchers etc — so it'll be a very mixed team!

Who do I report to?

When it comes to the project, you'll always report to your coach(es), and if they are not available your student coaches. They'll go through the project scope with the team at the start osoc. Together with your coach, you'll define a backlog of things to do for the team. It'll be chopped up into smaller tasks so you can plan what you're doing in those 4 weeks. It's your job to keep your coach up to date of what you've been working on, what you're stuck with and what you're going to work on.

Coaches might give you the mandate to communicate to your client as well under their supervision — to keep your client happy and up to date .

last year's edition of Belgium