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?
  • What will happen?
  • What does the team have to do?
  • What does the team representative do?

Was this helpful?

  1. Tutorials

Interviews

One of the team members will be representing your team, and will answer a short question during the livestream!

PreviousPitch Content TipsNextHosting

Last updated 3 years ago

Was this helpful?

What?

We give short interviews to give people some insight on what went down during open summer of code, and what the atmosphere is like.

On the other hand, it gives them some time to process the amazing pitches they just saw!

What will happen?

We show 3 pitches, then we have an interview with a 3 team representatives for each of those teams!

What does the team have to do?

  1. Decide who is going to be the team representative that will answer that question?

  2. Test that person's mic and surroundings (we need good sound, and not too much background noise!)

  3. Check out the extra to reassure quality 👌

What does the team representative do?

Hurrah, you're selected as the team representative!

  • Look at the sheet to see what question you have to answer

    • Fill out your name

    • Prepare your question, make sure it's short & sweet ♥️

  • We show 3 pitches from 3 teams, and then we take a moment to hear the answers from the representatives of those 3 teams.

    • When your team's pitch is about to go up, go to the Waiting room in discord. The other 2 (or 3 in the last round) representatives will be waiting there too. Turn off your notifications.

    • When it's time to answer your question, you'll get introduced to the Pitch Arena. I'll say hi, bring you on the screen – excited to hear your answer 😊. Make sure you mute the YouTube stream so we don't get feedback!

  • Leave when the 3 team representatives have answered the question 😘.

Example:

  1. Pitches of Team 1 (Bridges), 2 (ArTIFFact Control) and 3 (Simplification of election procedures) are shown

  2. Representatives of Team 1, 2 and 3 go to the waiting room during those pitches.

  3. Representatives of Team 1, 2 and 3 are introduced to the pitch area, and answer the question in that sequence.

  4. They all leave at once when the answers have been given.

  5. Next team pitches: 4, 5 and 6. During those pitches their representatives go to the waiting toom.

Extra Pitch and Interview Tips
project description