Eric Schmidt says, "The interview is where you truly learn about a person it is far more important than the resume."[1] Come and learn about the ideal interview experience, work through selected problems from Cracking the Coding Interview[2], share and (constructively!) critique resumes, and share strategies towards handling the less-than-ideal case.
[1] http://fortune.com/2014/09/04/how-google-attracts-the-worlds-best-talent/
[2] http://www.google.com/search?q=cracking+the+coding+interview+pdf

Preparation:
* Choose one position that you would love to apply for. Prepare a tailored resume and cover letter, and bring those plus the position description.
* Bring pen and paper for coding. If using a laptop, plan to use a plain-text editor, not your usual coding editor.
* Choose an interview-coding problem from somewhere on the web, and give yourself 30-40 minutes to solve it using pen-and-paper. Extra credit: Afterwards, write a well-tested solution and upload it to github. Consider bringing the link to share.

Itinerary:
7-7:30 What to expect, prep strategies.
7:30-8 Coding practice.
8-8:30 Other question types, fielding bad questions, q&a
8:30-9 Peer review of resumes and code.

Instructor Bio: Gregory Marton is a software engineer with about 200 interviews at Google and a few in other settings. He regularly teaches a class aimed at helping candidates prepare for their Google on-site interviews; this session is new material, broader, and not company sponsored. He has Master's and Engineer's degrees in EECS from MIT.