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

Things to avoid during the interview process

In the previous section, I told a story about my successes and how they helped me get into DevOps. Now, I would like to spend a few pages reminiscing on my failures, or more so my failed attempts to land a job. To start, we will travel back to 2008.

Avoid providing inaccurate or misleading information when applying for a position

The time incorrect information cost me a job.

In my junior year of college, I began looking for internships. I applied to one job that required applicants to be pursuing a degree in computer science; I was pursuing a degree in industrial engineering. When the question came up on the questionnaire asking if I was currently enrolled in a computer science program, I answered yes. A week later, I received a call from the recruiter and we began discussing the job; it was a very short discussion that ended with me being sent a link to a technical aptitude test. I must have done OK on it because I made it to the...