Earlier quoted context omitted.
Studying algo/data structure questions is not gaming the system. I'd far prefer to hire someone who did this over someone who didn't prepare and just tried to wing it, then complained about how unfair it is to ask such questions.
Why is that? Besides preparing for understanding the role, culture, etc why would you need someone to brush up on their algo knowledge for your job interview? Do you believe that algo prep would make them better at their job?
Amazon software engineer interview
181–189 of 189 posts
Re: Amazon software engineer interview
#182Earlier quoted context omitted.
Get the book, "Cracking The Coding Interview." It was the most valuable resource for me in preparing for technical interviews near the end of my time in undergrad.
Yes, I bought it last week. But, couldn't answer through the questions because I didn't know the concepts and DS's. Could you answer these 2 questions? 1. Where did you learn how to implement the Data Structures and Algorithms? 2. Also, I'm in a dilemma between using Python and C/C++. Which one would you suggest?
1. Introduction to Algorithms/CLRS (~The~ algorithms book) https://mitpress.mit.edu/books/introduction-algorithms
Also, Skiena's "Algorithm Design Manual" for something a bit lighter.
2. I chose to use Python when possible for technical interviews, as it allowed me to focus more on the algorithms/solution, rather than boilerplate. I rarely use Python in my actual job, but I still prefer it for interviews.
Re: Amazon software engineer interview
#183Earlier quoted context omitted.
Assuming you're serious, there are a number of books out there about working with people with unfortunate personalities. I've generally found those kinds of books more instructive towards my own behavior than books that claim to fix your own personality. Sometimes you need perspective more than instructions. My experience (both first and third-hand) is that being terrible to work/play/exist around often comes from no…
people don't have homogeneous personalities that allow them to neatly fit like bricks into office culture. the natural pressures of any business weed out the dissenters and those that can't quietly work with others or with the decisions being made or [... whatever your problems are ...]. Changing your 'unfortunate personality' (so condescending!) with a book is probably not the answer - you'll change naturally at you…
We can debate neurodiversity and range of personality vs. dysfunction and "unfortunate," but the truth of the matter is some people do things that make them hard to work with and will make them hard to work with in any setting. Some examples might be as simple as interrupting and not letting anyone else speak, or always saying no, or never thanking people and always criticizing, and so forth. If you've never met one of these people then I'm happy for you, but they're not rare in tech. We're all a little mad here, as the old cliche almost goes.
I really have no idea what the OP's issues are that they were asking about--for all I know they think they're terrible to work with because of an inferiority or confidence issue. But my advice stands: get some perspective by reading about other people terrible to work with. Either you'll find out you're not so bad or you'll get the right input to tweak your own behavior.
I appreciate your advice too, but not everyone has to skills or opportunity to "freelance or job-hop" until they find something that works, and the idea that everyone needs to accommodate you while you find the right fit is laughable in the real world. We're not bricks but we're expected to supply our own glue code between us and everyone else, at least to the halfway point, and it's downright narcissistic to expect otherwise. And tight settings like Silicon Valley, you'd be surprised how easy it is to get a reputation as an asshole or team liability while you learn to do that if you're not crisp about it.
For 90% of the people out there, some small tweaks to behavior in order to learn to play the game is the right answer. I'm glad you've apparently found an alternate route to success, but I wouldn't dismiss the typical ways either.
Re: Amazon software engineer interview
#184Earlier quoted context omitted.
what do i do if im a terrible person to work with? its something i really struggle with.
Honestly, the old but still excellent "How to Win Friends and Influence People" by Dale Carnegie changed forever how I interact with people. And, to answer a maybe obvious question, no the book isn't about manipulating people. It's more about dealing quirks of human nature and being excellent at negotiating and interacting with people. Can't recommend it enough if you're honestly looking to improve in that sphere.
Re: Amazon software engineer interview
#185Earlier quoted context omitted.
what do i do if im a terrible person to work with? its something i really struggle with.
Honestly, the old but still excellent "How to Win Friends and Influence People" by Dale Carnegie changed forever how I interact with people. And, to answer a maybe obvious question, no the book isn't about manipulating people. It's more about dealing quirks of human nature and being excellent at negotiating and interacting with people. Can't recommend it enough if you're honestly looking to improve in that sphere.
Re: Amazon software engineer interview
#186Earlier quoted context omitted.
> That's not been my experience. I've seen a strong correlation. Like said, might be culture or maybe I have been lucky. In my country (I haven't lived there for a while so might've changed but I don't think so) and my company we were not so salary obsessed, so 'at the salary you pay me' is a phrase used never in our office of few 100 colleagues. If you make 5 or 9 figures a year; if the boss tells me 'do it cuz i'm…
I don't know if it's a culture thing or not, but if I'm paid low I expect I am being paid to do what I'm told, but if I'm paid high I expect that I am being paid for my expertise, and that includes advising the boss. (It's not about being obsessed with salary.) None of this should be construed as a master/slave relationship. For an analogy, if I go to McDonald's I am not interested in the opinions of the cashier, I j…
Re: Amazon software engineer interview
#187This whole prep for interview testing seems very unpleasant and of questionable value to me. Are these interviews in any way representative of day to day operations in the job you are applying for? I worked as an independent software developer while doing my undergraduate in CS and was very successful just by using fundamentals I learned in courses and then reading and supplementing new things. I then transitioned in…
I don't have a CS degree and don't have a clue when it comes to the "rebalance a red-black tree" stuff. In all of my interviews, this hasn't been an issue -- I can think intelligently about problems and solve them, ask questions, and show correct, well-documented, maintainable code that I've written in the past. I'm good with people and with translating between biz problems and tech solutions.
Even in a large tech city (Boston) with lots of well-funded tech companies, my experience has been FAR from the hell you'd imagine from reading HN. I think a lot of this just comes from the SV bubble overrepresented here. And maybe from the huge crowd of people here who, for various reasons, desperately want to get into one of the big 4.
Those few enormous advertising companies (G, F, A, etc.) represent such a small fraction of the actual work out there, and make so much of the noise, that it's hard to keep an accurate perspective.
Anyway, don't worry about it. It sounds like you'll have an easier time than me, and I've had it surprisingly easy during this whole process.
Re: Amazon software engineer interview
#188This article makes me sad. Interviewing in our industry is so broken. I have been out of school for a while and switch jobs every few years and this is the technique I use to beat the bullshit interview process . Make a list of companies that I would apply to and sort them from most interesting to no-way-in-hell-i-am-working-here order . spend a weak reviewing typical algo/data structure questions . For the companies…
Re: Amazon software engineer interview
#189Earlier quoted context omitted.
I hear the temporary-work evaluation advocated on HN frequently, but this is a viewpoint almost exclusively held by junior developers. Those with families would find it difficult to accept the risk they may be terminated after the eval period. Senior developers aren't going to quit their job on the hope they won't be terminated at the end of the evaluation period. Job searching from scratch takes time and is stressfu…
Agreed to your argument about the temporary-evaluation job being only possible for a junior developer and not to somebody that already has a job. However you should also add to them all the cases of senior developers without jobs (yes, such cases do exist) -- a temporary evaluation job is better than nothing. Senior developers that have jobs won't take the risk of leaving their current job and going to an evaluating…