With DevOps continuing to grow in enterprises of all types and sizes, it’s no wonder that a new job market around DevOps is blossoming. If you want to pursue a career as a DevOps engineer, you might be looking at some pretty substantial compensation for your contributions as well. According to a survey published by PuppetLabs , over 55 of DevOps engineers make at least $100,000 a year, surpassed only by cloud, infrastructure and systems architects. Organizations are starting to see the value that an in-house DevOps leader can generate, leading to high demand and equally high compensation for the position. If this job sounds appealing to you, Matt Werner from DZone gives you his tips on nailing a DevOps interview .
Some more interesting statistics published this week from the Harvard Business Review show that only 20 of companies today qualify as “Digital Leaders” – companies that have the appropriate knowledge and skills to succeed in the digital facets of their business. In this modern age of tech, seeing these numbers took us a little by surprise. Carla Rudder from Enterpriser’s Project lays out the five reasons why companies are failing to lead digitally.
Read on for more stats and advice on how to create a DevOps environment that will give your company an edge over your competitors. As always, stay tuned to all the news coming from @ElectricCloud on DevOps and Continuous Delivery throughout the week to stay in the know.
1 What to Expect from a DevOps Interview
By Matt Werner | Published on @DZone
DevOps as a technical competency is still not as mature as other areas like networking or Java development. As a result, you may only now start seeing job listings specifically mentioning DevOps. Since the field is so new, chances are you haven’t had a ton of experience being interviewed about your practical DevOps experience.
I recently spoke with several hiring managers and DevOps practitioners to learn what kind of questions and may be asked and what experience may be necessary if you find yourself in an interview for a DevOps Engineer job.
— CloudBees (@electriccloud) November 17, 2015
2WantHigher Pay? Get Some DevOps Skills
By @IanDBarker | Published on @BetaNews http://betanews.com/2015/11/17/want-higher-pay-get-some-devops-skills/
DevOps skills are increasingly sought after and as a result salaries for DevOps engineers are higher than for other IT job titles according to new research. IT automation software provider PuppetLabs has released its 2015 DevOps Salary Report based on data gathered from its 2015 State of DevOps Report. Among the findings are that DevOps engineers make noticeably higher salaries than most other practitioner job titles in the 2015 survey and report. 55 percent of US DevOps engineers make $100,000 per year or more; this share is surpassed only by architects (with 75 percent making $100,000-plus), a group that includes the distinct job titles of architects, cloud or infrastructure architects, and systems architects.
3The Dangers of Neglecting a DevOps Strategy
By @dmccaff | Published on @CIOInsight http://www.cioinsight.com/it-strategy/application-development/slideshows/the-dangers-of-neglecting-a-devops-strategy.html
The majority of organizations are replacing existing tech with DevOps solutions, according to a recent survey from Appvance. By doing so, they hope to boost both the velocity of tech, while increasing productivity and quality assurance. For the most part, IT decision-makers are pleased with the progress their tech teams are making with DevOps. But there's room for improvement, as the number of required testing tools is slowing time to market, findings reveal.
— CloudBees (@electriccloud) November 19, 2015
4The DevOps Unicorn: Achieving Success with Speed and Security
By Kim Kay| Published on @CompTechReview http://wwpi.com/the-devops-unicorn-achieving-success-with-speed-and-security/
The DevOps unicorn. In the IT industry today, these are seemingly rare, mystical organizations that were born in the Internet era and leverage new technologies to break down the traditional silos between developers, security and IT operations. By effectively bridging these environments, the result is a high-trust team that is empowered to innovate, nimble and can quickly improve the competitive posture of their companies.
5Is Software Development Art or Science? Geekwire Podcast with Software Engineering Daily
By @toddbishop | Published on @GeekWire http://www.geekwire.com/2015/is-software-development-art-or-science-geekwire-podcast-with-software-engineering-daily/
I recently sat down with Meyerson at the GeekWire offices to record a podcast about some of the big topics in the industry and on the minds of his guests. We talked about the rapid changes in front-end web development, the evolving role of open-source technologies, the changing nature of data science, and the globalization of software development among younger generations — such as the two Nigerian teenagers behind the Crocodile browser.
6Five Barriers to Success in the Digital Future
By @carlarudder | Published on @4enterprisers
A recent global survey of nearly 450 business leaders, conducted by Harvard Business Review Analytic Services, found that most companies lack the knowledge and skills needed to succeed in the digital aspects of their business. The survey results placed less than 20 percent of respondents into a category of "Digital Leaders," organizations that have both a digital vision and strategy as well as the right people, processes and technology needed to succeed.
— CloudBees (@electriccloud) November 19, 2015
7Your DevOps Subculture
By @devopsdotcom | Published on @devopsdotcom http://devops.com/2015/11/16/your-devops-subculture/
I’m often asked how to create a DevOps Culture and there is no single answer to this question. The focus initially for me in any cultural movement is to understand how the organization incentivizes and what its core beliefs are. When it comes to DevOps, I am normally looking for ways to bring these two teams together from a fundamental aspect first. One method I have found that works well when I’m consulting with these two teams is a Culture Session. Teams often end up with a subculture that incorporates aspects of the macro culture. These subcultures can evolve into the silos that DevOps is designed to break down. A Culture Session is one where you bring these teams together en masse and work on defining a new unified subculture.
— DOES Summit (@DOESsummit) November 17, 2015
8Creating the DevOps Environment That'll Give you an Edge Over the Competition
By @trevorjTT | Published by @TechTarget
At a time when the speed of application development is vital to commercial success, the DevOps methodology -- based on communication, collaboration, integration and automation -- has become one of the biggest IT moves around. However, it’s more than just a business philosophy; to do it right requires genuine infrastructure investment and development. The increased availability of virtualized and cloud infrastructure is bringing agile development to organizations of all shapes and sizes. As you might expect, this means traditional large-scale organizations are bringing development and operations teams together to get more agility in their businesses, and ultimately develop projects in shorter timeframes.
9Successful Technology Leaders Will Embrace the Citizen Developer
By @GeorgevHulme | Published on @devopsdotcom
There’s just no slowing down the consumerization of IT. The Bring Your Own Device (BYOD) trend itself has created an enterprise market that will hit $266 billion in 2016, according to a recent report by Markets and Markets. Goldman Sachs released a study earlier this year that found the global software-as-a-service market will reach $106 billion in 2016. And a good portion of those software services are being bought outside of the traditional IT department. But the consumerization of IT isn’t stopping with BYOD and cloud services. It’s now extending to application development, more specifically, it’s extending to so-called citizen developers – who are any user (and especially not traditional developers) that are building new applications for use in their organization. They are generally using high-level, newer generation language platforms and cloud services to create their apps. And we’re not talking about creating apps for individuals or a small group of workstations in Excel or Microsoft Access. No, users have been creating for those years. We are talking about full-blown enterprise apps.
10Connected Teams, Connected Code, and the Connected Device
By @ audidv | Published on @SYSCONmedia http://anders-wallgren.ulitzer.com/node/3543505
In my previous post I discussed the challenges of IoT software delivery as they relate to managing the complexities of integrating three distinct development pipelines comprising the different components of the IoT software. These are: 1.) The embedded software in the device itself – for example, software embedded in a car. 2.) The big-data backend application used to store and analyze the real-time data accumulated from the different devices. 3.) The mobile app – used by end users to control the device.
— CloudBees (@electriccloud) November 16, 2015
Stay up to date
We'll never share your email address and you can opt out at any time, we promise.