3 ms·
I recently did interview loops at both Azure and GCP and the difference between the people were astounding. While Google takes way too long to make a hiring de
by VirusNewbie 4y ago
I recently did interview loops at both Azure and GCP and the difference between the people were astounding.
While Google takes way too long to make a hiring decision, all of the people I talked to seemed intelligent and very thoughtful. I did a Microsoft 'hiring event' and holy hell it was a clusterfuck. I got ghosted by one manager, another was extremely disinterested and seemed like they were interviewing me to check a box.
Another asked an algorithmic coding question they themselves did not understand, I had to very politely argue with them, I ended up having to show them step by step how my solution was correct (much to their surprised amazement). The system design interview was done by someone who clearly doesn't understand system design.
I cannot emphasize enough how much their engineering leads came across like a joke compared to other companies. Maybe I just got really unlucky and there are good people who work there, but I'm a bit frightened by what I saw.
- asciimike 4y agoWorked at Google Cloud a while ago and GitHub (Codespaces, which is built on Azure), I couldn't agree more. Google Cloud is so technically and operationally superior, and the average engineer quality was _much_ higher. The obvious downside is that because the bar for GA is so high (because everyone is, or is trying to be, clever), everything lives in beta forever and you can't ship anything on any reasonable scheduke.
- subradios 4y agoGoogle and Azure are both just light-years behind AWS , having worked on and with all three platforms and dealt with engineering staff all the way through. Google doesn't really build things for other engineers, hiding important details of system operation. Azure resources just don't spin up. AWS docs are a byzantine nightmare sometimes, but everything that's in the documentation works exactly as it says it does, and it doesn't go out of its way to go "look over there" when a mode of operation has downstream implications.
- jiggawatts 4y agoFrom what I've seen of Azure as a customer, the quality sucks and it's impossible to convince them to plug gaps no matter how trivial to fix and how obvious. Meanwhile I've had at least one ticket become a permanent fix in AWS almost without asking. However... I just switched back to AWS and it's like stepping back in time from Azure. The AWS Console structure, layout, and organisation is their internal corporate structure. The Azure Portal is designed to reflect your corporate structure, not Microsoft's. With AWS if I have some VMs, associated S3 buckets, and an RDS database, I have to click around a bunch of different web portals to find them all! Unrelated resources are all blended to together into flat lists with gibberish internal system-generated names. It's like clicking through the tables of a SQL database instead of using the actual client application. In Azure, everything is nicely organised into Resource Groups. The VMs, storage, load balancers, databases, etc... all together. Everything is shown with display names instead of IDs, and all their individual consoles are (mostly) consistent. Logs, RBAC, etc... are generally all in the same place and work the same way.
- musk_micropenis 4y ago
- rgblambda 4y ago>I did a Microsoft 'hiring event' and holy hell it was a clusterfuck. Microsoft's recruitment process is notoriously woeful. I wouldn't have believed half the things I've heard only it happened to a friend of mine. The interviewers never showed up to the interview, and terminated his job application when he told them the rescheduled date for the interview wasn't suitable.