N.B.: My use case is batch jobs that have a significant amount of output bytes, so I don't care about the "quality" of the bandwidth.
And for those who aren't aware, Google is charging about two orders of magnitude more than market rates for Internet egress.
In Europe their pricing is even less competitive.
It's insane how much they charge for bandwidth and it severely limits the usefulness of the service.
I guess that might be the point though. If egress is expensive, you're encouraged to keep everything inside GCP.
Can you share exactly what you do on GCE?
I used to work on Compute Engine itself. I led the team that built and launched Preemptible VMs, and I still participate in its upkeep / improvements. So I generally still write little bits of code that nobody else wants to (especially monitoring and other cleanup type work).
About a year ago we started an Office of the CTO with me as the first "hire". So I transitioned from building new things and writing code much of the time (Note: Many at Google will snicker at this, as I am routinely teased for being a pseudo-PM) to talking to high-profile customers most of the time (think CTO / VP Eng types). We usually talk through where they are, what challenges they have, and whether or not GCP can actually fulfill their needs today (and as my group focuses on candor, we certainly say "You shouldn't migrate to us until we do X, Y, and Z, or you rewrite Foo").
I just hang out on HN as I like the dialogue :).
You folks should really have a utility on the default images (maybe call it `seppuku` or `dienow`) which sends an "o" to /proc/sysrq-trigger; using that has allowed me to time shutdowns to within a couple seconds at worst (though there is an unfortunate discrepancy between the account logs, which show the accurate node shutdown time, and the instance logs, which only show it a few seconds later).
Might you have a link for this role? Do you have a way to get in touch? I didn't see any details in your profile.
The email you're looking for is etally@
https://careers.google.com/jobs#!t=jo&jid=/google/solutions-...
[EDIT] According to another Googler in this thread, the address is actually [email protected].
My team is composed of a mix of Google engineers that can (kind of) talk to people, and recovering CXO types from various industries (Finance, Healthcare, etc.). Each of us try to only work deeply with 1-3 customers at once, while SAs are usually focused on more broadly applicable solutions.
We all weave in and out depending on personal relationships with customers and individual skill sets, but we're all behind trying to make our customers successful regardless of role or title.
- Skylake is now generally available
- Broadwell is now globally visible
- "Extended Memory" custom machine types are now in Beta
I decided to focus on Skylake as GA for the title, but depending on your interest these other announcements may be good to know as well. In particular, this changes the historical "us-central1-a is the oldest zone" into "us-central1-a is a better choice than 1-f".
Disclaimer: I work on Google Cloud (and want to sell you cores)
[Edited: I always forget newlines]