This was in 2013 so it's out of date now, but it was very clear from the line of questions and the attitudes of the interviewers that they were being made to be there and saw no point. They were in general completely disengaged with me. Of the interviewers all but the last were fairly professional. The last pair I had were more junior and made it clear that I was wasting their time as far as they were concerned.
To be fair I interview poorly, but I would would have much preferred for the person managing the interviews to cut off the process as soon as they were sure that I wasn't a fit. By failing to do so it just created an awkward and frustrating situation.
Sorry to be a broken record, but can you give some specific examples?
I ask because elsewhere on this thread you have people bitching that they were asked some low level CS questions about inverting binary trees and the like, and how insulting they found that.
While I sympathize, it's not going to change the fact that the company does want to hire engineers that are equally competent at contributing to some sexy new high-scale AWS services as some boring business reporting features. Google, Facebook, and Microsoft all do exactly the same thing.
On the other hand, if you had people that were actively rude, did not give you hints when you got stuck, and made you feel unwelcome, that would definitely warrant feedback. Though, as you said, it's too late since it's 2013.
I advise anyone in the future who runs into this kind of situation to contact your recruiter with feedback, and be very clear if you had a bad experience. Amazon takes customer feedback super seriously, and when we interview, the candidates are customers.
I wish I could, but it's been three years so I don't recall specifics.
I do recall the last pair asked me to re-implement a java standard library functionality that was rather complex. It seemed out of place for an interview question.
While there are valid reasons to ask such questions they need to be framed carefully as to indicate why the developer would want to do so. Failing to do that causes frustration because in general the first rule is don't re-implement the standard library.
EX of good question: Facebook has their own COW C++ string with small string optimization because libstdc++ didn't used to have that. It can also provide massive speed improvements on multi-threaded code, what are some ways to implement this?
>While there are valid reasons to ask such questions they need to be framed carefully as to indicate why the developer would want to do so. Failing to do that causes frustration because in general the first rule is don't re-implement the standard library.
Seriously, you're bothered because someone asked you to solve a toy problem? Most interview problems are things one wouldn't do in the real job; that's because all real job problems take more than an hour to solve.
Implementing a stringbuilder is a bad question because there's not much depth to it (after you get the basic implementation down, where do you take the question next?), not because there's a stringbuilder in the stdlib.
> I do recall the last pair asked me to re-implement a java standard library functionality that was rather complex. It seemed out of place for an interview question.
Allow me to respectfully disagree.
Even if they ask you something you or they don't think you can do, it's not just about really solving it but at looking at how you approach such a problem.
No one can really solve important, long term problems in an interview but you sure can reason about them and talk/try toy solutions.
> Ex of bad question: Implement a stringbuilder.
You can always say "I probably wouldn't do this unless I had a good reason but, If i had to roll my own, I'd approach it this way:"
We'll have to agree to disagree. I think implement a string builder is a GREAT interview question.
The point is to have a discussion. Why? What are the benefits of a string builder? When is it necessary? What performance characteristics should it have. What kind of questions do you ask, what kind of edge cases do you consider?
It's an interview - if you are not sure why the interviewer is asking you to re implement a standard library, ASK.
This is not unusual for Amazon - most tech companies these days ask these kinds of questions
We used to ask people to implement standard date-related functions. "That's stupid, all the date functions are already written, and they handle all the weird edge cases for you!" That's right - we want to see if you can think about all the weird edge cases.
It's not about the obvious functions, it's about whether or not you can plan reasonable interfaces and think about edge cases.
To be fair I interview poorly, but I would would have much preferred for the person managing the interviews to cut off the process as soon as they were sure that I wasn't a fit. By failing to do so it just created an awkward and frustrating situation.