That's a big ask Googles software requires a different mind set than say correctly calculating veterans pensions.
From googles perspective having 2 or 3% suboptimal query's is fine but that wont pass muster for other types of work.
Try building billing systems for a global Telco and have one of Vint Cerfs reports nudge you and say this had be right otherwise we are both out of a job :-)
A google query? What does it even mean for a google query to be "100% right"? I'm not sure that's even a thing.
But I think you misunderstand software engineering and the nature of engineering skill or fields of experience. There may be no such thing as "100% right" when it comes to which hits are included in the result set for a google query, but I have no doubt that nearly any google engineer needs to write all sorts of code on a regular basis that indeed needs to be 100% right with regard to specifications or requirements.
Googles code quality isn't all its cracked up to be and you have a least heard of OSI? You know the other networking standard that was at least a decade ahead of the internet back then.
Okay, that's cool, if you want to talk on the internet about how you're obviously a better programmer than anyone that works at Google becuase you worked on an ancient over-engineered standard that basically ended up losing out to TCP/IP... who am I to stop you?
Calculating a pension and building a billing system is rather basic CRUD work compared to scaling software to handle millions of concurrent users. Google's hiring bar is relatively high compared to any government position in terms of quantitative skills you'd need to demonstrate.
From googles perspective having 2 or 3% suboptimal query's is fine but that wont pass muster for other types of work.
Try building billing systems for a global Telco and have one of Vint Cerfs reports nudge you and say this had be right otherwise we are both out of a job :-)