It seems fairly safe to assume someone has already snapped this guy up. I can't recall the last time I felt so impressed reading some security writeup
https://opnsec.com/2018/07/into-the-borg-ssrf-inside-google-...
Source: Also a 19 y/o Googler.
I chose this over university - I get paid and am working towards a CS degree as part of the work. Granted, am not an intern (I'm something different) but I understand they are well paid at FAANG companies and the experience is the same.
If the work you do is valuable then it deserves a comp that matches a full time workers rate.
Also, we work in computer science and a for a vast majority of developers it's business as usual. So I wouldn't say that it's particularly generous or lucky.
Before this current job I hadn't worked as a professional (outside of minor freelance work in my home town) so I see this as bootstrapping a career with zero student debt, plus there's perks like travel opportunities and accelerated career growth which I couldn't easily get elsewhere.
> Also, we work in computer science and a for a vast majority of developers it's business as usual. So I wouldn't say that it's particularly generous or lucky.
I was lucky enough to be born into a good family, where I could learn the skills to be where I am today, no?
Right but I meant that Google offering a job or keeping you on payroll shouldn't feel like luck but like the default, expected behaviour in our field.
And that is almost surely only a tiny subset of what could be done via the the whole run with arbitrary permissions thing. Most of the other don't jump out as me as much as that one does, but I may just not recognize the significance of some of the permissions.
It is interesting that he could only make it work in the non-production environment, but I'm not sure if that would actually limit the capabilities meaningfully.