131–140 of 335 posts
Earlier quoted context omitted.
I was pointing to growth, not revenue. A business that doubled its revenue in two years is great to have, even if it is not currently profitable.
So if I sell $1 bills for $0.90, I guess I should be glad if my “revenues grow”?
Earlier quoted context omitted.
So...it's kind of like being Big Head working at Hooli? Hanging out on the roof, or building potato guns and piezoelectric sensors?
Lots of networking over coffee. You don't just blindly apply on the internal job board. You talk to people you know in other parts of the company, you schedule meetings with managers with open roles. You reflect on what you actually want to do next. You reach out to mentors on if they know anyone who has interesting open roles or just on advice for next steps. Also interviewing with other companies. The next best job…
Earlier quoted context omitted.
Not just that. Google simply doesn't have it in their DNA to deliver the kind of high-touch support required of remaining #1 in this business. They've been hiring the pushy sales types to deliver one end of it but not the delivery people required on the other.
Not to mention that Google is so full of “smart people” (tm) that their sales force is made up of people who probably would never stoop low enough to do lift and shifts as phase 1. They would probably want you to move everything to k8s and rewrite your entire stack. As opposed to MS. If a business has a legacy app that requires a 10 year old version of Sql Server running on a 12 year old version of Windows, they will…
They push you to use a Beta feature as it's the "preferred" way of interacting with their internal APIs. Meanwhile they know definitively that there's a race condition in their code when using this feature that will _take down the entire service_. It took down our entire Production project, they weren't forthcoming with any information to get us a fix for several hours (until we started sending nasty escalation emails about our P1 ticket not being handled) and then they blamed us for using a feature that was still in Beta.
We'd had literal face to face meetings where they'd told us we need to use this feature.
Interestingly enough, we were assigned new reps this week. I wonder if our AM and TAM were laid off.
Earlier quoted context omitted.
Lots of networking over coffee. You don't just blindly apply on the internal job board. You talk to people you know in other parts of the company, you schedule meetings with managers with open roles. You reflect on what you actually want to do next. You reach out to mentors on if they know anyone who has interesting open roles or just on advice for next steps. Also interviewing with other companies. The next best job…
Do they have you whiteboard asinine college CS algo problems in the internal version?
Earlier quoted context omitted.
So if I sell $1 bills for $0.90, I guess I should be glad if my “revenues grow”?
In logic class we called that a red herring fallacy. Google Cloud isn't in the business of selling $1 bills for 90 cents.
Earlier quoted context omitted.
So if I sell $1 bills for $0.90, I guess I should be glad if my “revenues grow”?
If you expect to be able to acquire $1 bills for $0.80 in the future, then yes.
Earlier quoted context omitted.
So if I sell $1 bills for $0.90, I guess I should be glad if my “revenues grow”?
There's a difference between selling something with a fixed cost (and a fixed value) for a fixed price and selling something which has unknown (and variable) value for a fixed price.
Earlier quoted context omitted.
Do they have you whiteboard asinine college CS algo problems in the internal version?
Entirely dependent on the team and hiring manager. And the technical requirements of the role you want to move into versus your prior role. If you want to move from working on gmail to working on the android kernel, I imagine there's gonna be some whiteboarding. (Not that gmail is simple software, but just picked two examples that came to mind with different domain expertise).
Nothing is happening to Google Cloud overall. This is just a small org where two teams were doing similar stuff, so they got merged. This made a few roles redundant, so those folks will be looking for new roles within Google (Cloud). How this made for a WSJ headline, IDK. I couldn't read the whole article because paywall, but the first few lines do mention that it's a tiny number of employees affected and they can lo…
It isn’t a good look.
“This morning I learned that my role at Google has been eliminated. If you've got an opening for someone who's in Kubernetes and containers security, focuses on content, advocacy, and communication, and has an OSS background, holler!”