After the second time of having some Google product be cancelled, I vowed never to use any of their services ( apart from search ) in a commercial setup. My first question for any AWS/Azure service being considered in my organization is "When is it going to be EOL'ed?".
I've worked at a couple organisations where there was a mantra of 'No HR'. In all cases I saw mistakes and abuses that would / should have been picked up by a sensible HR person. I don't buy it. Granted you don't need entire departments of people but when you get to be a billion-pound company, there will be a need for some expertise.
It feels very unfinished. The "home" page and "dashboard" page don't display anything for me. I like the concept but it's looking very beta, or pre-beta.
Everythng that's repetitious and error-prone: Manual migrations of old physical servers, disaster-recovery, managing legacy infrastructure. Luckily, most of these have been obviated by the cloud, thank god. I became a sysadmin to work on interesting projects, not to endlessly reset AD user credentials. Granted there is a level of repetition in any job, but when the process becomes to the job, it's time to automate.
I interviewed at one place where the manager who was supposed to see me turned up an hour late, sweaty from a cycle ride and said I was too early. He consistently got my name wrong during the remaining half hour, and poured scorn on his current reports.
- If during the interview, they ask you if you have 'firing skills' and how you motivate unmotivated staff, that's a strong indicator also. The company was based 20 seconds from the edge of a airport runway. Repeatedly during the interview, we had to stop talking as the noise from jet engines wouldn't allow normal conversation.
Going with Google is too risky these days.