A career shift to DevOps
Here are a few things you should do to begin positioning yourself as a DevOps
engineer.
- Interview at a
company that's hiring DevOps. If you get hired, you'll learn the
operations side of things fast. Real fast. Or get fired. If you don't get
hired, you'll learn what is still missing from your resume / experience
that's preventing you from becoming a full-time DevOps engineer.
Incidentally, we're hiring: Keep Austin Bazaar
- Tell your boss
you want to become a DevOps engineer at your company. Your boss should
help you to this end. If he/she does not, quit. Then come work at
Bazaarvoice with me and a bunch of other really awesome, super talented
engineers working on some really awesome and challenging problems.
- Obtain practical
experience by using your skills as a software engineer to build tools
rather than software. Look at any of the open source projects Netflix has
written for examples / ideas.
- Learn OpenStack.
You can do this on your own time and budget. It's not important whether
OpenStack sucks compared to Rackspace Cloud. What's important is that you
understand all of the various components and why they are important. Have
a wad of cash lying around? Learn Amazon Web Services instead.
- Participate in
anything your team does involving operations -- deployment, scale, etc.
(See list above: "What DevOps is.") If your team doesn't do any
of that (i.e., they send artifacts over to Operations and the Operations
team does deployment), go over to the perations team and sit in on a few
deployments.