Best job interviewing books according to redditors

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

1. Make sure you're at least a little comfortable with HTML. At the end of the day, you have to output HTML (generally).
   
2. At least have looked at JSTL, maybe they don't use it, but take a glance.
   
3. Jakarta Struts is good to look at.
   
4. Relax.
   
5. Know where you'd look for an answer. If you don't know, say I'm not sure, but I was recently reading Horstmann's book and there's a chapter about it I'd review or that you could check google.
   
6. Think about your best quality, worst quality, (or how to answer these questions).
   
7. I have not personally read, but have heard EXCELLENT things from many people about Cracking the Coding Interview. I understand you don't have much time left for this, but if there is a next interview, it might be worth the read. (You might call actual book stores rather than wait on an online store.)

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!

The book Case In Point by Marc Cosentino is a very good resource for all case interviews. Check it out!

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!

There are tonnes of 'Inverview Questions' books out there. This one is probably the best known.

I second Programming Interviews Exposed. Also, check out Cracking the Coding Interview.

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.

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.

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.

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

I suggest looking through BOTH Cracking the Coding Interview and Elements of Programming Interviews.

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.