Resume Advice

Below is a standard set of resume advice I provide – it may or may not apply to your resume.

Your resume is a distillation of who you are, your experience, accomplishments, stengths, and goals that explains how you are a potential fit for a position.  It is NOT simply an accounting of your work history.  Failure to understand the goals and mechanics of a good resume will eliminate you from contention for all but commodity jobs.  If you don’t understand how a resume works and take the time to make this critical document the best possible representation of your work, how should a hiring manager interpret that?

Your resume needs to tell who you are, list (not explain) relevant skills/experience, and demonstrate your strength as a candidate.  Read this first.  It’s a great big picture view of how to build your resume and why.  Note that technical candidates need to modify this advice accordingly (“wrote 5000 lines of code saving firm $10mm” just doesn’t fly).

Frequent issues:

• Too long – nobody has time, respect that
• If you can’t distill information on your resume, what does it say about your ability to do so on the job?
• It is NOT a list of everything you’ve done
• Do not include mundane items that everyone in your job probably does – Ex: “Used JIRA to track bug fixes.” (yawn, delete)
• It IS a list of relevant experience, capabilities, and strengths – I want to know what you CAN do
• Too much prose
• Don’t write “The ABC system is for XYZ.  My responsibilities were to do …”
• Use concise, bulleted statements to list relevant information
• Give your reader the benefit of the doubt – they know the context
• Remove Summary – your resume is a summary.  If you feel a need for a summary at the beginning, something is wrong.
• As for Introduction/Profile paragraph, see http://theundercoverrecruiter.com/write-an-interview-winning-cv/, #3
• Don’t describe the companies you worked for (unless in circumstances where the company isn’t known)
• Make sure it’s clear where you were a contractor!
• Job movement is a red flag to hiring managers.  Contracting explains movement, so don’t omit where appropriate
• Spelling/formatting are important – what does it say to the reader that you can’t be bothered to check/fix obvious errors?
• Make absolutely sure there are not misspellings, grammar issues, etc.  MS Word is your friend and enemy – it will immediately show the reader every mistake in the document.  Extra/missing spaces are common
• Have someone proofread, especially if you are not a native English speaker
• Formatting should be clean and consistent
• Http://affinityny.blogspot.com/ - articles on resume writing
• Remove detail for older positions, especially when not relevant
• Don’t include GPA’s and other scores that aren’t notable
• Don’t include if it’s more than a few years ago
• Don’t use the third person
• Don’t name your resume JohnSmithML, so the reader knows this is your resume tailored for ML jobs

What does a hiring manager want in an employee?

Universally, they want people who are:

•           Smart
•           Dependable
•           Hard working
•           Easy to work with
•           Able to work independently
•           Know when they need help
•           Able to solve problems (this may be the sum of all of the above)

For a given job, you need the main skills, but certainly not everything listed in the job spec. Then your job is to convince the employer of all of the above.

Getting Hired at Google

Hint: Getting hired is not about your G.P.A. It’s about what you can do and what you know - Part 1.

I think this article, Part 2, is even more insightful.

Laszlo Bock is Senior Vice President of People Operations at Google Inc.  Check out his writings - has has written many insightful articles on hiring, interviewing, and people management.

Every time we step up to try something new, we learn more than we expect - Barry Farber

Interview Preparation - Technical Interviews

Interview Preparation
Nothing prepares you for interviews more than your work experience.  You can’t fake knowledge and experience, and it’s very important that you don’t try to represent experience that you don’t have.  However, interview preparation is critical!  Below are some pointers to help with the process.

Resume
Most interviewers will ask you specifically about what is on your resume.  Therefore, it is critically important that you know very well the areas you represent on your resume.  There is a balancing act between selling yourself and over-selling yourself.  You need to work on your resume to strike the right balance.

The Obvious
Know where you are going and who you are meeting with, and allow plenty of time to get there.  Be on time.

Dress appropriately.

Turn your phone off!  Never look at your phone during an interview.  It's rude and makes a terrible impression.  Worried about emergencies?  The probability that you will receive an emergency call during an interview is less than the probability your children will starve to death if you don't get the job.

Don’t eat, drink, or smoke before the interview.

Bring some energy – being well rested is important, but also, don’t forget that you are selling yourself, so you need to exhibit positive energy.

For phone interviews, make sure you will be in a quiet place, preferably on a land-line, and won’t be interrupted by children, dogs barking, etc.

The Somewhat Less Obvious
Know the details of the role you are interviewing for.  If your agent hasn’t provided sufficient detail about the role, insist on it. 

Research the company you are talking to.  Learn something about the industry if you are changing industries.  (http://www.recruitingblogs.com/profiles/blog/show?id=502551%3ABlogPost%3A1355203)

Behavioral Questions
 Many interviewers will ask some number of behavioral questions.  Since these types of questions are common practice, it doesn’t make a good impression if you are unprepared for them.  Make sure your answers reflect your personality and convey the message you are trying to communicate.  Generally you can come up with a few stories that can be modified to suit a number of different questions.  Many common questions are listed in this article: http://blog.timesunion.com/careers/50-behavioral-based-interview-questions-you-might-be-asked/1538/.

Your answers will be far better with preparation.  Practice your answers with someone who can give you feedback.

Technical Questions – Areas to Review

Data structures.  These are the building blocks of computer science, and most strong teams want to make sure your fundamentals are sound to ensure that your understanding and decision making at all levels is predicated on a solid foundation. Wikipedia has an excellent list of data structures here http://en.wikipedia.org/wiki/List_of_data_structures. 

Algorithms.  It's harder to point to a concise list of algorithms for study.  Sorting and traversing data structures are fundamentals to be sure to know.  You should be very comfortable with questions such as:

- Write the pseudo-code for performing a depth/breadth first traverse of a binary tree

- Is a hash table a good data structure for storing data in an application that support partial search such as "select * from MyTable where name like 'John%'.  If not, what is?

Databases.  The database may not be your focus, but there’s a database underneath just about every piece of software.  If you use a database at all and might be asked about it, know the fundamentals of SQL.  Make sure you know the syntax for joins (inner/outer), self-joins, grouping, having, etc.  This is one of the most frequent stumbling areas in technical interviews, because   many developers forget to brush up on basic SQL syntax.  You may use SQL regularly, often googling for specific syntax, but if you can't rattle off the correct syntax in an interview, you will get pegged as "light on database."  Beyond the basics, be sure to know the harder aspects of using a database properly – optimization, locking, and the transaction log (of course there's way more, but the depth of your database knowledge will depend on your experience).

Problem Solving/Puzzle Questions

There are any number of these types of questions, and you will do well to search the web for examples.  Google is famous for some of the trickier and more challenging questions.  While it is impossible to study all of these, it is very useful to practices many examples.  This practice provides familiarity with a variety of techniques for attacking these types of problems that can often be applied to other variations.  It also gets you used to the type of thinking that is necessary to solve these types of questions. 

Here are a few important things to keep in mind when answering questions:

·         Be honest about what you know and don't know.  The surest way to fail an interview is to say you have expertise in an area and then fail to demonstrate what you have represented when the interviewer asks about that area.  Your job is to demonstrate that you are good at what you have experience with and can learn whatever is necessary to be successful in your new job.

·         You don't need to get the answer to every question to do well.  The interviewer wants to see sound reasoning and creative approaches more than exactly the right answer.  When answering a question, if your ideas are sound, and you follow a logical progression of steps, possibly down a series of dead-ends but using solid reasoning along the way, you will likely make a good impression.  

·         When you don’t know the answer or how to start on the problem, never say, "I don't know!" Instead, say, "That's an interesting question, let me think about that."  Then do your best to bring your problem solving skills to the task.  Don't hesitate to ask questions about the problem to learn more.  This is also a way to get more time to solve the problem, as your subconscious will already be working on a solution.  Now it's about problem solving, so you want to demonstrate sound capabilities as you attack the problem.  If you are reasoning well, it is typical that the interviewer will give you hints and help you solve the problem as they see your progression.  Now the exercise becomes collaborative, and both you and the interviewer will learn a lot about each other.

Closing

You will be asked if you have any questions.  You may or may not.  Here is a good list that may give you ideas: http://www.careerbuilder.com/Article/CB-664-Getting-Hired-The-Best-Questions-to-Ask-in-the-Interview/. 

At the least, be sure to thank the interviewer for their time, express your enthusiasm for joining the company (if true), and ask what the next steps will be if they decide to move forward.  An example:

“Thank you so much for taking the time to speak with me today!  I’m very excited about the opportunity, even more so after talking with you and learning more about the role.  What are the next steps in the process if you decide to move forward with my candidacy?”

Last Thoughts

Preparing for an interview is work, but the payoff is significant.  Remember, the next person in the door to interview for the job has done their homework.