Book Image

The DevOps Career Handbook

By : John Knight, Nate Swenson
Book Image

The DevOps Career Handbook

By: John Knight, Nate Swenson

Overview of this book

DevOps is a set of practices that make up a culture, and practicing DevOps methods can make developers more productive and easier to work with. The DevOps Career Handbook is filled with hundreds of tips and tricks from experts regarding every step of the interview process, helping you save time and money by steering clear of avoidable mistakes. You’ll learn about the various career paths available in the field of DevOps, before acquiring the essential skills needed to begin working as a DevOps professional. If you are already a DevOps engineer, this book will help you to gain advanced skills to become a DevOps specialist. After getting to grips with the basics, you'll discover tips and tricks for preparing your resume and online profiles and find out how to build long-lasting relationships with the recruiters. Finally, you'll read through interviews which will give you an insight into a career in DevOps from the viewpoint of individuals at different career levels. By the end of this DevOps book, you’ll gain a solid understanding of what DevOps is, the various DevOps career paths, and how to prepare for your interview.
Table of Contents (17 chapters)
1
Section 1: A Career in DevOps
5
Section 2: The Application Process
10
Section 3: Interview Process
13
Section 4: Tips, Tricks, and Interviews

Interview with a tech executive passionate about neurodiversity and inclusion

The next individual I interviewed was Magnus Hedemark:

Figure 11.4 – Magnus Hedemark's bio

Reporter: Hi Magnus, I am excited you agreed to let me interview you about DevOps. Would you mind telling us about yourself, and your career progression in IT and DevOps?

Magnus Hedemark: I took a very unconventional route into IT and that could be a very long story by itself. But I think throughout my journey, one thing that always served me well was to try to look ahead and see how I could be useful ahead of the known need. I like figuring out how things work, so rather than starting on the developer side, I came upon the Ops side. And I always had a knack for figuring out how to automate big, hairy, audacious things so that I could focus on smarter work. That was not common in my field in my early career, not like it is now. But there were a couple of big inflection points...