47 ms·

This is a royal fuck up. Anyone using any g cloud service better be suspect when using their services. Amazing how some folks can't get a job at google if they

This is a royal fuck up. Anyone using any g cloud service better be suspect when using their services. Amazing how some folks can't get a job at google if they can't invert a binary tree. Perhaps hire folks with relevant skills rather than folks who can solve 2 leetcode mediums in under 45 mins?

GoToRO 3y ago
Oh, you think developers still have that kind of power... Management has made sure to not allow any developer to have any kind of power. Not even naming their own variable the way they want it. All big and small decisions are taken by managers that don't even understand coding. They are the ones that push for hard deadlines and then loose months deciding what to do next for example. The crappy software trend has been rising at the same pace with the stripping of power from developers.
refulgentis 3y ago
That's not actually how it works, that's an ollllld viral article. Source: worked at google for 7 years, 2.8 gpa dropout from state school economics EDIT: upvotes for reality-detached rant, upvotes for "you think you are The One" -2 for a polite concise reality.
- game_the0ry 3y ago
  My friend, don’t take this the wrong way, but you need to hear this. It would benefit you to take the downvotes as constructive criticism. You opinions may need recalibration based on feedback.
compiler-guy 3y ago
This comment smells very much like you think you are The One. Or that The One is out there somewhere [1]. Bugs happen and this is a serious failure that Google needs to fix. But the idea that incompetents are doing the development or that Google hires puzzle solvers over technical talent is just not true. 1. https://rachelbythebay.com/w/2018/12/21/env/ https://rachelbythebay.com/w/2018/12/21/env/
- game_the0ry 3y ago
  > ...that Google hires puzzle solvers over technical talent is just not true. Yeah, they do: https://twitter.com/mxcl/status/608682016205344768?lang=en https://twitter.com/mxcl/status/608682016205344768?lang=en
  - compiler-guy 3y ago
    I’m quite familiar with that story. Google doesn’t disclose to candidates why they were rejected. I didn’t interview him so have no insights, but ability to get along with others still matters. But even if he was rejected for the reasons he thinks he was, one story does not reveal how the tens of thousands of interviews Google conducts each year actually go and how hiring decisions are made. I have been a part of hundreds of hiring decisions at Google, and there is much to hate about the process. But leetcode over qualifications is not one of them.
    - game_the0ry 3y ago
      > ...there is much to hate about the process. That's a signal that's trying to tell you something. > But leetcode over qualifications is not one of them. A lot of people hate leetcode and the state of interviews at tech companies (17k people liked that tweet), but it looks like you do not. Tech is probably the only field where you have to study unrelated subject matter than the job you actually end up doing. > I have been a part of hundreds of hiring decisions at Google I am curious - I heard that Google is getting rid of its team matching process[1] : > The rationale is current system outputs a lot of false positive and false negative. The rumor was that google would do "generalist" (read that to "leetcode") style interviews and then put the candidate in a team matching process, where teams would review the candidate's (who ostensibly got an offer) package, and decide whether or not to bring them on the team. But then a lot of candidates would get stuck in the team matching phase bc they couldn't find a team to take them on. Machine learning engineers would be presented to teams that needed front end UI devs, which were clearly a mismatch. Basically, the generalist interview was creating a pool of candidates that passed the generic leetcode interview, but they producing poor matches for what teams at google really needed. Is that true? [1] https://www.teamblind.com/post/Google-just-got-easier-no-more-team-matching-HdQW00nw https://www.teamblind.com/post/Google-just-got-easier-no-mor...
deleted 3y ago
[deleted]

GoToRO 3y ago

Oh, you think developers still have that kind of power... Management has made sure to not allow any developer to have any kind of power. Not even naming their own variable the way they want it. All big and small decisions are taken by managers that don't even understand coding. They are the ones that push for hard deadlines and then loose months deciding what to do next for example. The crappy software trend has been rising at the same pace with the stripping of power from developers.

refulgentis 3y ago

That's not actually how it works, that's an ollllld viral article. Source: worked at google for 7 years, 2.8 gpa dropout from state school economics EDIT: upvotes for reality-detached rant, upvotes for "you think you are The One" -2 for a polite concise reality.

game_the0ry 3y ago
My friend, don’t take this the wrong way, but you need to hear this. It would benefit you to take the downvotes as constructive criticism. You opinions may need recalibration based on feedback.

compiler-guy 3y ago

This comment smells very much like you think you are The One. Or that The One is out there somewhere [1]. Bugs happen and this is a serious failure that Google needs to fix. But the idea that incompetents are doing the development or that Google hires puzzle solvers over technical talent is just not true. 1. https://rachelbythebay.com/w/2018/12/21/env/ https://rachelbythebay.com/w/2018/12/21/env/

game_the0ry 3y ago
> ...that Google hires puzzle solvers over technical talent is just not true. Yeah, they do: https://twitter.com/mxcl/status/608682016205344768?lang=en https://twitter.com/mxcl/status/608682016205344768?lang=en
- compiler-guy 3y ago
  I’m quite familiar with that story. Google doesn’t disclose to candidates why they were rejected. I didn’t interview him so have no insights, but ability to get along with others still matters. But even if he was rejected for the reasons he thinks he was, one story does not reveal how the tens of thousands of interviews Google conducts each year actually go and how hiring decisions are made. I have been a part of hundreds of hiring decisions at Google, and there is much to hate about the process. But leetcode over qualifications is not one of them.
  - game_the0ry 3y ago
    > ...there is much to hate about the process. That's a signal that's trying to tell you something. > But leetcode over qualifications is not one of them. A lot of people hate leetcode and the state of interviews at tech companies (17k people liked that tweet), but it looks like you do not. Tech is probably the only field where you have to study unrelated subject matter than the job you actually end up doing. > I have been a part of hundreds of hiring decisions at Google I am curious - I heard that Google is getting rid of its team matching process[1] : > The rationale is current system outputs a lot of false positive and false negative. The rumor was that google would do "generalist" (read that to "leetcode") style interviews and then put the candidate in a team matching process, where teams would review the candidate's (who ostensibly got an offer) package, and decide whether or not to bring them on the team. But then a lot of candidates would get stuck in the team matching phase bc they couldn't find a team to take them on. Machine learning engineers would be presented to teams that needed front end UI devs, which were clearly a mismatch. Basically, the generalist interview was creating a pool of candidates that passed the generic leetcode interview, but they producing poor matches for what teams at google really needed. Is that true? [1] https://www.teamblind.com/post/Google-just-got-easier-no-more-team-matching-HdQW00nw https://www.teamblind.com/post/Google-just-got-easier-no-mor...

deleted 3y ago

[deleted]