Difference between revisions of "Dev/Judging/Apply"

 
(14 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
<html>
 
<html>
  
−
<div id="HQ_info">
+
 
 
 
  
Line 19: Line 19:
 
<span class="on_page"></span><b>On this page</b>  
 
<span class="on_page"></span><b>On this page</b>  
 
you will find information on:
 
you will find information on:
−
<a href="#jamboree"> Judging at the Giant Jamboree </a>,  
+
<a href="#jamboree"> Judging at the Giant Jamboree</a>,  
−
<a href="#who"> Who should apply to be a judge? </a>,  
+
<a href="#who"> Who Should Apply to be a Judge?</a>,  
−
<a href="#why"> Why should you be an iGEM judge? </a>,
+
<a href="#why"> Why Should You be an iGEM Judge?</a>,
 
<a href="#process"> Application Process</a>, and
 
<a href="#process"> Application Process</a>, and
−
<a href="#benefits"> Judge Benefits</a>,
+
<a href="#benefits"> Judge Benefits</a>.
 +
<br><br>
 +
You can also go directly to the <a href="#application">Judge Application</a> located at the bottom of this page.
  
 
</p>
 
</p>
Line 33: Line 35:
 
<div class="details ">  
 
<div class="details ">  
 
<span class="icon announcement"></span>
 
<span class="icon announcement"></span>
−
<div class="title"> The iGEM 2019 Judging Application will open on April 5.  </div>  
+
<div class="title"> The iGEM 2019 Judging Application will open on April 19.  </div>  
 
</div>
 
</div>
 
<p>We will send out notifications about the opening of the judging applications through our <A href="https://igem.org/Newsletters">Newsletters</a>, so please sign up for our newsletters to stay informed! </p>
 
<p>We will send out notifications about the opening of the judging applications through our <A href="https://igem.org/Newsletters">Newsletters</a>, so please sign up for our newsletters to stay informed! </p>
Line 46: Line 48:
 
<h3>Judging at the Giant Jamboree</h3>
 
<h3>Judging at the Giant Jamboree</h3>
 
<p>Judging in iGEM is a lot of fun, but it does require <b>a strong commitment</b>. iGEM teams work incredibly hard on their projects over the summer, so we need judges who are also committed to work hard to evaluate them and who are willing to take part in the whole process of iGEM judging. If you can spend time learning about the judging process during the summer, evaluating team wikis the week before the Jamboree, and attending the Jamboree from October 31-November 4, 2019, we would love to have you on board!</p>
 
<p>Judging in iGEM is a lot of fun, but it does require <b>a strong commitment</b>. iGEM teams work incredibly hard on their projects over the summer, so we need judges who are also committed to work hard to evaluate them and who are willing to take part in the whole process of iGEM judging. If you can spend time learning about the judging process during the summer, evaluating team wikis the week before the Jamboree, and attending the Jamboree from October 31-November 4, 2019, we would love to have you on board!</p>
−
<p>We need experienced judges who understand iGEM, and new judges who are willing to learn about iGEM. We will provide educational resources to help judges learn how to evaluate teams, and we will help you get up to speed if you are selected.</p>
+
 
 +
<p>We need judges — both experienced and new — who understand iGEM, as well as some additional judges who are willing to learn about iGEM. We will provide educational resources to help judges learn how to evaluate teams, and we will help you get up to speed if you are selected.</p>
  
  
Line 54: Line 57:
  
 
<img src="https://static.igem.org/mediawiki/2019/f/f3/Judging_application_1.jpg">
 
<img src="https://static.igem.org/mediawiki/2019/f/f3/Judging_application_1.jpg">
−
<p class="image_caption">Judges at a team's poster during the 2019 Giant Jamboree</p>
+
<p class="image_caption">Judges at a team's poster during the 2018 Giant Jamboree</p>
 
</div>
 
</div>
  
Line 69: Line 72:
 
 
 
<div class="column two_thirds_size">
 
<div class="column two_thirds_size">
−
<h3>Who should apply to be a judge?</h3>
+
<h3>Who Should Apply to be a Judge? </h3>
 
<p>
 
<p>
 
We're looking for:</p>
 
We're looking for:</p>
 
<ul>
 
<ul>
 +
<li>iGEM alumni who want to stay involved, including professionals, graduate students, and post-docs</li>
 
<li>iGEM PIs, instructors, and advisors, both current and past</li>
 
<li>iGEM PIs, instructors, and advisors, both current and past</li>
−
<li>iGEM alumni who want to stay involved</li>
 
 
<li>People who have judged iGEM in the past</li>
 
<li>People who have judged iGEM in the past</li>
−
<li>Synthetic biology researchers who are new to iGEM, including graduate students and post-docs</li>
 
 
<li>Professionals in the synthetic biology, biotechnology, and engineering industries</li>
 
<li>Professionals in the synthetic biology, biotechnology, and engineering industries</li>
 +
<li>Synthetic biology researchers who are new to iGEM</li>
 
<li>People who have experience in complimentary areas, such as the humanities, art and design, and software</li>
 
<li>People who have experience in complimentary areas, such as the humanities, art and design, and software</li>
 
</ul>
 
</ul>
Line 97: Line 100:
 
<div class="column two_thirds_size">
 
<div class="column two_thirds_size">
  
−
<h3>Why should you be an iGEM judge?</h3>
+
<h3>Why Should You be an iGEM Judge?</h3>
 
<p>Judging at the annual iGEM Giant Jamboree is an incredibly fulfilling and worthwhile experience for all judges, whether you're returning as a veteran judge or are a new judge this year. Some of the benefits include:
 
<p>Judging at the annual iGEM Giant Jamboree is an incredibly fulfilling and worthwhile experience for all judges, whether you're returning as a veteran judge or are a new judge this year. Some of the benefits include:
 
<ul>
 
<ul>
−
<li><b>Networking:</b> You will meet fellow judges, students, and other professionals from around the world and different walks of life. Find your post-doc, network with industry leaders, and learn how others are doing synthetic biology worldwide!</li>
 
−
<li><b>New Technology:</b> You will learn about the latest cutting edge work being done in synthetic biology from student teams who are driven to excel and who test the boundaries of synthetic biology through their projects.</li>
 
−
<li><b>Collaborate:</b> Much like the iGEM teams, you'll have the chance to connect with people from around the globe, to expand your synthetic biology community, and to form new collaborations beyond the Giant Jamboree.</li>
 
 
<li><b>Contribute to the iGEM Community:</b> By volunteering to judge at the Giant Jamboree, you will contribute to what will be the most meaningful opportunity that these students experience in synthetic biology. Providing feedback to these dedicated students can be life changing for them as they continue through their academic career and beyond.</li>
 
<li><b>Contribute to the iGEM Community:</b> By volunteering to judge at the Giant Jamboree, you will contribute to what will be the most meaningful opportunity that these students experience in synthetic biology. Providing feedback to these dedicated students can be life changing for them as they continue through their academic career and beyond.</li>
 +
<li><b>Networking:</b> Much like the iGEM teams, you'll have the chance to connect with people from around the globe, to expand your synthetic biology community, and to form new collaborations beyond the Giant Jamboree. You will meet fellow judges, students, and other professionals from around the world and different walks of life. </li>
 +
<li><b>Learn About New Technology:</b> You will learn about the latest cutting edge work being done in synthetic biology from student teams who are driven to excel and who test the boundaries of synthetic biology through their projects.</li>
 +
 
</ul>
 
</ul>
  
Line 116: Line 119:
 
<h3>Application Process</h3>
 
<h3>Application Process</h3>
 
<p>
 
<p>
−
This year we are accepting applications on a rolling basis so there was no deadline to apply earlier in the year. We will be evaluating applications at the end of each month starting in April and will contact applicants approximately two weeks after the evaluation period. This means status notifications (1. invitation to judge, 2. invitation to serve as a reserve judge, 3. invitation to re-apply, or 4. decline for 2019 with an invitation to apply next year) will be sent in the middle of each month, beginning in May, until our quota is full (expected by August). We encourage you to apply early to increase your chances of being selected!
+
This year we are accepting applications on a rolling basis. We will be evaluating applications at the end of each month starting in May and will contact applicants approximately two weeks after the evaluation period. Status notifications (1. invitation to judge, 2. invitation to serve as a reserve judge, 3. invitation to re-apply, or 4. decline for 2019 with an invitation to apply next year) will be sent in the middle of each month, beginning in June, until our quota is full (expected by August). We encourage you to apply early to increase your chances of being selected!  
 
<br><br>
 
<br><br>
−
Applicants who are invited to join the judging panel will be asked to confirm their acceptance, so you can apply to be a judge prior to knowing if you can fully commit to attending the Giant Jamboree. We can also provide an official invitation letter if you require that to secure funding and/or permission from your institute to participate as a judge.
+
You can apply to be a judge before knowing if you can fully commit to attending the Giant Jamboree. Applicants who are invited to join the judging panel will be asked to confirm their acceptance. We can also provide an official invitation letter if you require that to secure funding and/or permission from your institute to participate as a judge.  
 
<br><br>
 
<br><br>
 
Once we have reached our quota of judges, we will close the application and add a notice to this page.
 
Once we have reached our quota of judges, we will close the application and add a notice to this page.
 
</p>
 
</p>
 +
 +
 +
<div class="column full_size">
 +
<div class="highlight post_item">
 +
<div class="details">
 +
<span class="icon note"></span>
 +
<div class="title">Giant Jamboree Attendance</div>
 +
</div>
 +
 +
<p>If you are selected as a judge, you <b>MUST</b> attend the iGEM 2019 <a href="https://2019.igem.org/Giant_Jamboree">Giant Jamboree</a> in Boston (October 31-November 4) <b>in person.</b> We are unable to support remote participation for judges due to the nature of the interactions you will have with the teams throughout the event.
 +
<br><br>
 +
If you can only attend a portion of the Jamboree, this may make judging your assigned teams a challenge. We will work with you to try to accommodate your schedule constraints as best as possible, but we may rescind your invitation to judge in favor of another applicant who can attend the entire event. This will be evaluated on a case by case basis.
 +
</div>
 +
</div>
 +
  
 
<div class="clear extra_space"></div>
 
<div class="clear extra_space"></div>
Line 131: Line 149:
 
<h3>Judge Benefits</h3>
 
<h3>Judge Benefits</h3>
 
<p>
 
<p>
−
Instructor judges (team PIs, instructors, and advisors) will receive a 50% discount on their Jamboree attendance fee! Judges who are not affiliated with a team will receive free Jamboree attendance!
+
Instructor judges (current team PIs, instructors, and advisors) will receive a 50% discount on their Jamboree attendance fee.
 +
<br><br>
 +
Judges who are not affiliated with a team will receive free Jamboree attendance.
 
<br><br>
 
<br><br>
 
We are also excited to offer free childcare for all of our judges throughout the Giant Jamboree!
 
We are also excited to offer free childcare for all of our judges throughout the Giant Jamboree!
Line 138: Line 158:
  
 
<div class="clear extra_space"></div>
 
<div class="clear extra_space"></div>
−
<div class="line_divider"></div>
 
−
<div class="clear extra_space" id="attend"></div>
 
−
 
−
<div class="column full_size">
 
−
<div class="highlight post_item">
 
−
<div class="details">
 
−
<span class="icon note"></span>
 
−
<div class="title">Giant Jamboree Attendance</div>
 
−
</div>
 
−
 
−
<p>If you are selected as a judge, you <b>MUST</b> attend the iGEM 2019 <a href="https://2019.igem.org/Giant_Jamboree">Giant Jamboree</a> in Boston (October 31-November 4) in person. We are unable to support remote participation for judges due to the nature of the interactions you will have with the teams throughout the event.
 
−
<br><br>
 
−
If you can only attend a portion of the Jamboree, this may make judging your assigned teams a challenge. We will work with you to try to accommodate your schedule constraints as best as possible, but we may rescind your invitation to judge in favor of another applicant who can attend the entire event. This will be evaluated on a case by case basis.
 
−
</div>
 
−
</div>
 
−
 
−
<div class="clear extra_space"></div>
 
−
 
  
 
<div class="highlight post_item gray">
 
<div class="highlight post_item gray">
Line 170: Line 172:
 
<div class="clear extra_space"></div>
 
<div class="clear extra_space"></div>
  
−
<div class="column full_size">
+
<div class="column full_size" id="application">
−
 
+
  
 +
<br><br>
  
 
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Line 290: Line 292:
 
</div>
 
</div>
 
<p>
 
<p>
−
To be eligible to become an iGEM judge, you must be at least 23 on the 31st of March 2019. We also expect judges to have completed their undergraduate degree before the Jamboree takes place. Any applicants who do no meet these criteria will be evaluated on a case by case basis.  
+
To be eligible to become an iGEM judge, you must be at least 23 years old as of March 31, 2019. We also expect judges to have completed their undergraduate degree before the Jamboree takes place.  
 
</p>
 
</p>
 
</div>
 
</div>
Line 439: Line 441:
  
  
−
 
+
<p class="question">2. Are you available to attend the <b>entire</b> <a href="https
−
<p class="question">2. Dietary restrictions. <span class="additional_question_text"> If you have other dietary restrictions, please <a href="https://igem.org/Contact">contact iGEM HQ</a></span> </p>
+
://2019.igem.org/Giant_Jamboree">Giant Jamboree</a> from October 31 - November 4, 2019, in Boston?</p>
−
<ul>
+
−
<li><label><input type="radio" data-validation="optional" name="Vegetarian" id="vegetarian" data-form-field="vegetarian"> Vegetarian</label></li>
+
−
<li><label><input type="radio" data-validation="optional" name="Food allergy" id="allergy" data-form-field="allergy"> Food Allergy or Other Restriction</label> <input type="text" size="60" data-validation="#allergy" name="Food allergy" data-form-field="allergy-describe"  placeholder="Please describe"></li>
+
−
<li><label><input type="radio" data-validation="optional" name="None" id="none" data-form-field="none"> None</label></li>
+
−
 
+
−
 
+
−
</ul>
+
−
 
+
−
 
+
−
 
+
−
 
+
−
<p class="question">3. Are you available to attend the <b>entire</b> <a href="https
+
−
://2019.igem.org/Giant_Jamboree">Giant Jamboree</a> (October 31 - November 4 2019, in Boston)?</p>
+
 
<ul>
 
<ul>
−
<li><label><input type="radio" name="Jamboree Attendance" data-form-field="jamboree" value="yes"> Yes</label></li>
+
<li><label><input type="radio" name="Jamboree Attendance" data-form-field="jamboree" value="yes">Yes</label></li>
 
<li><label><input type="radio" name="Jamboree Attendance" data-form-field="jamboree" value="no"> No</label> </li>
 
<li><label><input type="radio" name="Jamboree Attendance" data-form-field="jamboree" value="no"> No</label> </li>
 
</ul>
 
</ul>
  
−
<p class="question">3.1 If not, please indicate which days/times you are available to attend.</p>
+
<p class="question">2.1 If not, please indicate which days/times you are available to attend.</p>
  
 
<div class="column half_size">
 
<div class="column half_size">
Line 468: Line 457:
 
<th>Thursday <br> October 31</th>
 
<th>Thursday <br> October 31</th>
 
<td></td>
 
<td></td>
−
<td><label><input type="radio" name="Availability Thurs Oct 31, Evening" data-form-field="available_wed_eve" value="yes"> Yes</label><br /><br>
+
<td><label><input type="radio" name="Availability Thurs Oct 31, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label><br /><br>
−
<label><input type="radio" name="Availability Thurs Oct 31, Evening" data-form-field="available_wed_eve" value="no"> No</label>
+
<label><input type="radio" name="Availability Thurs Oct 31, Evening" data-form-field="available_thu_eve" value="no"> No</label>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 476: Line 465:
 
<tr>
 
<tr>
 
<th>Friday <br> November 1</th>
 
<th>Friday <br> November 1</th>
−
<td><label><input type="radio" name="Availability Fri Nov 1, Morning" data-form-field="available_thu_morn" value="yes"> Yes</label><br /><br>
+
<td><label><input type="radio" name="Availability Fri Nov 1, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br /><br>
−
<label><input type="radio" name="Availability Fri Nov 1, Morning" data-form-field="available_thu_morn" value="no"> No</label>
+
<label><input type="radio" name="Availability Fri Nov 1, Morning" data-form-field="available_fri_morn" value="no"> No</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Availability Fri Nov 1, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label><br /><br>
+
<td><label><input type="radio" name="Availability Fri Nov 1, Evening" data-form-field="available_fri_eve" value="yes"> Yes</label><br /><br>
−
<label><input type="radio" name="Availability Fri Nov 1, Evening" data-form-field="available_thu_eve" value="no"> No</label>
+
<label><input type="radio" name="Availability Fri Nov 1, Evening" data-form-field="available_fri_eve" value="no"> No</label>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 486: Line 475:
 
<tr>
 
<tr>
 
<th>Saturday <br> November 2</th>
 
<th>Saturday <br> November 2</th>
−
<td><label><input type="radio" name="Availability Sat Nov 2, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br /><br>
+
<td><label><input type="radio" name="Availability Sat Nov 2, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br /><br>
−
<label><input type="radio" name="Availability Sat Nov 2, Morning" data-form-field="available_fri_morn" value="no"> No</label>
+
<label><input type="radio" name="Availability Sat Nov 2, Morning" data-form-field="available_sat_morn" value="no"> No</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Availability Sat Nov 2, Evening" data-form-field="available_fri_eve" value="yes"> Yes</label><br /><br>
+
<td><label><input type="radio" name="Availability Sat Nov 2, Evening" data-form-field="available_sat_eve" value="yes"> Yes</label><br /><br>
−
<label><input type="radio" name="Availability Sat Nov 2, Evening" data-form-field="available_fri_eve" value="no"> No</label>
+
<label><input type="radio" name="Availability Sat Nov 2, Evening" data-form-field="available_sat_eve" value="no"> No</label>
 
</td>
 
</td>
  
Line 501: Line 490:
 
<th>Sunday <br> November 3</th>
 
<th>Sunday <br> November 3</th>
  
−
<td><label><input type="radio" name="Availability Sun Nov 3, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br /><br>
+
<td><label><input type="radio" name="Availability Sun Nov 3, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br /><br>
−
<label><input type="radio" name="Availability Sun Nov 3, Morning" data-form-field="available_sat_morn" value="no"> No</label>
+
<label><input type="radio" name="Availability Sun Nov 3, Morning" data-form-field="available_sun_morn" value="no"> No</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Availability Sun Nov 3, Evening" data-form-field="available_sat_eve" value="yes"> Yes</label><br /><br>
+
<td><label><input type="radio" name="Availability Sun Nov 3, Evening" data-form-field="available_sun_eve" value="yes"> Yes</label><br /><br>
−
<label><input type="radio" name="Availability Sun Nov 3, Evening" data-form-field="available_sat_eve" value="no"> No</label>
+
<label><input type="radio" name="Availability Sun Nov 3, Evening" data-form-field="available_sun_eve" value="no"> No</label>
 
</td>
 
</td>
  
Line 512: Line 501:
 
<tr>
 
<tr>
 
<th>Monday <br> November 4</th>
 
<th>Monday <br> November 4</th>
−
<td><label><input type="radio" name="Availability Mon Nov 4, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br /><br>
+
<td><label><input type="radio" name="Availability Mon Nov 4, Morning" data-form-field="available_mon_morn" value="yes"> Yes</label><br /><br>
−
<label><input type="radio" name="Availability Mon Nov 4, Morning" data-form-field="available_sun_morn" value="no"> No</label>
+
<label><input type="radio" name="Availability Mon Nov 4, Morning" data-form-field="available_mon_morn" value="no"> No</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Availability Mon Nov 4, Evening" data-form-field="available_sun_eve" value="yes"> Yes</label><br /><br>
+
<td><label><input type="radio" name="Availability Mon Nov 4, Evening" data-form-field="available_mon_eve" value="yes"> Yes</label><br /><br>
−
<label><input type="radio" name="Availability Mon Nov 4, Evening" data-form-field="available_sun_eve" value="no"> No</label>
+
<label><input type="radio" name="Availability Mon Nov 4, Evening" data-form-field="available_mon_eve" value="no"> No</label>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 544: Line 533:
 
<h2> 3. Conflicts of Interest </h2>
 
<h2> 3. Conflicts of Interest </h2>
  
−
<p>There are many possible reasons why you might be unable to judge some teams impartially. For example if you are a PI or instructor for the team, if the team comes from a school that you attended, or a school where you work or if you mentored or advised the team informally <br>
+
<p>There are many possible reasons why you might be unable to judge some teams impartially. For example if you are a PI or instructor for the team, if the team comes from a school that you attended, or a school where you work or if you mentored or advised the team informally.
 +
<br><br>
 
These situations could lead to a conflict of interest and iGEM takes conflicts of interests very seriously. Judges are not permitted to evaluate teams for which they have a conflict of interest. If you are a PI or instructor, your first responsibility is to your team, and we will schedule your judging assignment so that you are able to attend your team's presentation.</p>
 
These situations could lead to a conflict of interest and iGEM takes conflicts of interests very seriously. Judges are not permitted to evaluate teams for which they have a conflict of interest. If you are a PI or instructor, your first responsibility is to your team, and we will schedule your judging assignment so that you are able to attend your team's presentation.</p>
  
−
<br><br>
 
  
 
<p>To select multiple teams, use <i><b> Ctrl-click or Cmd-click</i></b>. Don't recognize a team name? Look it up in the <a target="_blank" href="https://igem.org/Team_List">Team List</a>.</p>
 
<p>To select multiple teams, use <i><b> Ctrl-click or Cmd-click</i></b>. Don't recognize a team name? Look it up in the <a target="_blank" href="https://igem.org/Team_List">Team List</a>.</p>
Line 597: Line 586:
 
<h2>4. Motivation</h2>
 
<h2>4. Motivation</h2>
 
<p>Please answer these questions in detail.</p>
 
<p>Please answer these questions in detail.</p>
−
<p>Did you apply to judge last year? <a id="last_years_application_link" target="_blank">View your answers from last year.</a></p>
+
<p>Did you apply to judge last year? <a id="last_years_application_link" target="_blank">View your answers from last year.</a> Please note we have changed some of the questions for 2019.</p>
  
  
Line 604: Line 593:
 
<textarea rows="5" name="Why do you want to be a judge" id="why_want_to_judge" data-form-field="why_want_to_judge" maxlength="2000"></textarea>
 
<textarea rows="5" name="Why do you want to be a judge" id="why_want_to_judge" data-form-field="why_want_to_judge" maxlength="2000"></textarea>
  
−
<p class="question">2. What professional experience do you have that's relevant to iGEM (e.g., synthetic biology, hardware, software, human practices)?</p>
+
<p class="question">2. What professional experience do you have that you believe is relevant to iGEM (e.g., synthetic biology, hardware, software, human practices)?</p>
 
<textarea rows="5" name="What professional experience do you have" id="professional_experience" data-form-field="professional_experience" maxlength="2000"></textarea>
 
<textarea rows="5" name="What professional experience do you have" id="professional_experience" data-form-field="professional_experience" maxlength="2000"></textarea>
  
−
<p class="question">3. Have you judged student competitions other than iGEM before? If so, which ones? (e.g. FIRST, BIOMOD, Science Olympiad)</p>
+
<p class="question">3. How important is scientific and/or engineering success to overall team success?</p>
−
<textarea rows="5" name="Have you judged other competitions" id="other_competitions" data-form-field="other_competitions" maxlength="2000"></textarea>
+
<textarea rows="5" name="How important is scientific and/or engineering" id="scientific_engineering" data-form-field="success" maxlength="2000"></textarea>
  
−
<p class="question">4. What features of an iGEM team and their project make them worthy of recognition?</p>
+
<p class="question">4. What are the synthetic biology principles that iGEM participants should learn during their project?</p>
−
<p>(New judges may want to familiarize themselves with the <a href="https://static.igem.org/mediawiki/2018/2/2f/2018_judging_handbook.pdf" target="_blank">2018 Judging Handbook</a>. The 2019 Judging Handbook will be available later this year.)</p>
+
<textarea rows="5" name="What are the synthetic biology principles" id="synbio_principles" data-form-field="principles"></textarea maxlength="2000"></fieldset>
−
<textarea rows="6" name="What makes an iGEM team worthy of recognition" id="worthy" data-form-field="worthy"></textarea maxlength="2500">
+
−
</fieldset>
+
  
  
Line 631: Line 618:
 
<p>iGEM teams compete in several "tracks", based on the topics of their projects. Please see <a href="https://2019.igem.org/Competition/Tracks" target="_blank">the Track page</a> for more information on each track.</p>
 
<p>iGEM teams compete in several "tracks", based on the topics of their projects. Please see <a href="https://2019.igem.org/Competition/Tracks" target="_blank">the Track page</a> for more information on each track.</p>
  
−
<p>When we assign judges to teams, we will try to assign you your first preferences wherever possible. However, we can't anticipate how many teams will be in each track, so it may not always be possible to assign you your first choice. Therefore, you can indicate how you feel about each track. The more first choices you select, the more likely it is that you will be assigned teams in those tracks. If you are <b>unable</b> to evaluate teams in some track areas (software or measurement, for example), please put "Avoid" for those tracks.</p>
+
<p>When we assign judges to teams, we will try to assign you your first preferences wherever possible. However, we can't anticipate how many teams will be in each track, so it may not always be possible to assign you your first choice. Therefore, you can indicate how you feel about each track. The more first choices you select, the more likely it is that you will be assigned teams in those tracks. If you are <b>unable</b> to evaluate teams in some track areas (software, for example), please put "Avoid" for those tracks.</p>
  
 
<p class="question">Please indicate how highly you prefer each track. You may select multiple first, second, and third preferences.</p>
 
<p class="question">Please indicate how highly you prefer each track. You may select multiple first, second, and third preferences.</p>
Line 644: Line 631:
 
<th>Avoid</th>
 
<th>Avoid</th>
 
</tr>
 
</tr>
−
<!--
+
 
−
<tr>
+
−
<th>Art and Design</th>
+
−
<td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="first"></td>
+
−
<td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="second"></td>
+
−
<td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="third"></td>
+
−
<td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="neutral"></td>
+
−
<td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="avoid"></td>
+
−
</tr>
+
−
-->
+
 
<tr>
 
<tr>
 
<th>Diagnostics</th>
 
<th>Diagnostics</th>
Line 694: Line 672:
 
<td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="avoid"></td>
 
<td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="avoid"></td>
 
</tr>
 
</tr>
−
 
−
<!--
 
−
<tr>
 
−
<th>Hardware</th>
 
−
<td><input type="radio" name="Track Preference: Hardware" data-form-field="pref_hardware" value="first"></td>
 
−
<td><input type="radio" name="Track Preference: Hardware" data-form-field="pref_hardware" value="second"></td>
 
−
<td><input type="radio" name="Track Preference: Hardware" data-form-field="pref_hardware" value="third"></td>
 
−
<td><input type="radio" name="Track Preference: Hardware" data-form-field="pref_hardware" value="neutral"></td>
 
−
<td><input type="radio" name="Track Preference: Hardware" data-form-field="pref_hardware" value="avoid"></td>
 
−
</tr>
 
−
-->
 
−
 
 
<tr>
 
<tr>
 
<th>High School</th>
 
<th>High School</th>
Line 730: Line 696:
 
<td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="avoid"></td>
 
<td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="avoid"></td>
 
</tr>
 
</tr>
−
 
+
        <tr>
−
<!--
+
−
<tr>
+
−
<th>Measurement</th>
+
−
<td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="first"></td>
+
−
<td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="second"></td>
+
−
<td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="third"></td>
+
−
<td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="neutral"></td>
+
−
<td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="avoid"></td>
+
−
</tr>
+
−
-->
+
−
 
+
−
<tr>
+
 
<th>New Application</th>
 
<th>New Application</th>
 
<td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="first"></td>
 
<td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="first"></td>
Line 752: Line 706:
 
<tr>
 
<tr>
 
<th>Open</th>
 
<th>Open</th>
−
<td><input type="radio" name="Track Preference: Software" data-form-field="pref_open" value="first"></td>
+
<td><input type="radio" name="Track Preference: Open" data-form-field="pref_open" value="first"></td>
−
<td><input type="radio" name="Track Preference: Software" data-form-field="pref_open" value="second"></td>
+
<td><input type="radio" name="Track Preference: Open" data-form-field="pref_open" value="second"></td>
−
<td><input type="radio" name="Track Preference: Software" data-form-field="pref_open" value="third"></td>
+
<td><input type="radio" name="Track Preference: Open" data-form-field="pref_open" value="third"></td>
−
<td><input type="radio" name="Track Preference: Software" data-form-field="pref_open" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Open" data-form-field="pref_open" value="neutral"></td>
−
<td><input type="radio" name="Track Preference: Software" data-form-field="pref_open" value="avoid"></td>
+
<td><input type="radio" name="Track Preference: Open" data-form-field="pref_open" value="avoid"></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 899: Line 853:
  
 
</div>
 
</div>
−
</div>
+
 
 
</div>
 
</div>
 
</html>
 
</html>
 
{{Footer2019}}
 
{{Footer2019}}

Latest revision as of 13:10, 19 April 2019

Loading...

iGEM 2019 Judging Applications

On this page you will find information on: Judging at the Giant Jamboree, Who Should Apply to be a Judge?, Why Should You be an iGEM Judge?, Application Process, and Judge Benefits.

You can also go directly to the Judge Application located at the bottom of this page.



The iGEM 2019 Judging Application will open on April 19.

We will send out notifications about the opening of the judging applications through our Newsletters, so please sign up for our newsletters to stay informed!

Judging at the Giant Jamboree

Judging in iGEM is a lot of fun, but it does require a strong commitment. iGEM teams work incredibly hard on their projects over the summer, so we need judges who are also committed to work hard to evaluate them and who are willing to take part in the whole process of iGEM judging. If you can spend time learning about the judging process during the summer, evaluating team wikis the week before the Jamboree, and attending the Jamboree from October 31-November 4, 2019, we would love to have you on board!

We need judges — both experienced and new — who understand iGEM, as well as some additional judges who are willing to learn about iGEM. We will provide educational resources to help judges learn how to evaluate teams, and we will help you get up to speed if you are selected.

Judges at a team's poster during the 2018 Giant Jamboree

Who Should Apply to be a Judge?

We're looking for:

  • iGEM alumni who want to stay involved, including professionals, graduate students, and post-docs
  • iGEM PIs, instructors, and advisors, both current and past
  • People who have judged iGEM in the past
  • Professionals in the synthetic biology, biotechnology, and engineering industries
  • Synthetic biology researchers who are new to iGEM
  • People who have experience in complimentary areas, such as the humanities, art and design, and software

If you have colleagues who you think should apply, please feel free to direct them to this form.

If you are a student on a 2019 iGEM team, you can't apply to be a judge this year. But you can apply when you graduate and become an iGEM alum!

Why Should You be an iGEM Judge?

Judging at the annual iGEM Giant Jamboree is an incredibly fulfilling and worthwhile experience for all judges, whether you're returning as a veteran judge or are a new judge this year. Some of the benefits include:

  • Contribute to the iGEM Community: By volunteering to judge at the Giant Jamboree, you will contribute to what will be the most meaningful opportunity that these students experience in synthetic biology. Providing feedback to these dedicated students can be life changing for them as they continue through their academic career and beyond.
  • Networking: Much like the iGEM teams, you'll have the chance to connect with people from around the globe, to expand your synthetic biology community, and to form new collaborations beyond the Giant Jamboree. You will meet fellow judges, students, and other professionals from around the world and different walks of life.
  • Learn About New Technology: You will learn about the latest cutting edge work being done in synthetic biology from student teams who are driven to excel and who test the boundaries of synthetic biology through their projects.

Application Process

This year we are accepting applications on a rolling basis. We will be evaluating applications at the end of each month starting in May and will contact applicants approximately two weeks after the evaluation period. Status notifications (1. invitation to judge, 2. invitation to serve as a reserve judge, 3. invitation to re-apply, or 4. decline for 2019 with an invitation to apply next year) will be sent in the middle of each month, beginning in June, until our quota is full (expected by August). We encourage you to apply early to increase your chances of being selected!

You can apply to be a judge before knowing if you can fully commit to attending the Giant Jamboree. Applicants who are invited to join the judging panel will be asked to confirm their acceptance. We can also provide an official invitation letter if you require that to secure funding and/or permission from your institute to participate as a judge.

Once we have reached our quota of judges, we will close the application and add a notice to this page.

Giant Jamboree Attendance

If you are selected as a judge, you MUST attend the iGEM 2019 Giant Jamboree in Boston (October 31-November 4) in person. We are unable to support remote participation for judges due to the nature of the interactions you will have with the teams throughout the event.

If you can only attend a portion of the Jamboree, this may make judging your assigned teams a challenge. We will work with you to try to accommodate your schedule constraints as best as possible, but we may rescind your invitation to judge in favor of another applicant who can attend the entire event. This will be evaluated on a case by case basis.

Judge Benefits

Instructor judges (current team PIs, instructors, and advisors) will receive a 50% discount on their Jamboree attendance fee.

Judges who are not affiliated with a team will receive free Jamboree attendance.

We are also excited to offer free childcare for all of our judges throughout the Giant Jamboree!

iGEM currently cannot provide travel funding for judges to attend.

Questions?

Please email traci [AT] igem [DOT] org and/or vinoo [AT] igem [DOT] org if you have questions!



Judge Application Form

This form has been submitted.

You can unsubmit the form if you wish to make further edits.

Click here to dismiss this message

1. General Information

Full name: -

Username: -

1. Email

2. Age

Note

To be eligible to become an iGEM judge, you must be at least 23 years old as of March 31, 2019. We also expect judges to have completed their undergraduate degree before the Jamboree takes place.

3. Gender

4. Institution

5. Institution type

6. Position

7. Region Where you currently live/work :

8. Number of years of iGEM experience as a:

Judge:


PI/Instructor:


Advisor:


Student:


Volunteer:

2. Jamboree Information

Please complete this section as well as you can. You will be asked to check or update this information prior to the Jamboree.

1. Sweatshirt Size:

2. Are you available to attend the entire Giant Jamboree from October 31 - November 4, 2019, in Boston?

2.1 If not, please indicate which days/times you are available to attend.

Day Morning Evening
Thursday
October 31

Friday
November 1



Saturday
November 2



Sunday
November 3



Monday
November 4



3. Conflicts of Interest

There are many possible reasons why you might be unable to judge some teams impartially. For example if you are a PI or instructor for the team, if the team comes from a school that you attended, or a school where you work or if you mentored or advised the team informally.

These situations could lead to a conflict of interest and iGEM takes conflicts of interests very seriously. Judges are not permitted to evaluate teams for which they have a conflict of interest. If you are a PI or instructor, your first responsibility is to your team, and we will schedule your judging assignment so that you are able to attend your team's presentation.

To select multiple teams, use Ctrl-click or Cmd-click. Don't recognize a team name? Look it up in the Team List.

1. Team Affiliations:

Please select any teams you are officially affiliated with (i.e. you are listed on the team roster as a PI, Instructor, or Advisor).



2. Conflicts of Interest:

Please select any teams for which you have a conflict of interest for another reason. (For example, a team that you mentored informally, or a team from the university where you were an undergrad student.)


3. If you have any other conflicts of interest that are not indicated above, please describe them:

4. Motivation

Please answer these questions in detail.

Did you apply to judge last year? View your answers from last year. Please note we have changed some of the questions for 2019.

1. Why do you want to be a judge in iGEM?

2. What professional experience do you have that you believe is relevant to iGEM (e.g., synthetic biology, hardware, software, human practices)?

3. How important is scientific and/or engineering success to overall team success?

4. What are the synthetic biology principles that iGEM participants should learn during their project?

5. Track Preferences

iGEM teams compete in several "tracks", based on the topics of their projects. Please see the Track page for more information on each track.

When we assign judges to teams, we will try to assign you your first preferences wherever possible. However, we can't anticipate how many teams will be in each track, so it may not always be possible to assign you your first choice. Therefore, you can indicate how you feel about each track. The more first choices you select, the more likely it is that you will be assigned teams in those tracks. If you are unable to evaluate teams in some track areas (software, for example), please put "Avoid" for those tracks.

Please indicate how highly you prefer each track. You may select multiple first, second, and third preferences.

Track First Second Third Neutral Avoid
Diagnostics
Energy
Environment
Food and Nutrition
Foundational Advance
High School
Information Processing
Manufacturing
New Application
Open
Software
Therapeutics

Thank you!

Thank you for filling out this form. We look forward to picking a strong judging team for 2019!

Finished?

Need to make changes?

iGEM Foundation

The International Genetically Engineered Machine (iGEM) Foundation is an independent, non-profit organization dedicated to the advancement of synthetic biology, education and competition, and the development of an open community and collaboration. Visit us at igem.org


hq AT igem DOT org


27 Drydock Avenue
Suite 27E-230
Boston, MA 02210


+1.617.500.3106