Slashdot Mirror
Want a Job At Google? Better Know Microsoft Office!
theodp writes "After recent Slashdot discussions on Google's quest to unseat Microsoft Office in business and whether Google Docs and MS-Word are an even matchup, let's complete the trilogy by bringing up the inconvenient truth that numerous Google job postings state that candidates with Microsoft Office expertise are 'preferred' to those lacking these skills. 'For example,' notes GeekWire, 'when hiring an executive compensation analyst to support Google's board, the company will give preference to candidates who are 'proficient with Microsoft Excel."' Parents and kids at schools that have gone or are going Google are reassured that, 'it is more important to teach technology skills than specific programs' and that 'Google itself uses Google Apps to run its multi-billion dollar company.' Which, for the most part, is true. Just don't count on getting certain Google jobs with that attitude, kids!"
trol?
Is this a serious Google branding issue? I can kinda understand the confusion, just as I can the whole "Google Voice is trying to compete with Vonage!" crap - that's a voicemail and forwarding service on steriods service people, not a VoIP service (Google Talk is the VoIP service.) Though that said, if you don't actually use a product enough to know what it is, why mention it?
You are not alone. This is not normal. None of this is normal.
The company I work for uses Google Docs extensively; in fact, we use it so much I wrote SAS scripts to interface with the API so we can easily share datasets in and out of Google Docs. While it's powerful for collaborative work over the Internet, especially with remote resources housed all over the world, it's no replacement for Office.
It doesn't have all the powerful tools Office does, it doesn't format documents the same as Office does (especially importing and exporting--and yes, I realize Office doesn't do all that well version to version), and it doesn't work all that well offline (if at all).
So it's no wonder a corporation dealing with other corporations would require Office knowledge. This is a non-story.
Google can push their own platform all they want internally, but they can't control the format of documents they receive. I've resorted to installing LibreOffice on my personal system to edit/collaborate/modify Office documents before sending them back. Doesn't work so well in Google Docs.
As opposed to a employee relations person, you understand.
The weasels want people with 5 years experience with Java in 1995, and then wonder why no-one but James Gosling applies.
Send the posting to Larry Page's office with a subject line like "Public relations blunder".
--dave
davecb@spamcop.net
Which is fine, until a client sends you a document from MS Office and wants you to send back your changes with change tracking turned on, so that they can see what has changed in the document. If you only use it for internal documents, Google Docs can be fine. However, once you want to communicate with the outside world, you had better have MS office, or things will break down quite quickly.
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
Ever heard of LibreOffice? If you claim you're unable to write "powerful macros" in any of these languages, then it is you who is the "idiot".
I don't think the problem is so much writing new Macros, but in rewriting all of the tried-and-true macros and formulas that the Finance exec has been using for the past decade. Sure, it could be ported and rewritten, but why have a $100/hour finance professional spend time learning a new macro language and rewriting and validating his old functions/macros for a new spreadsheet platform? It only takes a few hours of wasted work to pay for MS Office.
Competent programming teams will look at MS word on your resume and go,"If this guy thinks Office is something special, he must not know a lot."
Corporate HR on the other hand might have struggled to learn MS Office as it is one of the few applications they ever used. They think putting MS Office on a resume is a badge of honor. So if you don't put MS Word on your resume in some corporate places, they think you're not cut out for the job."What this guy doesn't know Office? He must not know much."
This has bugged me for many years as I have a hard time getting interviews. If someone is a programmer, it should be assumed they know how to use most every piece of software they come into contact with. Yet, a lot of HR departments don't get it. It is hard to tell who is competent and who isn't, so the question you ask is,"Do I put the Microsoft Office on my resume?" I've come to the conclusion,"I don't want to be hired by an incompetent organization, so I'll just leave the Microsoft Office off my resume."
God spoke to me
Sure, it could be ported and rewritten, but why have a $100/hour finance professional spend time learning a new macro language and rewriting and validating his old functions/macros for a new spreadsheet platform?
That's why you hire on some bright kid off the street for $10/hour part time to port it to the new macro language.
In a few hours, you have your ported macros, and you only need the newer shinier spreadsheet program.
And the $100/hour finance guy still has to validate the work and ensure that it's working as expected - he's not going to present numbers to the board of directors based on what some $10/hour kid did. And it's going to take more than "A few hours" - you'd be surprised at some of the corporate finance spreadsheets out there - some are pages upon pages of linked numbers with obscure calculations that have been refined over time. And when he wants to tweak it, he either needs to hire a new $10/hour kid to do the work, or sit down and learn the new system.
Your argument sounds kind of like the CIO that says "Hey, I've been reading a lot about dotNet and I think we ought to port our code over from Java to dotNet - we just need to hire a few $10/hour coders to do it, right? Then we'll be running on this shiny new platform, despite the fact that it was running fine before." The actual coding itself is a small part of the overall project - architecture, design and validation are all much harder.