| You’re describing work that has no relevance outside of a megacorp like Google which even amongst megacorps is quite unique because it invents technology and can afford to do so. 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. |
This is so incredibly dismissive and naive about the work being done. I can't believe you actually think this way. Its almost insulting
These kinds of projects require everything any other project needs. He learned a new tech, was able to identify a real problem then solve the issue with real measureable results. All of this within an organziation where you need to design and plan correctly
all of this is generalizable to almost any software work being done. and important skills for experienced engineers