114 karma · joined April 6, 2012
Remote: Prefer to work in-office, but would consider remote opportunities.
Willing to relocate: Possibly, for the right opportunity.
Technologies: Linux, Python, Rust, C, Kubernetes
I have been working in SRE/infrastructure roles for the past 13 years at employers including Google, Facebook, and several smaller companies.
I am interested in both SRE-type positions and roles developing systems software. I'd especially like to work with rust or on open source software.
My job search started a few days ago so I don't have an updated resume yet, but my work history can be found on my LinkedIn: https://www.linkedin.com/in/markatto
mark@marktmerritt.com
2) I have been on call for most of my career, but google is the only employer that has actually provided compensation. Depending on your lifestyle, the extra pto can be really nice (for example it’s easy for me to ski on less-crowded days), but as I’ve gotten older being on call has definitely gotten more painful (now that I have a serious partner, not being able to do things on the days she has off can be frustrating.) The actual difficulty/stress of the pages you get will be highly team-dependent, but SRE does a reasonable job of training and tracking pager load.
3) This is highly team-dependent, but there are many teams where systems skills are not a big deal. You need to be able to think in a reliability-focused way, though.
4) Some teams actually develop their own code, other teams rely on swe teams for most of the code. You will read a lot more code than you will write, and you will write less code than they say you will during the interview process. This is also true for SWEs - everyone spend more time big-company-ing than computer-ing.
5) I have not done this, but I have considered moving to a SWE role because there’s more open source opportunities on that side.
6) I’ve found google to be the best place to work of the mega corporations I’ve been, but honestly if the money was the same I’d prefer a smaller company. I’m better at tasks like “chase this bug though a bunch of layers until you find some weird kernel behavior” than “explain why your rollout plan is compliant with our reliability directives.”
1) I don't keep all of my keys on my person, so if I want to sign up for a service when I'm not at home, I have to remember to go back and add my other keys at a later time. If I wanted to, for example, keep a backup key in an offsite location such as a safe deposit box, this would be even more painful.
2) If I lose a key, I need to go and change every service to deactivate the lost key and add my replacement key. This is both time-consuming and error-prone, as it requires me to keep a full list of providers that I use keys with somewhere.
3) Some providers do not even allow you to register multiple keys.