<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Yeah… that’s not exactly what they mean when they say “site reliability engineer”.</div><div class=""><br class=""></div><div class="">In fact, of the three separate things they tried to interview me for, the initial 3, 4, or 5 steps of the interview process had nothing to do with the position, and when getting finally to a Google human in Atlanta, it was COMPLETELY different than what the previous levels of interview had asked for. And none of it, at any level, referred to “end to end testing”.</div><div class=""><br class=""></div><div class="">I’m told that there’s been a recent overhaul in the recruiting and interviewing process there, but they just haven’t been consistent at any time I’ve spoken with them.</div><div class=""><br class=""></div><div class="">As for the actual core of your question… If you can, do the Server Tuning class from RedHat. It does the whole shebang concentrating on CGROUPs. Best overall introduction to the tech I’ve seen anywhere, and I’d say I’m a much better “tuner” in regards to Linux boxes than I was in the past solely due to that class.</div><div class=""><br class=""></div><br class=""><div apple-content-edited="true" class="">
<div class="">Jerald Sheets</div><div class=""><a href="mailto:questy@gmail.com" class="">questy@gmail.com</a></div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On May 21, 2015, at 9:13 AM, leam hall <<a href="mailto:leamhall@gmail.com" class="">leamhall@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">Hey guys,<br class=""><br class=""></div>I'm seeing more jobs similar to Google's "Site Reliability Engineer". Someone who has a good handle on testing things from end to end to find bottle-necks, risks, and solve problems. I've been doing something like that for a while, but would like to get better. Any books, courses, tools, or ideas on how to do that?<br class=""><br class=""></div>Thanks!<br class=""><br class=""></div>Leam<br class=""><div class=""><div class=""><div class=""><div class=""><div class=""><br class="">-- <br class=""><div class="gmail_signature"><div class=""><a href="http://leamhall.blogspot.com/" target="_blank" class="">Mind on a Mission</a></div></div>
</div></div></div></div></div></div>
_______________________________________________<br class="">Ale mailing list<br class=""><a href="mailto:Ale@ale.org" class="">Ale@ale.org</a><br class="">http://mail.ale.org/mailman/listinfo/ale<br class="">See JOBS, ANNOUNCE and SCHOOLS lists at<br class="">http://mail.ale.org/mailman/listinfo<br class=""></div></blockquote></div><br class=""></body></html>