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

Google - Madison, WI. Sorry, no remote work, but Google does sponsor visas. All levels of experience welcome. We've recently hired an ACM fellow, as well as a new college grad.

Of course Google is hiring. So, why I posting this? Every time I tell someone I'm working at Google in Madison, they're shocked that there's an office in Madison, and I often hear people complaining about the lack of interesting technical work in Madison. There's fun technical work in Madison, I promise.

I'm working on a hardware/software co-design project that's attacking a fundamentally hard problem, which started as a 20%-time project. There are a couple other hardware projects in the office; most hardware projects start as prototypes of crazy ideas, and go from there. 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. I'm sorry I can't describe projects in much more detail -- Google is pretty secretive about what goes into datacenters.

The office is small (just under 30 people), and manages to avoid any bureaucracy you might expect from a big company. The work is interesting enough that in the five year history of the office, only one person has left (and he retired to a ranch in Nebraska). Feel free to email me (see profile) if you have any questions.



Edit: Interesting to see this downvoted. If you're downvoting this, I'd be curious to know why. Because Madison is in the middle of nowhere and you don't care about Madison? Because you don't like big companies? Because you're cynically trying to push your job post above this one? Because you think job postings need bullet points?

Just had a recruiter from Google contact me. They do pretty often, once a year. I usually tell them I am not interested. This time the guy mentioned they have some interesting work. So I said ok, I'll talk to him. Set up a time. Waiting for the call. Get an email that he can't make it. Ok, reschedule. Set a new time. Get confirmation he would call. No call, no email not anything.

I am thinking WTF. I wasn't even the one interested in the position, is this level of unprofessionalism common with Google?

Sorry don't mean to derail the comments, but it just kind of left me with a bad taste in my mouth. And then seeing Google as first comment on HN hiring, kind of brought that back to my mind.

Similar experience. Took 4-6 weeks to get a reply to my application email (I'd actually forgotten about it). 4-6 weeks after that (and a few emails from me chasing it up) Google were able to schedule a phone interview. Interviewer was really friendly, and I was pretty excited. Got an email shortly after saying "great that went well, can we fly you to (nearest Google office)". Replied sure - I'm free anytime. 4 weeks later (and a few emails from me chasing it up) and I find out the recruiter has gone on holiday. Another 4 or so weeks later (and more emails from me chasing it up) and I'm told they are having trouble finding someone to interview me for the in-person. Another 2 weeks later I'm finally told the position was filled, but as a promising candidate I should consider applying for other positions.

The idea of working at Google is interesting, but I don't really have the months to invest in the interview process.

A good strategy for getting hired at a big company is to find an internal advocate. It is easy for the Google HR/recruiter to ignore individual candidates, but it is harder for them to ignore you if they get an email from another Google employee asking about the status of your application.

How do you find an internal advocate? Start networking. Find people at Google with common interests or backgrounds as you. Then send me a cold email introducing yourself. It will take a few months to develop a relationship where somebody will happily send that email to HR for you, so start a few months before you are planning to submit job applications.

And at least you were the one who made the first contact. I wasn't even interested to start with, they came to me trying to impress me with new and interesting working going on in that group. I was kind of surprised. For some reason, (and I don't even know why) I expected more from them. Oh well, no need to waste time on them in the future.

Also similar to mine. Someone called me first time but the phone call was bad and he scheduled a new meeting, but he didn't call me back in the scheduled day. 2 days later he sent me a mail trying to reschedule it. As I was travelling i gave him a new number to call. He called in the first one and sent me a message saying that i wasn't there. I think i sent something like 5 emails later to explain that he called in the wrong number, but he never response me back.

By any chance can a technical/coding interview be done completely offline?

And preferably with more relevant tasks, rather than asking to come up with Knuth–Morris–Pratt algorithm on the spot, whereas Knuth, Morris and Pratt spent months of researching.

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...

UW-Madison produces a ton of computer engineering talent. Cray, Intel and Nvidia all recruit heavily here. Sadly outside the Google office there aren't many local options for grads so they end up in Texas or California, even when they often want to stay in Madison. I've always thought you guys were genius for having an office in town.

Is the interview process for working in Madison any less than the ~4 month long nightmare in SV?

Wisconsin is home to some other interesting tech companies too. If you're into HPC, Cray has a big presence there. I think that a lot of job hunters make a mistake by only considering the "startup" scene like Silicon Valley, Boston, etc. when they really are looking for interesting tech jobs not necessarily startup work.

luu, are you open for applications from abroad, concretely, from Pakistan?

Does Google-Madison stack-rank like the rest of Google?

Why is Microsoft all over the blogosphere for stack ranking, but I know dozens of Google folk and this is the first I've heard of it at Google?

No, one tiny office has a completely different set of HR policies.

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