<node id="584445">
  <nid>584445</nid>
  <type>news</type>
  <uid>
    <user id="33693"><![CDATA[33693]]></user>
  </uid>
  <created>1480531615</created>
  <changed>1480533653</changed>
  <title><![CDATA[Tech Wreck Camp Staff Positions]]></title>
  <body><![CDATA[<p><strong>General Requirements of Wreck Camp Staff</strong></p>

<ul>
	<li>Must be in good academic and disciplinary standing with Georgia Tech</li>
	<li>Must have at least a 2.3 cumulative GPA</li>
	<li>Must be enrolled at Georgia Tech in the fall of 2017</li>
</ul>

<p><strong>Wreck Camp Counselor Duties</strong></p>

<ul>
	<li>Be committed to Wreck Camp from February - September 2017</li>
	<li>Interact with incoming students for camp activities, serving as a small group leader for 10 to 15 student participants</li>
	<li>Participate in all camp functions</li>
	<li>Be a positive role model and good representation of the Institute and Georgia Tech community for participants</li>
	<li>Participate in all training sessions during the spring of 2017, including a Staff Retreat (February 18-19)</li>
	<li>Contribute to staff in a positive and energetic fashion, always being a team player</li>
	<li>Serve as a member of a Wreck Camp committee</li>
</ul>

<p><strong>Wreck Camp Crew Duties</strong></p>

<ul>
	<li>Be committed to Wreck Camp from February - September 2017</li>
	<li>Interact with incoming students for camp activities</li>
	<li>Participate in all camp functions</li>
	<li>Be a positive role model and good representation of the Institute and Georgia Tech community for participants</li>
	<li>Participate in all training sessions during the spring of 2017, including a Staff Retreat (February 18-19)</li>
	<li>Contribute to staff in a positive and energetic fashion, always being a team player</li>
	<li>Responsible for implementing all logistics for the Wreck Camp program (i.e. setting up group rooms, setting up for arrival of participants, etc.)</li>
	<li>Plans and implements the Wreck Camp games, a &quot;field-day&quot; competition between the Wreck Camp Color Teams</li>
	<li>Overseen by the Director of Operations and Media</li>
</ul>

<p><em>**All applicants will be considered for both Counselor and Crew positions.**</em></p>

<p><em>Wreck Camp staff are not required to be in the Atlanta area during the summer months. However, please review our&nbsp;Mandatory Dates&nbsp;and&nbsp;Summer Plans&nbsp;sections of this page and the application for more information on those requirements.&nbsp;</em><br />
&nbsp;</p>

<p>The following dates will be Training Sessions that will occur from 6:00 - 8:00 p.m.:</p>

<ul>
	<li>February 6</li>
	<li>February 13</li>
	<li>February 27</li>
	<li>March 6</li>
	<li>March 13</li>
	<li>March 27</li>
	<li>April 3</li>
	<li>April 10</li>
	<li>April 17</li>
</ul>

<p>The following dates will be an all Staff Retreat that will be overnight:</p>

<ul>
	<li>February 18-19</li>
</ul>

<p>The following dates are Pre-Wreck Camp Training and Wreck Camp 2017 dates:&nbsp;</p>

<ul>
	<li>Pre-Wreck Camp Training: &nbsp;August 9 &nbsp; 8 a.m. - 5 p.m.</li>
	<li>Wreck Camp 2017: August 10-12</li>
</ul>
]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2016-11-30T00:00:00-05:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Apply by midnight TONIGHT if you would like to be a summer camp counselor with Tech Wreck Camp ]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_media>
          <item>
        <nid>
          <node id="186361">
            <nid>186361</nid>
            <type>image</type>
            <title><![CDATA[Wreck Camp 2012 - color fight]]></title>
            <body><![CDATA[]]></body>
                          <field_image>
                <item>
                  <fid>196162</fid>
                  <filename><![CDATA[img_3691.jpg]]></filename>
                  <filepath><![CDATA[/sites/default/files/images/img_3691_0.jpg]]></filepath>
                  <file_full_path><![CDATA[http://hg.gatech.edu//sites/default/files/images/img_3691_0.jpg]]></file_full_path>
                  <filemime>image/jpeg</filemime>
                  <image_740><![CDATA[]]></image_740>
                  <image_alt><![CDATA[Wreck Camp 2012 - color fight]]></image_alt>
                </item>
              </field_image>
            
                      </node>
        </nid>
      </item>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>473211</item>
      </og_groups>
  <og_groups_both>
      </og_groups_both>
  <field_categories>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>473211</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[_OLD: School of History and Sociology Student Blog]]></item>
      </og_groups_both>
  <field_keywords>
          <item>
        <tid>166849</tid>
        <value><![CDATA[HSOC Blog]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
