Can I ask (at the risk of sounding churlish) why you're asking? Is it because you want to know how to explain your new job to friends, how to couch your experi

Can I ask (at the risk of sounding churlish) why you're asking? Is it because you want to know how to explain your new job to friends, how to couch your experience in your CV to future employers, whether you should be backing out immediately and returning to something (else) you feel comfortable with? Does the idea of changing careers (an increasingly nebulous term) worry or deter you, or is it the specific career of 'Systems Administrator' that worries you? Devops (another regrettably nebulous term, and one that's on the same shortlist of words to eschew as 'cloud'), as logn observes, makes the distinction less relevant. If you want to hedge your bets and keep an option open to return to full-time dev (though it sounds like it's been a while since you were in such a role), then push the 'devops' appellation, not just on the CV, but also by continuing your 50/50 split of admin and development work. I'd suspect it's easier to drift from devops, rather than sys-admin, into a developer-titled role. Aside: I'm always bewildered by people who obviously have a deep understanding of the syntax of a handful of programming languages, but can't get their head around the English rule that possessive its has no apostrophe.