Bookshelf section in CV.

Question

I'm finishing M.Sc. in physics soon but I want to work as software developer. I have broad yet often shallow knowledge of programming. I can learn programming-related things easy, I have no problems with pointers etc... However I have no experience working on large or even medium scale projects, only writing code for myself for fun, topcoder competitions, simulations for my thesis... The message that I want to deliver to the employer is that I already have broad theoretical knowledge and ability to learn from printed materials. (It also includes reading specifications, tutorials etc...). I think it is my strong side as other graduate students here often ask me to look at the googled answer to their matlab/C/fortran/linux-configuration problem and interpret it for them.

I have bookshelf section in my CV that mentions several classic and/or important books like "Code Complete" and "Design Patterns". I really learned from these books and found them useful yet again I (almost) never applied what I learned from there in practice.

I heard that it is not a good idea to put Bookshelf section in CV for several reasons. Could you explain me these reasons?

How else can I deliver this message to the employer?

Edit: To be honest I'm probably "Smart but does not get things done" by Joel classification. I know it is a bad thing.

I understand data structures/algorithms no worse than many B.Sc. Comp.Sc graduates and can solve related problems no worse and in less time that they can.

Some (poor) excuses: I never worked in real (shipped) projects. I worked only on projects without well defined requirements I prefer to work in group. I guesstimate that monetary motivation could keep me going when I get bored.

I think I'm still a good choice for employer willing to invest and give me some time.

Answer 1

The list of the books that you read doesn't tell too much about you. Instead you can just list what you know/master (that you acquired by reading these books).

And in a separate sentence in the CV you can also directly say that you "have broad theoretical knowledge and ability to learn from printed materials."

Answer 2

I don't think it is always a bad thing to point to some book that you think influenced you, but think what you're trying to tell an employer, how wille this benefit them? If they are looking for someone with a broad theoretical knowledge then sure, show them how braod your knowledge is. If they are looking for someone with very specific experience in a certain field then naming a lot of books won't do you any good, they might wonder if you read the job description at all.

Answer 3

I think it looks silly. I don't care that you've read a book. I care that you've read a book and applied the material in some relevant way.

However, you're just coming out of school so people won't expect you to have a lot of experience.

The message that I want to deliver to the employer is that I already have broad theoretical knowledge and ability to learn from printed materials.

Sorry, I wouldn't even say that. You're basically saying I just earned my master's degree and you know what I can do? Read a book and learn from it!. Frankly, thats just embarrassing. The ability to read something and internalize the material is a basic requirement for almost any job, let alone a technical position.

Answer 4

Employers look, among other things, for the ability to learn. A bookshelf section is too easy to copy from another CV, or a list of good programming books on the web, etc. I suggest you write the things about your learning ability in a cover letter, or for them to arise from the list of projects you wrote during your studies. See Steve Yegge's Get that job at Google for a list of books and what you can make of them.

Answer 5

Having a large book shelf doesn’t say anything about the capability of its owner. (Some even buy books just to look good.) And having read a book doesn’t mean you have understood what the book is about.

So appending a list of books that you have already read is not very expressive to me. Since others already pointed out that you could just have copied some popular titles to look good.

So when you want to become a programmer, you should do some programming instead. It’s better to say “I’ve worked on project X and my theoretical knowledge I’ve earned reading Y helped me a lot” than just “I’ve read Y and I think it might help me”.

Answer 6

Your paper CV is only one part, and a small one at that, of how you "sell" yourself to prospective employers. Consider whether you want to spend the space on something that may not be a differentiator. Think of the paper CV as a flyer.

On the other hand, I would definitely include books - ideally with short essays or notes - somewhere on your Web site and point readers of your CV to that.

Answer 7

I agree with a number of replies to this thread, in that I wouldn't put much merit in a book list. (It might even detract from a CV.).

I suggest you take the knowledge you've gained and use it to help an open source project of some sort, or your own project.

This experience can then be listed on your CV, which will help you much more then any booklist.

Once you're at the interview stage, you can name drop books as much as you like, if the conversation warrants it.

Answer 8

As a general rule of thumb, I don't put anything on my CV I am not prepared to discuss with an interviewer for at least 10 minutes, because every line of a resume is fair game. So ask yourself this question -- do you want to spend 10 minutes of your interview discussing the book "Code complete", or what simulations you wrote? The other guy interviewing for the same position will be discussing his code, not a book.

I think there are a lot of hiring managers out there who know the value of an education in fields other than CS. This industry is filled with formally educated physicists, chemists, and mathematicians. It isn't all that unusual.

It sounds to me like you feel a bit insecure about your level of experience; but the truth of the matter is, almost everyone graduating from the University has not worked on large projects -- just class assignments and simulations. Go into depth about your simulations. Make sure you don't just write what you did ("wrote simulations of geothermal disturbances on California coastline"), but what your software helped you achieve ("This work made it possible to accurately predict the Great Big Earthquake of 2011").

Your resume will look different than other candidates'. That's a good thing.

Answer 9

You know, after thinking about your question for a bit, I think that you are asking the wrong type of question here. :) Granted, you are looking for the best way to prepare your CV so that you can get a job which will help to build upon your experience, which is essentially where you feel your CV is weak, and hence, why you asked your question.

Now, I'll take your word for it that you're the "smart but doesn't get things done" type, but that's actually very easy to remedy -- you just need to start doing things. Build that widget app which you always wanted to make or contribute to an open source project. These are all things which "count" on your CV, even if it wasn't done in a workplace.

And best of all, it'll give you a chance to apply some of the things which you've been reading about. :)

Answer 10

Being an avid reader of programming books is something you should tell a prospective employer. It lets them know that you have a passion for software development and that you take the initiative to learn new things on your own.

However, your CV is not the appropriate place for this information. Your CV should be a quick, concise run-down of "this is what I've done".

I believe the place to discuss the relevant books you've read is in the interview. For example, in one interview I had about a year ago, I mentioned that I was reading "Code Complete". One of the older guys across the table perked up, told me he had it and loved it, and we ended up talking for a few minutes about it. The next day, I got multiple job offers from that company.

Answer 11

I use LinkedIn as my primary CV, they've recently added a bookshelf feature.

I think it's pretty cool, since I read a lot and want my future employers (and coworkers) to know that I stay up to date on current technologies and techniques.

I would also be prepared to discuss any of these books at an interview situation.