Reddit reviews Cracking the Coding Interview, Fourth Edition: 150 Programming Interview Questions and Solutions

Looks like you're getting the interviews, but not getting the job. Try going to the Tatham Centre and brushing up on your interview skills. Read up on Cracking the Coding Interview. Keep trying!

Search algorithms and data structures will be pretty important for the interview, but if you're a bit rusty, there's probably still time to brush up on stuff before the interview. Books like Cracking the Coding Interview or Programming Interviews Exposed really help.

One thing to be careful about on the interview though is to not get too hung up on finding the best possible answer to a question. Yes, coming up with an efficient solution is good (and if you give a less than optimal solution, your interviewer will probably ask you to improve it or add more constraints), but if you cannot come up with any solution, even a naive one, and aren't able to code it (or run out of time because you spent too long trying to find an efficient solution), you probably won't make it to the next round.

In general though, you shouldn't be asked too many questions that require memorization as long as you know the basics (and you should be able to discuss space and time complexity for any solutions you provide). If you have any more questions though, feel free to send me a PM (I work at Amazon).

You should take a look at Cracking the coding interview.

This book should be very useful: http://www.amazon.com/Cracking-Coding-Interview-Fourth-Programming/dp/145157827X/ref=cm_cr_pr_product_top

There is a book called Cracking the Coding Interview which I highly recommend for such tasks. It has some tough questions that are usually asked at an interview setting. This is the best way to practice your algos, IMO.

"Programming Interviews Exposed" suggested by Kaelin is pretty helpful. Personally for me, Cracking coding interviews was extremely helpful. I highly recommend it. Read from the beginning, even the chapters before the technical questions. For technical questions, only once you are satisfied with the solution you come up with or when you have spent enough time trying to solve it, look at the solutions.

I would also suggest looking for questions online and then try to solve them. Again, avoid looking at the solutions as much as possible.

Kinda late but

Software Engineer, been working 1year ~ 3 months now. I have no Github account and no personal projects on my resume, but I did list relevant class&internship projects, and my resume is also pretty beefed with work experience and extracurriculars, as well as honor societies, even though my GPA isnt super stellar.

• easy peasy. Talked to someone at a job fair (funnily enough, not usually who you'd think of as a tech company), ended up getting a call, they lost my resume, and then found it again a couple weeks later. Finally the week before I was due to respond to a different offer, they asked me to go in for an interview, I did, and I got the job a few days later.
  
• Resume wise, I was webmaster of my school's TBP chapter, and my internship involved extensive web work. The job was for a web company so i think they liked that. That and I was really chill during my interview, and bonded with one of my interviewers over the fact that we both dance. I've heard that they base their hiring a lot on who they think will fit into team dynamic, so it's important to relax and be yourself.
  
• Yep. I work in socal, and I live in a less expensive area, but I bought a new ~30k car, travel regularly, and go out to eat often. In terms of work/life, sometimes I end up working too much just due to how deadlines work out, but you get that everywhere. 80% of the time I'm chillin.
  
  This book -> http://www.amazon.com/Cracking-Coding-Interview-Fourth-Edition/dp/145157827X did me wonders during the interview process.

Hehe, I wrote that while taking a break from reading something about forgery versus borrowing in art, so everything I came up with was related to that.

Another interesting problem is something that may not be well documented (and thus may be hard to write about), but a friend of mine's boss (that sounds far removed!) has noticed a serious lack of actual ability to code in people pretending to be software engineers. That's why you get interview problems like fizz buzz--interviewers actually do need to check that you actually can code before doing anything else because there're a lot of people who apply for those jobs thinking that they can just 'design code' instead of actually writing code. The coding interview is actually another really interesting problem for our field--not only 'how do you determine whether or not someone is qualified in an interview' but also 'how do you prove that you're qualified in an interview'. There are even books on the subject, such as Cracking the Code. (Speaking of which, if your CS major doesn't require you to take probability/proofs/logic/combinatorics/discrete math classes, take them anyway.)

And I babble. Good luck :D

A great GPA (3.8+) will take you far. Also, put some webdesign-related projects on your resume!

If you can, go to a career fair. Be friendly, be prepared, and follow up with thank you e-mails.

I'm not sure how interviews for UI people go. If companies give technical interviews, I recommend you buy and review one or both of the following:

I recommend: Programming Interviews Exposed: Secrets to Landing Your Next Job

And:
Cracking the Coding Interview, Fourth Edition: 150 Programming Interview Questions and Solutions

If not, I'm not sure. Sorry.