Secrets to Finally Getting a DevOps Job

T: Tools [4:42]

• Tools are essential but not the sole focus for landing a DevOps job.
• Engineers often enjoy learning tools, but this alone is not sufficient.
• Data should guide tool selection; for example, the Kubernetes market is projected to grow significantly.
• The Kubernetes market is expected to grow from $2.5 billion to $7.07 billion with a 22.4% growth rate.
• Key players in the Kubernetes market include Google, Microsoft, IBM, and Red Hat.
• Focus on cloud-native technologies and Kubernetes.
• A deep foundation in Linux is crucial, especially for software engineers.
• Learn one programming language, with Python recommended.
• Develop automation skills, specifically CI/CD, with GitHub Actions recommended.

This section emphasizes that while technical tools are a necessary component, they must be strategically chosen based on market growth and industry trends. Focusing on cloud-native technologies, Kubernetes, Linux, a programming language like Python, and CI/CD tools like GitHub Actions is advised for leveraging a growing market.

When a market is growing, that's how you know there are going to be plenty of jobs and plenty of work available in the time to come.

E: Experience [7:19]

• Companies hire individuals who can perform the work, not just those who study.
• Hiring is a risk; employers need proof of capability.
• A university degree or many years of experience are not always required, but evidence of learnability is.
• DevOps experience can be gained outside of a formal job, at home or in one's current role.
• A Linux Foundation report indicates hands-on experience and a portfolio of accomplishments are key.
• Relevant hands-on experience is rated at 95% importance, followed by a portfolio (85%), certifications (53%), and formal degrees (47%).
• A portfolio of accomplishments can be built at home, solving the "need a job for experience, need experience for a job" conundrum.
• Personal anecdote: early experience with scripting games like Runescape led to renting Linux servers and managing bots, providing hands-on coding, automation, and Linux administration skills.
• Starting a home lab is recommended, using an old laptop with Linux, and progressing to Kubernetes.
• Self-hosting applications can provide valuable DevOps-relevant skills.
• Contributing to open-source projects helps develop collaboration and software building skills.
• A story is shared about how a home lab setup helped someone land a senior SRE role by demonstrating practical experience.
• Listing home lab projects on a CV can transform interviews from interrogations to passionate conversations about one's work.

This pillar stresses the critical importance of practical, hands-on experience and a demonstrable portfolio over formal education or certifications. The speaker advocates for creating such experience through home labs, personal projects, or open-source contributions, as this directly addresses employer needs and significantly enhances interview performance.

The edge came from building and breaking things in my CubeCraft home lab.

C: Content [14:11]

• Content creation is about leveraging algorithms to work for you, not necessarily becoming a full-time content creator.
• Being active on LinkedIn by posting a few times a week can place individuals in the top 1% of users.
• Posting about one's journey and learnings helps market oneself and stand out from numerous applications.
• A CV is also content; it should be a "weapon of mass destruction" and "bulletproof."
• Prioritizing time spent on personal configurations (like Vim RC or Bash RC) over CV optimization is a mistake.
• CVs must be tailored to each job application; there is no one-size-fits-all CV.
• The purpose of a CV is to secure an interview, not the job itself, allowing for discussion of projects and passion.

This section focuses on strategically using content, primarily through active engagement on platforms like LinkedIn and crafting a highly effective, tailored CV, to draw attention from recruiters and hiring managers. It highlights that consistent, quality content creation can significantly improve visibility and create opportunities.

If you spend more time on your hyperland config than you do on your CV, you're doing it wrong.

H: Human [16:59]

• DevOps is not just about coding; it requires interaction with teams, stakeholders, and convincing others of technical implementations.
• DevOps engineers are drivers of change and need people skills to be successful.
• Being difficult to work with or generating friction can hinder hiring, reputation, and references.
• People skills and social skills must be actively cultivated.
• Interviewing is a skill; anxiety and an inability to speak eloquently about one's work can reduce job prospects.
• Employers seek clear, confident individuals who can articulate their skill set.
• Networking is crucial, building a professional network of industry contacts is infinitely more valuable than tech skills alone.
• A professional network can lead to referrals and opportunities that wouldn't arise otherwise.
• The quote "Your network is your net worth" is emphasized.
• Strategies for building a network include being active on LinkedIn (aiming for 500+ connections), attending local meetups, and going to conferences.
• Networking is a compounding effort that builds over time.
• For existing engineers or system administrators, working as a consultant on various contracts can expose them to new environments and people, facilitating network building.

This pillar underscores the importance of interpersonal and networking skills, arguing that they are as, if not more, critical than technical abilities for success in DevOps. Cultivating these "human" aspects is presented as essential for driving change, building a strong reputation, and unlocking career opportunities through professional relationships.

My most recent freelance contract happened because I made a post on LinkedIn where I simply shared a tool that I was learning.