Second: as a sysadmin you'll be expected to manage servers and services. Nobody will give a damn how you do that (except for fellow sysadmins), as long as you don't break anything (too much, too often). This means that nobody will give a damn what language and runtime you use to automate things.
As a sysadmin that writes tools, which means a system programmer, except without the "programmer" title, you'll fly under radar in most organizations and you'll be free to choose any tool that does the job. I learned Erlang this way (I'm a sysadmin/system programmer myself).
And me today? I get offers for programmers quite often, and if I was to go down this road, I probably could land somewhere; I don't know OOP design patterns or latest JavaScript framework by heart (I never learned them specifically), but I have many tools written and published and used to this day, so my programming-fu is quite strong.
So yes, I think it may be a good move to take this job. It certainly was good for me ten years ago.
In the software role I had no idea how apps were actually deployed, and had never touched anything like AWS. At hackathons, for example, I was always clueless when it came to deploying my app and could only ever demo locally. Now, I am very comfortable deploying the code I write in a variety of production environments. Experience with the bottom end of the stack has made me a more productive developer since I have more experience with, say, database migrations, and can debug environment-related issues on my development machine much quicker on my own.
So in my opinion, dev-ops skills are useful and highly transferable, so you should do what interests you. In the worst case you lose interest and flip-flop to another part of the stack and come away as a more well-rounded engineer.