Google Can't Google?
Last year Google tried to convince me to join their ranks. I had a nice trip to Mountain View, a pleasant day of interviews, and a glimpse inside of their campus. All pretty cool. I ended up shutting down the process between the "we really want to hire you" …
Context & Ripple Effects
In December 2005 the San Francisco Chronicle profiled how Google woos the best and brightest (How Google woos the best and brightest), and the Washington Post was already dissecting the company's outsized cultural pull (Googling Google). At that point Google's recruiting machine was treated as an asset in itself — a brand so strong that candidates competed to get in.
This post is the counter-story from inside the funnel: the author describes a flown-out Mountain View visit, a full day of interviews and a campus tour, then walking away himself between Google's 'we really want to hire you' stage and an actual offer. That a senior technologist would publicly document opting out — while Google is simultaneously announcing a $100 million Feedburner deal and defending its Dell preinstalled-software partnership against spyware criticism — matters because the recruiting halo and the operating reality were starting to diverge in public.
First-order effects
- Google absorbs the full cost of a courting cycle — travel, a day of interviewer time across campus, executive attention — and still loses the candidate, a direct yield leak at the most expensive stage of its pipeline.
- A first-person account of stalling out after the 'we really want to hire you' stage enters the public record, giving every rival competing for the same senior engineers a ready-made counter-recruiting narrative.
Second-order effects
- Competing employers gain a concrete talking point — 'we decide faster' — aimed directly at candidates Google has already softened up, forcing Google's recruiters to defend process speed rather than just sell prestige.
- As the blog post circulates, Google's interviewer corps faces implicit pressure to shorten loops and commit earlier, trading some of the consensus-driven thoroughness that made the process feel rigorous.
Third-order effects
- If late-stage walkaways become a pattern, employer brand flips from a moat into contested territory: the same blogosphere that amplified Google's mystique in 2005 can just as efficiently amplify its friction, making hiring process itself a competitive battleground among large tech companies.
- Sustained pressure on the interview gauntlet points toward structural change in how big-company technical hiring is run — fewer open-ended loops, faster decisions — though whether one anecdote signals a systemic problem or one mismatched candidate is genuinely unclear from this account alone.
The trend: Technical hiring is becoming a public contest over process quality, where candidates' firsthand accounts — not just compensation — shape which company wins senior engineers.