3 ms·
I found Google's dev interview to be especially difficult, I personally hate doing hours of whiteboard coding (sorry, I tend to code on computers instead, silly
by snorkel 9y ago
I found Google's dev interview to be especially difficult, I personally hate doing hours of whiteboard coding (sorry, I tend to code on computers instead, silly me) ... So I wasn't hired, but those who worked as devs there told me that's a blessing because after all the rigorous interviewing bluster they'll assign devs to remedial code refactoring anyway. I'm not a rockstar coder above doing the housekeeping work but doesn't sound fun either. Why hire top coders then assign them intern busy work? I wonder if the strategy was to just drain the local talent pool of top coders so competitors had less of a candidate pool. Just odd to set the interview bar so high, and for what purpose?
- foota 9y agoYou leave your interns to do code quality refactors? Seems like something more experienced engineers should do.
- nradov 9y agoI don't work at Google, but code refactoring is critically important in the real world. It's not intern work.
- alexasmyths 9y agoRe-factoring is probably 80% of the job. New projects are rare, so very few are writing a lot of code from scratch.
- away2017throw 9y agoWhy not, like, test refactoring skills? Mind blown!
- deleted 9y ago[deleted]
- cycrutchfield 9y agoIf that's the attitude you brought to the interview, then perhaps that's why you were not hired? What percent of software engineers' time do you think is spent doing green-field development with no refactoring, writing tests, documentation, etc.?
- throwayit 9y agoI actually find refactoring legacy code to be one of the most challenging things I do at work. While I definitely wouldn't want to do that for all 40 hours of work I wouldn't classify refactoring as "remedial".
- balls187 9y ago> Just odd to set the interview bar so high, and for what purpose? Check Google's stock price.
- nishs 9y agoFWIW, interns on the team I interned on had the chance to work on experimental, new features that required little to no refactoring. Maintaining existing code was done by developers who knew the code well and were capable of making measured engineering decisions.