Earlier quoted context omitted.
We hired a former Googler recently, great hire. Your resume couldn’t be more different from his: yours is so generic that my only takeaway is “oh he worked at Google”. I fear you’ve taken resume advice along the lines of “…explain the value of what you did…” (which is great advice) but should be used to augment technology experience, not replace it. I have no idea what you’re good at. Find some former Google colleagu…
> but should be used to augment technology experience, not replace it. Do you have some specific feedback or bullets that stand out to you? Most of Google tech is all in-house stuff that nobody would recognize, outside of a few open-source counterparts (Blaze -> Bazel). I'm confused how my resume could better convey what I'm good at. I can say I worked with Java, Angular, Typescript, etc. But that's all exceedingly g…
If you look at the type of work being done at “normal” companies you’re applying for, you’ll likely see work that is much more at the coal face and so experience at the coal face is worth much more than work that most people can’t even conceptualise — even if it happened at Google.
In a competitive hiring environment, you need your resume to tell the person reviewing it why you’re a safe bet. Your resume tells me that if I need someone to build internal full stack web-app automation then you’ve got experience of doing that at Google… which is great except Google is pretty much the only place where that work is required.
Don’t think of your experience as a list of things you’ve done, think of it as evidence for why you’re the right candidate to fill a role. If you’re applying for a company that has an internal customer support system then absolutely shout about how you did exactly that at Google, it’ll get you an interview… if you’re applying for a company that builds AR furniture previewing for e-commerce, it’s probably not worth even mentioning.
The perfect resume is a copy-and-paste of the job spec, you need to get as close to that as is possible. If you did a random weekend project at Google that can be framed as relevant to the job you’re applying for, that will do more for you than the hundreds of engineering hours you saved by automating the deployment of full stack apps.
Google is valuable to have on your resume because it lends credibility to the work you did, but that work has to be relevant to the job you’re applying for.
> I can say I worked with Java, Angular, Typescript, etc. But that's all exceedingly generic
For example, if you’re applying for a company that uses Angular, the focus of your experience section should be having used Angular at Google. A single paragraph that says “Google created Angular, I worked every day with Angular at Google. I built web apps that help support millions of Google customers via a customer service team processing thousands of calls per day. I used angular features x y and z and contributed code to Angular itself.” would be an order of magnitude more effective than what you have now.