Amazing developer tooling - you don't know how good it can be until you use it.
Practically infinite resources - There's an internal joke around, "I just want to serve five terabytes" and "I forgot how to count that low."
Everyone isn't a genius; that's overhyped, but everyone's very competent.
Lots of weird corners of the company you can get stuck in.
There are a lot of engineers who find out the company classified them as something else. What's the process to move? Interview like an external candidate! (the dreaded ladder transfer).
This requires permissions that only a few can grant (readability to commit code in a language). Depending on where you are in the company, this will either be extremely easy or take months to do the simplest thing.
Transfers require good performance reviews, which means everyone moves along until they land in something that doesn't fit their skills, at which point they can never leave. There's no bad fit, just bad employees.
Look, I know I'm pretty clearly a single-issue complainer, but it really is awful if you fall through the cracks.
Make transferring easier; lots of people are stuck in weird spots. Don't look at your written policy around this and mistake it for what actually happens. The real rules are much more frustrating.
Figure out a different way to manage the Business/Engineering conflict. There's a constant tug-of-war where Engineering doesn't want to be told what to do, and Business really, really wants to be able to tell them what to do. There have been a few back-and-forths where GBO hires a bunch of warm bodies they can micromanage for their purposes, then that loophole is changed, and they can't do that anymore, so they find another one.
I get it! They have things they need. But the solution is for a mature relationship where all of Eng does what Business wants some of the time, rather than have most doing it none of the time and a few trapped doing nothing but that. I did maybe three net months of work in two years; all the rest was spent undoing and redoing things because of high-level flailing. Did you get your money's worth from my salary and benefits? No way. Did my manager get promoted? You bet.
I had a phone screen, followed by several rounds of onsite interviews. Some of the technical phone screen questions were copied from the internet, with one question being poorly described and unsolvable. While some of the onsite interviews went smoo
Batch Day. If you survive the first three interviews in the morning, you might be invited back in the afternoon if you are "cool" enough. You had to prepare a demo in the Google Cloud Platform, which I did. After three weeks, they shut down my accou
Very competent interviewers. Be sure you know the "tricky" algorithms and "big O". A very positive, though unsuccessful, process.
I had a phone screen, followed by several rounds of onsite interviews. Some of the technical phone screen questions were copied from the internet, with one question being poorly described and unsolvable. While some of the onsite interviews went smoo
Batch Day. If you survive the first three interviews in the morning, you might be invited back in the afternoon if you are "cool" enough. You had to prepare a demo in the Google Cloud Platform, which I did. After three weeks, they shut down my accou
Very competent interviewers. Be sure you know the "tricky" algorithms and "big O". A very positive, though unsuccessful, process.