On 6/24/10 6:07 , Mark Dennehy wrote: > Have to agree with Jan there. My recent interviews with them were > courteous, friendly and interesting, there wasn't a negative note in > there except for the hype-generated stress and the embarressing > brainfarts that resulted (that's the second time in five years that > I've interviewed for an SRE role, and both times I blanked on things I > dealt with day-to-day. Interview stress != Job stress). And that's a > complaint about their hiring process rather than the interviews > themselves. In fact, Google interviews are the only ones I've > consistently come away from with interesting questions to go dig into > or new stuff learnt.
I guess I've moved beyond a phase where I could be excited by the things you can easily google when you need them. Who cares how syncookies exactly work or that there is no creation timestamp in an inode record or that a switch uses link down event to clear the ARP cache? But how to design, implement and document a system, network or a process (especially process) and then redesign it and adapt several times as the business needs change, and still keep it in a good shape and well oiled, usable and maintainable by other people, that is what you can not google, this is the real challenge. My latest accomplishment was that I've managed to take a full month off work and not get a single call or even an email, although I've designed and implemented at least 80% of the infrastructure at my current employer. I think I'm going to put that on the first page of my resumé. > Now if they'd just stop saying no after seven or eight interviews > without feedback, I'd be happy... Boy, you can't take no for an answer, can't you? ;) _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
