I recently got rejected by Amazon Google Verily and some other companies . During the interviews everything looks positive and I finish coding well before time as well mostly . After that I double check with them if it’s fine and they say it’s great or perfectly ok etc .. then I get these rejection emails and they never give any specific feedbacks . I remember for Amazon they asked a question and I started telling solution wrongly and I felt it’s wrong and about to rethink , by that time she told its great go ahead and code . I coded and screwed . Are most interviewers like that
- Indeed dxsiChkIf you converse the same way you type, it’s not surprising that you were rejected 🤷🏻♂️
- Indeed dxsiChk@Apple, I am not in the business of sugar coating. So not trying to be an asshole just providing some honest feedback
@OP, you need to work on your comm skills. Software development is a team sport nowadays so how you converse and how effectively you can get your point across matters a lot.
You are having a hard time expressing yourself and that will not fly on top tech firms. Any amount of leetcoding will not close that gap. Find courses that allows you to improve your conversational skillsMay 145
- Intel minion59Wow, people, you don't have to be so nasty! arch135 asked for feedback to help, not jerky A-hole comments!!
I have noticed alot of that on here lately. Are people just that negative anymore? Maybe it's time to take a look at yourself and your life and do something about it instead of berating others!! YOLO!
- pr~ sounds like a fussy prick. Do you also leave your 3 year old to cross the street unattended to teach him a lesson ?
If it's a coding test, leave the candidate the fuck alone to code and ask him about the code otherwise you'll always find another detail he hasn't addressed "Oh, but does your code cure cancer ? No ? I'm very sorry, you failed. You should have clarified if it's a tree that cures cancer or hiv."
- No, I won't leave 3 year old unattended (though I will see her from distance to let her feel independent) but 12 year old. Same goes with coding question, if yoe is 3, I will be happy to see the code only.
Even for 12 yoe senior swe, I am not asking people to write code for all possible problems in the world but at the same time I expect them to know that there are bigger problems and they are at least aware and know about it.
Acknowledge them, have a solution for that with pros and cons and come back to write the code for base.
- Isn't that what system design is for ? Or at least have follow up discussions about how that algo could be used in practice in a specific area. If you just throw a coding problem and you have a hidden agenda it's just misleading and unfair for the candidate.
Think about this: you use trees for whatever web apps, someone else uses trees for some machine learning algo. You go to the interview and start talking about your use of that concept while the interviewer expects something very different based on his experience. Doesn't make any sense to me.
- Uber 2muchblindOP — If you’d like to work on verbal communication skills, I suggest joining Toastmasters.
For written communication, try reading classical books written in English (like, Charles Dickens, John Steinbeck, etc). I guess you could also take courses a local community college.
I agree with the above posts that at senior levels, communication becomes more and more important.
- @microsoft I’m curious what questions can someone ask on horizontal vs vertical scaling or globalization etc on tree problems. I understand memory constraints hence use bfs instead of DFS but all other doesn’t apply for the question you mentioned ???
- Two Sigma OmfsmInterviewing is a random process. Furthermore the companies you mentioned have an explicit policy to be nice to interviewees.
With more real interviewing (yeah, I think real interviews are far more helpful than mock ones) you'll get a better feel as to evaluating how they went. Do those with companies you don't care about, to get real training. Even then, you don't know much - the interviewer asked the same question multiple times, and calibrated it. You have no idea.
Also, spend time on websites such as hackerrank or codesignal. Doing coding questions really well is more than half the battle.
- Snapchat eeXB43Do mock interviews. You probably have weaknesses and shortcomings that you are not aware of. Get other people’s opinion.
- At your level coding is secondary, design skills, communication skills, thought processes are more important.
Once your recruiter said, no, go ahead with whatever you thought, it was a strong warning. I usually say this when I have already made my mind of no hire.
How do you approach a problem? Do you ask clarification? Do you consider scale, maintainability, once or reusability, memory & cpu constraints, localisation, globalisation, horizontal v/s vertical scaling? I am not saying to implement all of them but mention.
For example, given a question to find the sum of all elements under a subtree, how you will approach it?
If you jump to algorithm with out considering all of the above points mentioned, I will have no hesitation to put no hire even before you start writing any code.
- Amazon / EngDeepObsessPractice discussing technical stuff with your colleagues. At senior levels, professional opinions matter a lot. I think you should work on the ability to have a fun and engaging technical conversation with anyone in your team
- Qualtrics Tommy H moreI had the same experience (Facebook x2, Zillow, WeWork) all seemed to go well but you get no real feedback.
Mock interviews (YouTube videos, podcast etc are good helpers in structuring your answers). Also, it’s pretty subjective at the end of the day.
If you’re interviewing to do a job that you “know how to do” but just at a new company compared to trying a new discipline, you’re most likely going to feel like you did well - because of course you know how to do that job and can solve problems. But it’s also are you better than the other people that apply etc. it’s a simple thing but realizing that was helpful