Google Interview Questions
-
Why Google, Amazon etc such companies technical interview questions are like this 1) kth largest element in array 2) Find minimum number of steps to reach the end of array from start (array value shows how much you can move). 3) Median of stream of numbers 4) Question like pancake sorting where you can only swap to sort an array of characters. This questions are asked for a person with 4 years experience. Mostly,these are not real world problems in projects. This are only for testing problem solving skills. Other companies give preference to working experience and project experience etc. Why Google is different?
-
Why Google, Amazon etc such companies technical interview questions are like this 1) kth largest element in array 2) Find minimum number of steps to reach the end of array from start (array value shows how much you can move). 3) Median of stream of numbers 4) Question like pancake sorting where you can only swap to sort an array of characters. This questions are asked for a person with 4 years experience. Mostly,these are not real world problems in projects. This are only for testing problem solving skills. Other companies give preference to working experience and project experience etc. Why Google is different?
Because Google already know everything about you, and are only going through the motions of an interview so you won't realize...:~
You looking for sympathy? You'll find it in the dictionary, between sympathomimetic and sympatric (Page 1788, if it helps)
-
Why Google, Amazon etc such companies technical interview questions are like this 1) kth largest element in array 2) Find minimum number of steps to reach the end of array from start (array value shows how much you can move). 3) Median of stream of numbers 4) Question like pancake sorting where you can only swap to sort an array of characters. This questions are asked for a person with 4 years experience. Mostly,these are not real world problems in projects. This are only for testing problem solving skills. Other companies give preference to working experience and project experience etc. Why Google is different?
Because Google is different. They're not just gluing "Boring Business Thingamajig 3.1415", "Overhyped Web Fad 2.45" and "Newest non-SOLID Database Nonsense" together with some extra existing components to form some Rube-Goldberg Machine / Frankenstein Monster the way most companies are doing.
-
Why Google, Amazon etc such companies technical interview questions are like this 1) kth largest element in array 2) Find minimum number of steps to reach the end of array from start (array value shows how much you can move). 3) Median of stream of numbers 4) Question like pancake sorting where you can only swap to sort an array of characters. This questions are asked for a person with 4 years experience. Mostly,these are not real world problems in projects. This are only for testing problem solving skills. Other companies give preference to working experience and project experience etc. Why Google is different?
-
Why Google, Amazon etc such companies technical interview questions are like this 1) kth largest element in array 2) Find minimum number of steps to reach the end of array from start (array value shows how much you can move). 3) Median of stream of numbers 4) Question like pancake sorting where you can only swap to sort an array of characters. This questions are asked for a person with 4 years experience. Mostly,these are not real world problems in projects. This are only for testing problem solving skills. Other companies give preference to working experience and project experience etc. Why Google is different?
pandu web dev wrote:
This questions are asked for a person with 4 years experience.
There are quite some people out there that have more than four years experience and still haven't learned to program.
pandu web dev wrote:
Mostly,these are not real world problems in projects.
"Real world problems"? Sorry, but IT uses a lot of abstract examples, we cannot provide an "real world example" for each problem.
pandu web dev wrote:
Other companies give preference to working experience and project experience etc.
It does not say they don't - but larger companies get more applications, and it costs time and money to evaluate those. Hence it's a good idea to have some sort of pre-selection. Adding a programming-task so the applicant can "prove" they can actually think is a good idea.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
Why Google, Amazon etc such companies technical interview questions are like this 1) kth largest element in array 2) Find minimum number of steps to reach the end of array from start (array value shows how much you can move). 3) Median of stream of numbers 4) Question like pancake sorting where you can only swap to sort an array of characters. This questions are asked for a person with 4 years experience. Mostly,these are not real world problems in projects. This are only for testing problem solving skills. Other companies give preference to working experience and project experience etc. Why Google is different?
pandu web dev wrote:
Other companies give preference to working experience and project experience etc.
No they don't. Companies I've interviewed for don't even know I've been a Microsoft MVP or a current CP MVP or that I've written 167 articles. They ask me the same stupid questions. Stupider, actually, if you can believe it. Marc
Automating Semantic Mapping of a Document With Natural Language Processing
-
Because companies like Google value the ability to solve problems where some other companies are happy if the bottom feeders working for them are capable of keeping their drool from saturating the keyboards.
Pete O'Hanlon wrote:
keeping their drool from saturating the keyboards
I'm trying, I really do, but some days it's just really very hard! Excuse me while I go wash my hands now...
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
} -
Why Google, Amazon etc such companies technical interview questions are like this 1) kth largest element in array 2) Find minimum number of steps to reach the end of array from start (array value shows how much you can move). 3) Median of stream of numbers 4) Question like pancake sorting where you can only swap to sort an array of characters. This questions are asked for a person with 4 years experience. Mostly,these are not real world problems in projects. This are only for testing problem solving skills. Other companies give preference to working experience and project experience etc. Why Google is different?
pandu web dev wrote:
Why Google is different?
Abstract and real life problem solving skills are more important to them, then your ability to perform string manipulation or your ability to solve towers of Hanoi puzzle. I have read that you can have 7 to 11 interviews before you can get picked for an Engineer position with Google. The first couple of interviews weed out the ones that can't code. The rest of the interviews are about you as a person and your "approach" to solving problems, not necessarily getting the answer correct. Some of their problems have no correct answer.
-
Why Google, Amazon etc such companies technical interview questions are like this 1) kth largest element in array 2) Find minimum number of steps to reach the end of array from start (array value shows how much you can move). 3) Median of stream of numbers 4) Question like pancake sorting where you can only swap to sort an array of characters. This questions are asked for a person with 4 years experience. Mostly,these are not real world problems in projects. This are only for testing problem solving skills. Other companies give preference to working experience and project experience etc. Why Google is different?
Because experience means very little and 'problem solving skills' are extremely important. Some of these questions are a bit too artificial for my liking but the idea of seeing how a candidate can solve a problem in a constrained environment is a good one. My company gives interviewees a fairly simple programming problem to solve, though it's a bit more real world than this as it's for about half a day, and apparently it filters out a lot of people who've made themselves look good on their CV and sound convincing but can't actually solve problems.
