|
|
|
|
|
|
by bane
4746 days ago
|
|
|
I was contacted by a Google recruiter a few months ago, I had no intention of changing my day job at the time, but for shits and grins I went through a couple phone interviews. The position they were hiring for wasn't an area I have any experience in (the recruiter had made a mismatch), but I thought the questions were reasonable for somebody who works in that field and were kind of fun. They were quizzy, but could be practical. It was a management position so there weren't any coding questions, but things like basic cost estimating that sort of thing. I had fun and wouldn't mind it again, it didn't feel like a bunch of stupid random brain teasers like I've experienced before (how many t-shirts would it take to make sea worthy sail? why are manholes round?) etc. |
|
|
Interesting; when I interviewed for a management position (test manager) it was nothing but coding questions, including the infamous "reverse a string" question. ("Would like that optimized for space or speed? In-place, or do I get a buffer? Can you tell I've heard this a zillion times before?") I can understand wanting a test manager to be more than an empty suit, but yoiks.