91–100 of 225 posts
Someone recommended Skiena's "The Algorithm Design Manual" and I picked it up. If you feel like more exposure to data structures can be useful, it has a section titled "A Catalog of Algorithmic Problems" which I find useful to read before an interview.
Earlier quoted context omitted.
It's possible the position was filled, so some hiring manager just cleared the queue.
Good point; never really thought about that. I just found it odd because their email response actually gave me a reason stating my resume didn't have enough experience for the position when it far exceeded everything they wanted for the position.
I'm only a rising junior in CS on my second internship and I completely agree. I did really well in my Data Structs & Algorithms class (A+...) and I just hate these types of problems. I bombed Google and Dropbox's interviews, and am ready to never go through another process like that again if I can. I've been exceedingly lucky landing gigs at great companies that don't filter with these questions. I worked for LeadGe…
Earlier quoted context omitted.
pojo is a common term for java devs, at least any who have been molested by spring
It's also seen some use in the Javascript community as well (though not nearly as common).
This type of interview questions worries me. My nervousness then permeates throughout the whole interview so I've never been asked these type of questions, which is unfortunate as perhaps it's not as bad as I make it. Someone recommended Skiena's "The Algorithm Design Manual" and I picked it up. If you feel like more exposure to data structures can be useful, it has a section titled "A Catalog of Algorithmic Problems…
Algorithms: Design and Analysis, Part 1: https://www.coursera.org/course/algo
Algorithms, Part I: https://www.coursera.org/course/algs4partI
Earlier quoted context omitted.
I was told by someone many years ago to always take a copy of my resume with me to an interview. That advice has paid off a couple of times. These days I also keep an email draft ready to send.
While that's good advice, I don't follow it. If a company doesn't have their shit together enough to coordinate an interview schedule and get the right people into the right room at the right time with my resume in their hands, ideally in their hands ahead of time, I don't want to work there. It's a basic competence test.
They feel the same way about you having your own resume in an interview.
>You are then ushered into a room with the programmer's worst nightmare - a blank whiteboard. Am I the only one who enjoys programming interviews? Even if you screw it up, it's still fun to try your hand at whatever problem they give you. They also don't expect you to do it perfectly; you're allowed to have sub-superhuman performance.
I interviewed at Microsoft and it was about 10 hours of this stuff and I loved it. Had a great time, and I think I did pretty well. One guy wanted me to write a shuffling program. So I came up with one which I later discovered was Fisher-Yates and optimal. But he kept saying "how can it be faster" so I'm not sure what I was missing. Most of the other stuff was pretty fun and straightforward - pointer stuff, string co…
This passage gives me a good idea: The OPower guy said they had a ton of problems where they will be using Scalding, so I asked him what they are doing in its absence. He said Oh we pojo it. Then he said pojo this and pojo that, and soon I was drowning in pojos, so I asked, Sorry, what exactly is a pojo ? Now, bear in mind I am a Scala programmer and haven't touched Java in ages, and they knew that. Their whole pitch…
Earlier quoted context omitted.
I was told by someone many years ago to always take a copy of my resume with me to an interview. That advice has paid off a couple of times. These days I also keep an email draft ready to send.
While that's good advice, I don't follow it. If a company doesn't have their shit together enough to coordinate an interview schedule and get the right people into the right room at the right time with my resume in their hands, ideally in their hands ahead of time, I don't want to work there. It's a basic competence test.
I recently interviewed for (and got) a new job. The interview process took about two weeks and on the whole was pretty reasonable for both sides. There was a short phone screen (~30 minutes) Then I had two technical exercises to do. For each, I was given a reasonable time period (4 hours) that started when I visited a special link to the get the problem description, and then used whatever tools I wanted to get it don…