Open kmolo opened 9 years ago
Of the possibilities under discussion so far:
no.1 seems complex to implement and likely to contain stale information over time (Is an internship and its contact details evergreen? in my experience, no). It seems much easier to forward announcements to the Google Group as they come, and request that members reply to the thread if they (1) get the internship or (2) pursued the internship in any way and can offer insight to others considering approaching the company in the future. Annually, this feedback can be collected and published all together (as we are trying to do for the minutes of the Industry feedback panel, which currently is lingering in a pinned thread in our Google Group).
no.2 also seems complex, but very important to collect Feedback from students about internships they have actually held is very valuable, and should be collected and available to all CCSF CS students. I wonder if the CS197/198 class (currently taught by Aaron Brick) is collecting anything like this? As an interim solution, we might host a panel discussion of students who have had internships & representatives from companies that regularly take interns. Another related solution might be hold a standing feedback panel (like the Industry Feedback panel) comprised of students who have had internships & representatives from companies that regularly take interns. [I'll take responsibility for floating these two ideas elsewhere, so they can be worked on separately.]
no.3 and no.4 both seem fairly easy, and will contain fresh leads without any ongoing work required
I vote that we pursue:
More detail about using the 'Jobroll' webmaster tool from Indeed.com:
I generated the following code
<script type="text/javascript">
<!--
indeed_jobroll_title = 'Search more Jobs';
indeed_jobroll_background_color = "#FFFFFF";
indeed_jobroll_width = "150px";
indeed_jobroll_text_font = "10px Arial, Helvetica, Sans serif";
indeed_jobroll_link_color = "#000000";
indeed_jobroll_border = "1px solid #000000";
//-->
</script>
<script type="text/javascript" src="http://www.indeed.com/jobroll?q=%28Java+or+Python+or+Ruby+or+SQL+or+C+or+C%2B%2B+or+PHP+or+perl+or+Android+or+iOS+or+iPhone+or+iPad+or+HTML+or+CSS+or+JavaScript+or+Javascript%29&l=San+Francisco,+CA&jt=internship&sort=date&limit=10">
</script>
<noscript><a href="http://www.indeed.com/">Jobs</a> by Indeed</noscript>
...from this original search:
...which is just an Indeed.com search for jobs in San Francisco using the keywords for every CS skill taught at CCSF that I could think of, limited to the JOB TYPE = Internship (this being the awesome feature of Indeed.com for internship searching).
One wrinkle, the Jobroll auto-generated code doesn't include anything but location & keywords. I was able to manually add '&jt=internship&sort=date' in the code above, but when you click the 'Jobs by Indeed' link that Indeed.com has next to the created box, the original link is somehow embedded, and so drops those key parameters.
For the first iteration, I say use the boilerplate code.
Then, if someone can figure out how to write a custom version that wouldn't have this problem, that can be implemented later.
Moving issue from https://github.com/mrpaxton/ccsf_coders_website/issues/5
Possibilities under discussion (so far):
...after our discussion here, we might spin off separate GitHub Issues for the incremental work phases.