4 ms·

How do you explain that to companies that follow the Google interviewing model?

by modarts 10y ago

fredophile 10y ago
What do you mean by "Google interviewing model"? Are you suggesting that this is a problem at Google and companies that interview the way it does?
- ghgfhgfhn 10y ago
  I think he means: The Google culture is built around cerebral competition. The drive to dominate ones peers, possessed by many technical types, is used to create a fiercely competitive atmosphere. This competition is used to drive productivity. The trouble with this is that it is difficult to measure code quality but easy to measure how quickly the code is produced. Thus within highly competitive environments code tends to be produced as quickly as possible, rather than as well as possible. Of course this is debatable and if true, is only a tendency...
- ForHackernews 10y ago
  A "dead" (or shadowbanned?) user replied to you: << ghgfhgfhn 26 minutes ago [dead] [-] I think he means: The Google culture is built around cerebral competition. The drive to dominate ones peers, possessed by many technical types, is used to create a fiercely competitive atmosphere. This competition is used to drive productivity. The trouble with this is that it is difficult to measure code quality but easy to measure how quickly the code is produced. Thus within highly competitive environments code tends to be produced as quickly as possible, rather than as well as possible. Of course this is debatable and if true, is only a tendency...>>
  - sctb 10y ago
    If a dead comment appears in a thread, users with vouching privileges and 'showdead' turned on in their profile can vouch for it to make it visible if they believe it to be substantive. Please do this instead of reposting.
    - ForHackernews 10y ago
      What are "vouching privileges" and how might one vouch for it?
      - sctb 10y ago
        At least 31 karma are required, and a link that says 'vouch' will appear on a dead post.
        ForHackernews 10y ago
        Huh. I have about 7k karma, and I don't think I've ever seen that link. Is it a new feature?
        deleted 10y ago
        [deleted]
deleted 10y ago
[deleted]
jondubois 10y ago
I think a lot of times during such interviews, they're more interested in seeing how you approach problems rather than the actual solutions that you provide (at least that's what good companies will tell you). I haven't worked at Google but I have worked in both startups and big corporations and I find that big corporations are usually slower-paced and engineers have more 'generous timeframes' to complete features (and to do them properly). The downside of the big company/corporation approach though is that managers tend to use the extra time to create bureaucracy around the project (in an attempt to manage risk) and this slows things down further - So while big companies tend to 'get it right the first time'; they do so at a significantly slower pace than what you would see in a startup.

How do you explain that to companies that follow the Google interviewing model?

by modarts 10y ago

How do you explain that to companies that follow the Google interviewing model?

What do you mean by "Google interviewing model"? Are you suggesting that this is a problem at Google and companies that interview the way it does?

ghgfhgfhn 10y ago
I think he means: The Google culture is built around cerebral competition. The drive to dominate ones peers, possessed by many technical types, is used to create a fiercely competitive atmosphere. This competition is used to drive productivity. The trouble with this is that it is difficult to measure code quality but easy to measure how quickly the code is produced. Thus within highly competitive environments code tends to be produced as quickly as possible, rather than as well as possible. Of course this is debatable and if true, is only a tendency...
ForHackernews 10y ago
A "dead" (or shadowbanned?) user replied to you: << ghgfhgfhn 26 minutes ago [dead] [-] I think he means: The Google culture is built around cerebral competition. The drive to dominate ones peers, possessed by many technical types, is used to create a fiercely competitive atmosphere. This competition is used to drive productivity. The trouble with this is that it is difficult to measure code quality but easy to measure how quickly the code is produced. Thus within highly competitive environments code tends to be produced as quickly as possible, rather than as well as possible. Of course this is debatable and if true, is only a tendency...>>
- sctb 10y ago
  If a dead comment appears in a thread, users with vouching privileges and 'showdead' turned on in their profile can vouch for it to make it visible if they believe it to be substantive. Please do this instead of reposting.
  - ForHackernews 10y ago
    What are "vouching privileges" and how might one vouch for it?
    - sctb 10y ago
      At least 31 karma are required, and a link that says 'vouch' will appear on a dead post.
      - ForHackernews 10y ago
        Huh. I have about 7k karma, and I don't think I've ever seen that link. Is it a new feature?
      - deleted 10y ago
        [deleted]

deleted 10y ago

[deleted]

jondubois 10y ago

I think a lot of times during such interviews, they're more interested in seeing how you approach problems rather than the actual solutions that you provide (at least that's what good companies will tell you). I haven't worked at Google but I have worked in both startups and big corporations and I find that big corporations are usually slower-paced and engineers have more 'generous timeframes' to complete features (and to do them properly). The downside of the big company/corporation approach though is that managers tend to use the extra time to create bureaucracy around the project (in an attempt to manage risk) and this slows things down further - So while big companies tend to 'get it right the first time'; they do so at a significantly slower pace than what you would see in a startup.