Hacker News new | comments | show | ask | jobs | submit login

I didn't downvote you, but "sorry, no remote work" is a comical restriction for this field, especially for a large organization like Google.



Is your hypothesis that all types of work in "this field" (which, exactly?) spanning all levels of interactivity can be performed equally well by remote workers? I have personal experience that such a hypothesis is demonstrably false, even for pure software projects. I can only imagine how much more so the disconnect would be when the work involves hardware.


"The majority of people here are doing low-level systems programming, usually networking related, and a handful of people are doing data analysis (call it big data, if you like) to figure out how to optimize Google's next generation hardware and software platforms."

Those tasks can and are done by programmers from anywhere. There is absolutely no reason to make them come to an office.


How the hell do you build hardware remotely?


"The majority of people here are doing low-level systems programming, usually networking related, and a handful of people are doing data analysis (call it big data, if you like) to figure out how to optimize Google's next generation hardware and software platforms."


If you're doing firmware/software people can just mail you devkits, proto boards.


devkits and proto boards do have bugs, especially during the early iterations. There are many occasions that I (firmware engineer) need to sit down with FPGA/Hardware engineers to figure out why the system is not performing as designed, sometimes it is firmware issue, sometimes it is hardware, and it was the combination of firmware/hardware and ambient temperature!! It is way more ineffective to perform this kind of debugging with someone in a remote site.


That could be quite time inefficient, depending on where you live...




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: