Reddit mentions: The best job interviewing books
We found 14 Reddit comments discussing the best job interviewing books. We ran sentiment analysis on each of these comments to determine how redditors feel about different products. We found 6 products and ranked them based on the amount of positive reactions they received. Here are the top 20.
1. Decode and Conquer: Answers to Product Management Interviews
- Designer style and superior security with this Kwikset Signature Series product; Smart key security re-key technology is compatible with Kwikset (KW1) keyway
- Customized automatic door locking after 30 seconds for peace of mind and keypad stays lit for 5 seconds after inactivity
- Featuring smart key security, which protects against advanced break in techniques and allows you to re-key your lock yourself in seconds
- ANSI/BHMA grade 3 certified
- Includes latch with adjustable backset 2 to 3/8 inches to 2 to 3/4 inches to fit all standard door preparations
- Comes with a lifetime mechanical and finish warranty and a 1 year electronics warranty
- Note: Please refer the installation manual below for better use
Features:
Specs:
Height | 9 Inches |
Length | 6 Inches |
Number of items | 1 |
Weight | 0.68 Pounds |
Width | 0.52 Inches |
2. 150 Most Frequently Asked Questions on Quant Interviews (Pocket Book Guides for Quant Interviews)
- A molded SkySculpt upper provides support inspired by intimate apparel
- Low-cut, slip-on fit with a fold-over forefoot for ease of use and mobility
- Machine wash COLD for durability, softness and convenience
- SkySpring architecture, EVA midsole and PU footbed for added comfort
- Offered in versatile solids and edgy, modern prints for feminine style
Features:
Specs:
Height | 6.88 Inches |
Length | 4.25 Inches |
Weight | 0.4 Pounds |
Width | 0.51 Inches |
3. Cracking the Coding Interview: 150 Programming Questions and Solutions
- Milton Bradley - MB - Hasbro
- STAR WARS
- EPIC DUELS Game
Features:
Specs:
Height | 9 Inches |
Length | 6 Inches |
Number of items | 1 |
Weight | 1.8 Pounds |
Width | 1.15 Inches |
4. The Pharmacy Professional's Guide to Resumes, CVs, & Interviewing
Used Book in Good Condition
Specs:
Height | 10.75 Inches |
Length | 8.25 Inches |
Number of items | 1 |
Weight | 0.00992080179 Pounds |
Width | 0.5 Inches |
5. How to Write the Perfect Resume: Stand Out, Land Interviews, and Get the Job You Want
Specs:
Height | 9 Inches |
Length | 6 Inches |
Number of items | 1 |
Weight | 0.44 Pounds |
Width | 0.32 Inches |
6. Case in Point Complete Case Interview Preparation
- Used Book in Good Condition
Features:
Specs:
Number of items | 1 |
Weight | 1.15 Pounds |
🎓 Reddit experts on job interviewing books
The comments and opinions expressed on this page are written exclusively by redditors. To provide you with the most relevant data, we sourced opinions from the most knowledgeable Reddit users based the total number of upvotes and downvotes received across comments on subreddits where job interviewing books are discussed. For your reference and for the sake of transparency, here are the specialists whose opinions mattered the most in our ranking.
OP try giving this text a read: https://www.amazon.com/gp/product/0615930417/ref=as_li_qf_sp_asin_il_tl_nodl?ie=UTF8&camp=1789&creative=9325&creativeASIN=0615930417&linkCode=as2&tag=seatintecoac-20
Basically a CC functions like this: Credit card companies make the bulk of their money from three things: interest, fees charged to cardholders, and transaction fees paid by businesses that accept credit cards.
Think of a credit card as a short term loan, so if you were to start lending money, what would you look into first? Determining who your target market is. Is the CC for college students, first time creditors, arm forces members, state employees, mid income or new creditors with 0 credit?
How are you finding your CC company?
Will you have crediting investors who would get profits from the collected interests over time it will you have shared holders of a financial institution?
Think about how you would go about establishing credit worthiness, credit interest tiers, payment methods, insurance, security and fraud etc.
Hope this gives you something to start on.
I am a physics PhD student who prepared for a quant transition and got an offer relatively soon after applying.
How much time do you have, where are you going to look, and from which university are your degrees? This book is an easy read, a bit American-centric. There are also books with preparation problems, I liked 1 2 3.
Play on your strengths - if you don't like programming just get a basic idea of how C++ work, and learn a lot of stochastic calculus if that's what you like. Eventually you should identify 1 or 2 areas which you like most and become strong in those. It's better to be so-so in some of the areas of the books above but beyond their level in 1-2 areas than being quite good at all of them but excel in none. Don't completely neglect any topic though - if you have no idea what a call option or a pointer are, you'll be in trouble. Don't neglect brainteasers.
Certain interesting areas are surprisingly ignored by those books, for example econometrics and machine learning. Good luck!
If I was running an 'Interviewing for PM roles 101' first and foremost I'd go over this article by Ken Norton. It runs the gamut of questions I've had over the course of many interviews and sets expectations around a possible interviewers frame of mind.
For books I have three: Cracking the PM Interview, Swipe to Unlock, and Decode and Conquer. Cracking the PM Interview is a general overview of what PMs do, how to prepare for interviews, and general interview questions. Swipe to Unlock give reasons for why certain PM decisions were made and the strategy behind it. Decode and Conquer has more interview questions, but also sample answers to them and is a bit more technically-focused.
My recommendation is to come up with something you want to build and explore what it would take to do that. For example, what if I was interested in who would win the Oscars? I might use Twitter's Search API and explore which movies come up the most with the hashtag Oscars. What would that take? Well, I would have to integrate with Twitter security so they know it's a valid request, use Twitter's documentation to figure out how to search for terms, and then import that into a data analysis tool to do sentiment analysis. In an interview I discussed what I would build, worked through what features I would want to add, and a roadmap for deployment, which was a fun exercise!
Don't ask any "gotcha" questions. Interviews are stressful enough. Please don't add to it by asking foolish trivia questions around a particular language's minutiae. Ain't nobody got time for that.
Do look up the questions that you can and cannot legally ask of a candidate. For instance, you can ask "Are you authorized to work in the United States without sponsorship?" but you can't ask "What's your nationality?" Google "illegal interview questions" for more.
If one must ask someone to whiteboard a problem, it's better to ask them to work out the algorithm they would use to solve the problem than have them actually write out code. Whiteboarding is a very artificial way of coding. Is that what you're going to do on the job? Of course not. You're going to be typing code into an IDE with a debugger, not be writing if-then statements with a Sharpie. You're trying to determine the logic process the candidate follows to solve a problem. That's the important thing.
Borrow a copy of Gayle Laakmann McDowell's Cracking the Coding Interview and go through the chapters dealing with "The Interview Process", "Special Situations", "Behavioral Questions" and "Technical Questions" to get a feel of how professionals do it.
I saw a quote from the founder of Visa the other day which is fitting here:
> "Hire and promote first on the basis of integrity; second, motivation; third, capacity; fourth, understanding; fifth, knowledge; and last and least, experience. Without integrity, motivation is dangerous; without motivation, capacity is impotent; without capacity, understanding is limited; without understanding, knowledge is meaningless; without knowledge, experience is blind."
Also, remember that you conduct a bunch of interviews for about a week and then don't have to interview people for months at a time. The person on the other side of the table, on the other hand, has been attending interview after interview after interview. They're probably beaten down by the process (and on the flip side have more experience with interviewing than you have)...so, be kind to them. That would be the best way to give a good impression of your company, even if in the end you don't choose that candidate, they will remember how well (or how badly) you treated them on the day.
Good luck.
Have you read Decode and Conquer (http://amzn.to/29G0irv) and How Google Works (http://amzn.to/29G0p6k)?
Some videos:
https://userbrain.net/blog/product-management-videos-that-are-worth-your-time
But still, I'd love to keep learning. Especially about improving people skills. It gets more important as you move up.
I’d recommend this book: The Pharmacy Professional's Guide to Resumes, CVs, & Interviewing
https://www.amazon.com/dp/1582121486/ref=cm_sw_r_sms_c_api_i_bZvTCbJ76EF62
It has a lot of good examples and has served me well.
I haven't read this one myself, but from hearing Grey and Myke talk about their experiences, I think this book could be very helpful.
There are tonnes of 'Inverview Questions' books out there. This one is probably the best known.
The book Case In Point by Marc Cosentino is a very good resource for all case interviews. Check it out!
https://www.amazon.com/gp/aw/d/0979757649/ref=mp_s_a_1_10?ie=UTF8&qid=1474590120&sr=8-10&pi=AC_SX236_SY340_FMwebp_QL65&keywords=quant
This one is good IMO
As others are bound to point out, read through Cracking the Coding Interview and/or Programming Interviews Exposed. Both books walk you through a large variety of common technical interview questions--with an emphasis on the reasoning to get to the correct answer.
Keep in mind that many of the problems you face aren't going to be in those books. The key is to be able to recognize the problem and then use something from your toolkit to solve it. Part of this is practicing these kinds of problems (the above books will help, as will puzzle sites like TopCoder, Google CodeJam, Project Euler, etc.) so that you know how to recognize the problem. The other half is just having a big tool box. You need to be pretty solid in fundamentals like sorting/search algorithms, data structures (trees tend to be especially popular), recursion, etc. During the interview, constantly communicate your reasoning and what you think the problem represents and why you're going to use a specific kind of solution.
Here are some other great resources to look through:
Topics you should be familiar with
Variety of problems that you may be asked
A lot more resources
I second Programming Interviews Exposed. Also, check out Cracking the Coding Interview.