<p>At the risk of getting vote down, off-topic  or even heresy, I going to tell you, 
"Don't listen to the purists telling you that DevOps is not a role."</p>

<p>You are on the right track. <strong>It should fit your company.</strong> That's what matters when hiring.</p>

<p>If you need a DevOps, to work like a DevOps, produce results like DevOps, it is a DevOps. </p>

<ul>
<li>Don't let anyone dissuade you otherwise.</li>
<li>Advertise anyway.</li>
<li>Interview anyway.</li>
<li>Hire anyway.</li>
</ul>

<p>While at that, find out more about DevOps, how the concept can fit into your company, how does the person fits in.</p>

<p>Distill out more about the role you need to fill. Search for questions you can ask. There are plenty of <a href="https://www.quora.com/What-are-some-good-interview-questions-for-a-DevOps-position" rel="nofollow noreferrer">example</a>, even if you are not subject matter expert. Some good old-fashioned patience and hardwork.</p>

<p>Do you need an employee? Or freelancer? A jack of all trades? Only you know your company well. </p>

<p>Create your unique culture that is your interpretation of DevOps.</p>

CC BY-SA 3.0
2017-06-27T13:46:07.057Z
+1 to this. Purists have been hung up on the _devops is not a role_ answer for too long, but the industry, job boards and recruiters have already turned it into a reality, and it's time we accept it for what it is.
grumpyops
CC BY-SA 3.0
2017-03-23T18:31:39.853Z
2017-08-13T03:44:25.660Z
2017-08-13T03:44:25.660Z
kenchew
<p>"Hiring a DevOps" will be tough because DevOps isn't a role.  IF you can find an engineer with software development <em>and</em> engineering skills, you're on the right track..</p>

<p><strong>However</strong>,</p>

<p>Your hiring process will be complicated by a few factors:</p>

<ol>
<li>Site Reliability Engineers (Google's term for admin/engineers with coding skills) are rare</li>
<li>Rare skills are expensive</li>
<li>Rare skills are... rare.</li>
</ol>

<p>The good news is you may not need a fully qualified SRE.</p>

<p>Your use case, as it were, is hiring engineers to establish your infrastructure (AWS) and automate deployments (Jenkins.)  Those skills are not all that rare, but you may have a challenge finding them in a single person.  </p>

<p>You also mention that you yourself don't have those skills.  This is a further complicating factor.  You don't have the skills necessary to evaluate the skills of your candidates.  You must ultimately find a way to develop (or hire, as in an Engineering Manager) the skills needed to manage this type of resource.</p>

CC BY-SA 3.0
2017-03-10T20:03:05.697Z
That's common for human resource people to not have the skills of the people they are hiring. Usually the best idea is to interview with skilled people to have an evaluation of the candidates
Tensibai
CC BY-SA 3.0
2017-03-10T21:19:00.277Z
I meant to say, I'm a good developer, but I also want to be surrounded with people who excel at other disciplines inside the company eventually, better than mine.
Thomas
CC BY-SA 3.0
2017-03-10T21:39:52.100Z
@ThomasMoors that's a very good idea. Don't bother too much, I'm vocal about what I think about this site, but I'm just one in a crowd. Sorry if I sounded rude btw
Tensibai
CC BY-SA 3.0
2017-03-10T19:53:37.083Z
2017-03-10T19:53:37.083Z
Dave Swersky
<p>There are two possibilities: </p>

<ol>
<li><p>You need help figuring out what are the changes your company needs to go through on your journey to DevOps. </p></li>
<li><p>You know what you need and just look to hire people to implement this vision for you.</p></li>
</ol>

<p>If you need someone to help you figure out which issues you need to concentrate on, there is a really good company called <a href="https://devops-research.com" rel="nofollow noreferrer">DORA</a> (DevOps Research and Assessment), which is cofounded by Dr. Nicole Forsgren, Jez Humble and Gene Kim. Nicole has run the <a href="https://puppet.com/resources/whitepaper/2016-state-of-devops-report" rel="nofollow noreferrer">State of DevOps</a> survey for years and has been keeping detailed statistics of the industry for years. Jez Humble is a guru of Continuous Delivery and literally wrote <a href="http://a.co/iCdMtDo" rel="nofollow noreferrer">the book</a> on it. Gene Kim is the author of <a href="http://a.co/6ze2QvB" rel="nofollow noreferrer">The Phoenix Project</a> and the last two are co-authors of <a href="http://a.co/1UiVWxV" rel="nofollow noreferrer">The DevOps Handbook</a>. DORA provides an <a href="https://devops-research.com/assessment.html" rel="nofollow noreferrer">assessment</a> of your company and help you answer those questions.</p>

<p>If you have a pretty good idea where you need to go and need someone to help you get there, getting a recruitment agency is probably not a good idea at this point. I would suggest to go to DevOps Enterprise <a href="http://events.itrevolution.com" rel="nofollow noreferrer">DOES Conference</a> or local <a href="https://www.devopsdays.org" rel="nofollow noreferrer">DevOpsDays Conference</a> and talk to people in the hallways. Look for recommendations and maybe even open a booth, make a poster about hiring.</p>

<p>Second option would be to come here and start asking those questions in this forum and look for the experts that answer them and get up-voted. Many of those might be actually looking for a job or a challenge. Sometimes even asking questions about your current situation and use case here could point you to the right course of action.</p>

CC BY-SA 3.0
2017-03-23T21:03:02.937Z
2017-03-23T21:03:02.937Z
Jiri Klouda
<p>I look for a number of things in the people I have hired into this space.</p>

<ul>
<li>a minimum of 'ha' level of agile (google shu, ha, ri for agile adoption if you need more)</li>
<li>technical hands-on experience - coding, automation, etc, but I'm tool and language agnostic</li>
<li>learning personality - they take the initiative to constantly learn</li>
<li>inquisitive and not looking to place blame - they can accept failure as a learning lesson</li>
<li>they are a team player who can trust and be trusted since psychological safety is the number one success factor for high performing teams</li>
<li>they can coach and mentor - they share their knowledge without being elitist - prima donnas have no place on high performing teams</li>
<li>they have "enough" social skills since they need to be team members and communicate well</li>
</ul>

<p>I have yet to find a perfect candidate, so it's always some type of trade-off. In today's world, I looked through 65+ resumes that were "pre-qualified" as candidates by agencies and HR, discarded 50 or more as not meeting my minimum requirements on paper, interviewed 15+, and hired 3. This process took me the better part of 9 months.</p>

CC BY-SA 3.0
2017-03-23T22:52:32.827Z
And to complement, what I feel missing in your post is a description of what you feel was missing, saying there was some lacks without guidance on how to present things to cover these lacks doesn't help to get a better situation
Tensibai
CC BY-SA 3.0
2017-03-23T23:11:36.883Z
If people do not submit a resume tuned to the job posting minimum requirements then they don't meet my minimum requirement to progress further in the process. If a person really wants to be considered for a position then they need to show it with some effort on their part. As a hiring manager it is my point of view that counts because I know what I'm looking for.
icewav
CC BY-SA 3.0
2017-03-24T06:56:18.590Z
Sounds like a good advice to add 'posting a resume tuned to the job'. That's easier to check than guessing your requirement on the paper. if your requirements are the bullet points above then maybe ´my requirements above on the paper' could be a better wording
Tensibai
CC BY-SA 3.0
2017-03-25T01:10:41.260Z
Unfortunately the bulleted list above is what I need to discern from the interview. My minimum requirements and my preferred requirements are clearly spelled out in the job postings I make, and they change based on what skills I need to round out a team. The applicant usually gets an interview if they meet the minimum requirements and almost always if they meet the minimum requirements plus some of the preferred requirements.  While this may seem vague, I am quite specific in each job posting I make as to what I'm looking for in a successful candidate.
icewav
CC BY-SA 3.0
2017-03-25T01:15:03.713Z
There is a percentage of candidates that falsely claim what's on their resume that simple fact checking uncovers. These applicants never get an interview with me. Example: claim you have a Scrum Alliance certification, since I have a few of their certifications, I can log in and check yours.
icewav
CC BY-SA 3.0
2017-03-25T08:40:48.933Z
I think you should try to integrate/move your comments in your actual answer.
Pierre.Vriens
CC BY-SA 3.0
2017-03-23T22:24:47.110Z
2017-03-23T22:41:58.403Z
2017-03-23T22:41:58.403Z
icewav
<p>Aside other questions I believe the following answer is yet missing - I want to summarize what I have learned so far in a mostly humble tone:</p>

<p>Introducing DevOps skills to your team is probably not enough (that is to consider that you cannot hire a DevOps)! (Like asking on a lower level what are best tools to make things work, here you seem to want your organization work).</p>

<p>The real question is: what is your oganizations digital transformation strategy and <strong>how much good DevOps will help you to create more customer value and reduce your costs</strong>, still having a good climate?</p>

<p>DevOps reveals the need for change, and change requires taking responsibility.</p>

<p>Imagine a situation were working DevOps might introduce pressure on other teams. DevOps is sometimes a result of evolution from Agile and Continous Integration - what are your assets here?</p>

CC BY-SA 3.0
2017-06-27T09:07:41.123Z
2017-06-27T09:07:41.123Z
Ta Mu
<p>It is a common misbelief that “DevOps” is a role in a company. The word merely denotes an organisational shift in software companies, this shift can be shortly described by the “<a href="https://www.safaribooksonline.com/library/view/programming-amazon-ec2/9781449303617/ch01s03.html" rel="noreferrer">You build it, you run it!</a>” coined by Werner Vogels:</p>
<blockquote>
<p>There is no need to distinguish between building and running, and according to Werner Vogels, it is much better than that:</p>
<blockquote>
<p>Giving developers operational responsibilities has greatly enhanced the quality of the services, both from a customer and a technology point of view. The traditional model is that you take your software to the wall that separates development and operations, and throw it over and then forget about it. Not at Amazon. You build it, you run it. This brings developers into contact with the day-to-day operation of their software. It also brings them into day-to-day contact with the customer. This customer feedback loop is essential for improving the quality of the service.</p>
</blockquote>
<p>This lesson is interesting, but this particular change in an organization is not always easy to implement.</p>
</blockquote>
<p>This shift is concomitant of an increasing importance of continuous integration and deliveries methods. Please note that these ideas are much older than the formalisation of “agile” methodologies, some of them are already present in the NATO Scientific Committee report about software engineering published in … 1968!</p>
<p>While the wording can be overlooked, the short description of the DevOps proposal (this site) mentions “software engineers”:</p>
<blockquote>
<p>Beta Q&amp;A site for software Engineers working on automated testing, continuous delivery, service integration and monitoring, and building SDLC infrastructure.</p>
</blockquote>
<hr>
<p>Now if you are looking for a software engineer that can help your team getting started with these methodologies, engage them on this topic. Even if you are not familiar with this topic, following the “You build it! You run it!” slogan you can start from a programming problem and lead the interview towards question about deployment and maintenance of the application.</p>

CC BY-SA 3.0
2017-03-10T17:40:46.430Z
The confusion is also based on job offers like this: http://stackoverflow.com/jobs/135988/devops-engineer-yellowtail?offset=1&q=devops
Thomas
CC BY-SA 3.0
2017-03-10T17:46:45.373Z
Yes, there is a lot of people or organizations using “DevOps” as a role. No one can be blamed for being a victim of this and your question is useful to clarify this, so thank you to have asked it, even it will probably finally be closed. I hope you find this answer useful and that you will take the chance to otherwise contribute to this site or use it as an information source!
Michaël Le Barbier
CC BY-SA 3.0
2017-03-10T18:54:23.017Z
@ThomasMoors : your prior (interesting!) comment should be integrated in your actual question ... even if it was only to document your confusion ...
Pierre.Vriens
CC BY-SA 3.0
2017-03-10T18:57:01.660Z
@Pierre.Vriens done
Thomas
CC BY-SA 3.0
2017-03-10T19:59:20.860Z
Synonym/related "eat your own dog food", don't do something you won't use
Tensibai
CC BY-SA 3.0
2017-03-10T17:37:20.343Z
2017-03-10T17:37:20.343Z
2020-06-18T08:28:10.803Z
Michaël Le Barbier
<p>Good developers should fit rule 11 of the <a href="https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/" rel="nofollow noreferrer">Joel Test</a>:</p>

<blockquote>
  <p>Do new candidates write code during their interview?</p>
</blockquote>

<p>However, I know little to nothing about Docker containers, how to configure Jenkins or AWS, etc. What would be a good way to test if the person who applies can manage such tasks?</p>

<p>Sub-questions: I believe that a good devops employee can configure the build chain once and it should work from then on out. Can I then also expect him or her to be a developer in the company (DEVops)? As DevOps is a relatively "new" job, is it maybe better for small companies to share a devops employee or hire him or her as a freelancer whenever you need him or her?</p>

<p><a href="https://i.sstatic.net/omE6J.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/omE6J.png" alt="enter image description here"></a>
My confusion about the term originates from job offers like this, even <a href="https://stackoverflow.com/jobs/135988/">here on stackexchange</a> (= link where above screenprint was taken from).</p>

<p>I found this helpful, but possible opinionated article you might want to read if you stumble on this question: <a href="https://hackernoon.com/devoops-some-common-anti-patterns-1850ac2f5074" rel="nofollow noreferrer">https://hackernoon.com/devoops-some-common-anti-patterns-1850ac2f5074</a></p>

CC BY-SA 3.0
2017-03-10T16:00:21.667Z
As DevOps is not a role (its a buzzword as such), you're hiring a modern sysadmin according to your description.
Tensibai
CC BY-SA 3.0
2017-03-10T16:01:09.767Z
I'm voting to close this question as off-topic because [DevOps is not a role/job position](http://devops.stackexchange.com/questions/157/what-is-the-difference-between-sysadmin-and-devops-engineer/160#160)
Tensibai
CC BY-SA 3.0
2017-03-10T16:02:35.117Z
I agree on that part, but in the past it was easier to get away without continuous integration, but nowadays it really is a necessaty
Thomas
CC BY-SA 3.0
2017-03-10T16:07:27.377Z
That just mean the job of a Sysadmin has evolved, it is not exactly the same in a DevOps organization than a silo based one. But you're still after a sysadmin, not after a DevOps. I really can't support this buzz of DevOps is a role on this site. Maybe if wording it as "How do I ensure a Sysadmin candidate is good fit in my DevOps organization ?" that would be a better idea. But read my answer to the question linked in my second comment, that should give a start of answer to your questions.
Tensibai
CC BY-SA 3.0
2017-03-10T16:41:53.367Z
@Tensibal I agree with you but I am also tempted to leave this question open as it can help to clarify this misconception – and we can expect to see this question coming again and again and again and again.
Michaël Le Barbier
CC BY-SA 3.0
2017-03-10T17:02:56.170Z
@MichaelGrünewald Add an answer clarifying this. If upvoted it will prevent the question from dissapearing, even if closed. Best of both worlds: clarifies the issue & remains visible as off-topic for the site, helping prevent future such questions (which could be duplicated to it)
Dan Cornilescu
CC BY-SA 3.0
2017-03-10T17:03:44.270Z
@DanCornilescu I was not aware of this, I will do this right away!
Michaël Le Barbier
CC BY-SA 3.0
2017-03-10T18:47:45.600Z
@Tensibai FWIW, I don't think we should ever close a question on the basis that "DevOps is not a role."  Every question where this confusion is evident is an opportunity to clarify. The answer to the question should include a clarification to that effect, and a link to that question.  If we close questions just because they confuse the DevOps term, we will alienate new users and miss the opportunity to clarify.
Dave Swersky
CC BY-SA 3.0
2017-03-10T18:52:11.217Z
"***If it doesn't work according to the documentation, then change the documentation!***". I mean can't we somehow adapt what DevOps.SE is about? I.e. (of course) what DevOps is really about, but also those topics that people (incorrectly) assume to be DevOps, something like "and also misconceptions about DevOps" (the documentation fix could be that easy ...).
Pierre.Vriens
CC BY-SA 3.0
2017-03-10T19:14:59.893Z
@Dave I disagree as guessing what's the Op put under devops is just... a guess... I'd prefer to close, let the OP edit to clarify and reopen.
Tensibai
CC BY-SA 3.0
2017-03-10T21:23:26.547Z
@ThomasMoors thank you for including the image (hope it's ok I added the actual link to it also). By accident the job offer is in my language. So I did review that job itself. About the only DevOps related item in it are (1) the DevOps in the job title and (2) "ontwikkelstraat opzetten" (literal translation = creation of a street to perform development). Really interesting requirements (no I did not apply yet). But it seems like the perfect candidate only needs to know what DevOps means, and should also have some idea of what "ontwikkelstraat" could mean (nobody will understand that anyway).
Pierre.Vriens
CC BY-SA 3.0
2017-03-10T21:27:10.303Z
@Pierre.Vriens I'm also Dutch and altough you are correct, this is just the very first hit for DevOps I could find. Unrelated: `ontwikkelstraat` will without a doubt mean continuous integration / a workflow for writing code -> integrating code (delivering it to the users). However I agree they should not create their own slang / translate it this way.
Thomas
CC BY-SA 3.0
2017-03-10T21:37:05.340Z
"ontwikkelstraat" = CI, how funny those Dutch guys over there (they can be very creative with terminology transation ... instead of just caling it "Continue Integratie" ..... yes that is also Dutch, or should I say rather Flemish?) ... PS: watch out that it doesn't end up in a traffic jam (a highway that looks like a parking lot) ... sorry for the joke ... Doei!
Pierre.Vriens
<culture><software-engineering>
How do I hire a good DevOps, fitting my company?
Thomas
# How do I hire a good DevOps, fitting my company?

(Asked by: username_0 on 2017-03-10)

Good developers should fit rule 11 of the [Joel Test](https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/):

> Do new candidates write code during their interview?

However, I know little to nothing about Docker containers, how to configure Jenkins or AWS, etc. What would be a good way to test if the person who applies can manage such tasks?

Sub-questions: I believe that a good devops employee can configure the build chain once and it should work from then on out. Can I then also expect him or her to be a developer in the company (DEVops)? As DevOps is a relatively "new" job, is it maybe better for small companies to share a devops employee or hire him or her as a freelancer whenever you need him or her?

[![enter image description here](https://i.sstatic.net/omE6J.png)](https://i.sstatic.net/omE6J.png)
My confusion about the term originates from job offers like this, even [here on stackexchange](https://stackoverflow.com/jobs/135988/) (= link where above screenprint was taken from).

I found this helpful, but possible opinionated article you might want to read if you stumble on this question: <https://hackernoon.com/devoops-some-common-anti-patterns-1850ac2f5074>

**Tags:** culture, software-engineering

> **Comments:**
> **username_1**: As DevOps is not a role (its a buzzword as such), you're hiring a modern sysadmin according to your description.  
> **username_1**: I'm voting to close this question as off-topic because [DevOps is not a role/job position](http://devops.stackexchange.com/questions/157/what-is-the-difference-between-sysadmin-and-devops-engineer/160#160)  
> **username_0**: I agree on that part, but in the past it was easier to get away without continuous integration, but nowadays it really is a necessaty  
> **username_1**: That just mean the job of a Sysadmin has evolved, it is not exactly the same in a DevOps organization than a silo based one. But you're still after a sysadmin, not after a DevOps. I really can't support this buzz of DevOps is a role on this site. Maybe if wording it as "How do I ensure a Sysadmin candidate is good fit in my DevOps organization ?" that would be a better idea. But read my answer to the question linked in my second comment, that should give a start of answer to your questions.  
> **username_2**: @Tensibal I agree with you but I am also tempted to leave this question open as it can help to clarify this misconception – and we can expect to see this question coming again and again and again and again.  
> **username_3**: @MichaelGrünewald Add an answer clarifying this. If upvoted it will prevent the question from dissapearing, even if closed. Best of both worlds: clarifies the issue & remains visible as off-topic for the site, helping prevent future such questions (which could be duplicated to it)  
> **username_2**: @DanCornilescu I was not aware of this, I will do this right away!  
> **username_4**: @username_1 FWIW, I don't think we should ever close a question on the basis that "DevOps is not a role."  Every question where this confusion is evident is an opportunity to clarify. The answer to the question should include a clarification to that effect, and a link to that question.  If we close questions just because they confuse the DevOps term, we will alienate new users and miss the opportunity to clarify.  
> **username_5**: "***If it doesn't work according to the documentation, then change the documentation!***". I mean can't we somehow adapt what DevOps.SE is about? I.e. (of course) what DevOps is really about, but also those topics that people (incorrectly) assume to be DevOps, something like "and also misconceptions about DevOps" (the documentation fix could be that easy ...).  
> **username_1**: @Dave I disagree as guessing what's the Op put under devops is just... a guess... I'd prefer to close, let the OP edit to clarify and reopen.  
> **username_5**: @username_0Moors thank you for including the image (hope it's ok I added the actual link to it also). By accident the job offer is in my language. So I did review that job itself. About the only DevOps related item in it are (1) the DevOps in the job title and (2) "ontwikkelstraat opzetten" (literal translation = creation of a street to perform development). Really interesting requirements (no I did not apply yet). But it seems like the perfect candidate only needs to know what DevOps means, and should also have some idea of what "ontwikkelstraat" could mean (nobody will understand that anyway).  
> **username_0**: @username_5 I'm also Dutch and altough you are correct, this is just the very first hit for DevOps I could find. Unrelated: `ontwikkelstraat` will without a doubt mean continuous integration / a workflow for writing code -> integrating code (delivering it to the users). However I agree they should not create their own slang / translate it this way.  
> **username_5**: "ontwikkelstraat" = CI, how funny those Dutch guys over there (they can be very creative with terminology transation ... instead of just caling it "Continue Integratie" ..... yes that is also Dutch, or should I say rather Flemish?) ... PS: watch out that it doesn't end up in a traffic jam (a highway that looks like a parking lot) ... sorry for the joke ... Doei!  

---

## 6 answers

### Answer by username_2 on 2017-03-10. Score: 13 | Accepted answer

It is a common misbelief that “DevOps” is a role in a company. The word merely denotes an organisational shift in software companies, this shift can be shortly described by the “[You build it, you run it!](https://www.safaribooksonline.com/library/view/programming-amazon-ec2/9781449303617/ch01s03.html)” coined by Werner Vogels:

> There is no need to distinguish between building and running, and according to Werner Vogels, it is much better than that:
>
> > Giving developers operational responsibilities has greatly enhanced the quality of the services, both from a customer and a technology point of view. The traditional model is that you take your software to the wall that separates development and operations, and throw it over and then forget about it. Not at Amazon. You build it, you run it. This brings developers into contact with the day-to-day operation of their software. It also brings them into day-to-day contact with the customer. This customer feedback loop is essential for improving the quality of the service.
>
> This lesson is interesting, but this particular change in an organization is not always easy to implement.

This shift is concomitant of an increasing importance of continuous integration and deliveries methods. Please note that these ideas are much older than the formalisation of “agile” methodologies, some of them are already present in the NATO Scientific Committee report about software engineering published in … 1968!

While the wording can be overlooked, the short description of the DevOps proposal (this site) mentions “software engineers”:

> Beta Q&A site for software Engineers working on automated testing, continuous delivery, service integration and monitoring, and building SDLC infrastructure.

---

Now if you are looking for a software engineer that can help your team getting started with these methodologies, engage them on this topic. Even if you are not familiar with this topic, following the “You build it! You run it!” slogan you can start from a programming problem and lead the interview towards question about deployment and maintenance of the application.

> **Comments:**
> **username_0**: The confusion is also based on job offers like this: http://stackoverflow.com/jobs/135988/devops-engineer-yellowtail?offset=1&q=devops  
> **username_2**: Yes, there is a lot of people or organizations using “DevOps” as a role. No one can be blamed for being a victim of this and your question is useful to clarify this, so thank you to have asked it, even it will probably finally be closed. I hope you find this answer useful and that you will take the chance to otherwise contribute to this site or use it as an information source!  
> **username_5**: @username_0Moors : your prior (interesting!) comment should be integrated in your actual question ... even if it was only to document your confusion ...  
> **username_0**: @username_5 done  
> **username_1**: Synonym/related "eat your own dog food", don't do something you won't use  

---

### Answer by username_6 on 2017-03-23. Score: 8

At the risk of getting vote down, off-topic or even heresy, I going to tell you,
"Don't listen to the purists telling you that DevOps is not a role."

You are on the right track. **It should fit your company.** That's what matters when hiring.

If you need a DevOps, to work like a DevOps, produce results like DevOps, it is a DevOps.

* Don't let anyone dissuade you otherwise.
* Advertise anyway.
* Interview anyway.
* Hire anyway.

While at that, find out more about DevOps, how the concept can fit into your company, how does the person fits in.

Distill out more about the role you need to fill. Search for questions you can ask. There are plenty of [example](https://www.quora.com/What-are-some-good-interview-questions-for-a-DevOps-position), even if you are not subject matter expert. Some good old-fashioned patience and hardwork.

Do you need an employee? Or freelancer? A jack of all trades? Only you know your company well.

Create your unique culture that is your interpretation of DevOps.

> **Comments:**
> **username_7**: +1 to this. Purists have been hung up on the _devops is not a role_ answer for too long, but the industry, job boards and recruiters have already turned it into a reality, and it's time we accept it for what it is.  

---

### Answer by username_4 on 2017-03-10. Score: 6

"Hiring a DevOps" will be tough because DevOps isn't a role. IF you can find an engineer with software development *and* engineering skills, you're on the right track..

**However**,

Your hiring process will be complicated by a few factors:

1. Site Reliability Engineers (Google's term for admin/engineers with coding skills) are rare
2. Rare skills are expensive
3. Rare skills are... rare.

The good news is you may not need a fully qualified SRE.

Your use case, as it were, is hiring engineers to establish your infrastructure (AWS) and automate deployments (Jenkins.) Those skills are not all that rare, but you may have a challenge finding them in a single person.

You also mention that you yourself don't have those skills. This is a further complicating factor. You don't have the skills necessary to evaluate the skills of your candidates. You must ultimately find a way to develop (or hire, as in an Engineering Manager) the skills needed to manage this type of resource.

> **Comments:**
> **username_1**: That's common for human resource people to not have the skills of the people they are hiring. Usually the best idea is to interview with skilled people to have an evaluation of the candidates  
> **username_0**: I meant to say, I'm a good developer, but I also want to be surrounded with people who excel at other disciplines inside the company eventually, better than mine.  
> **username_1**: @username_0Moors that's a very good idea. Don't bother too much, I'm vocal about what I think about this site, but I'm just one in a crowd. Sorry if I sounded rude btw  

---

### Answer by username_8 on 2017-03-23. Score: 2

There are two possibilities:

1. You need help figuring out what are the changes your company needs to go through on your journey to DevOps.
2. You know what you need and just look to hire people to implement this vision for you.

If you need someone to help you figure out which issues you need to concentrate on, there is a really good company called [DORA](https://devops-research.com) (DevOps Research and Assessment), which is cofounded by Dr. Nicole Forsgren, Jez Humble and Gene Kim. Nicole has run the [State of DevOps](https://puppet.com/resources/whitepaper/2016-state-of-devops-report) survey for years and has been keeping detailed statistics of the industry for years. Jez Humble is a guru of Continuous Delivery and literally wrote [the book](http://a.co/iCdMtDo) on it. Gene Kim is the author of [The Phoenix Project](http://a.co/6ze2QvB) and the last two are co-authors of [The DevOps Handbook](http://a.co/1UiVWxV). DORA provides an [assessment](https://devops-research.com/assessment.html) of your company and help you answer those questions.

If you have a pretty good idea where you need to go and need someone to help you get there, getting a recruitment agency is probably not a good idea at this point. I would suggest to go to DevOps Enterprise [DOES Conference](http://events.itrevolution.com) or local [DevOpsDays Conference](https://www.devopsdays.org) and talk to people in the hallways. Look for recommendations and maybe even open a booth, make a poster about hiring.

Second option would be to come here and start asking those questions in this forum and look for the experts that answer them and get up-voted. Many of those might be actually looking for a job or a challenge. Sometimes even asking questions about your current situation and use case here could point you to the right course of action.


---

### Answer by username_9 on 2017-03-23. Score: 2

I look for a number of things in the people I have hired into this space.

* a minimum of 'ha' level of agile (google shu, ha, ri for agile adoption if you need more)
* technical hands-on experience - coding, automation, etc, but I'm tool and language agnostic
* learning personality - they take the initiative to constantly learn
* inquisitive and not looking to place blame - they can accept failure as a learning lesson
* they are a team player who can trust and be trusted since psychological safety is the number one success factor for high performing teams
* they can coach and mentor - they share their knowledge without being elitist - prima donnas have no place on high performing teams
* they have "enough" social skills since they need to be team members and communicate well

I have yet to find a perfect candidate, so it's always some type of trade-off. In today's world, I looked through 65+ resumes that were "pre-qualified" as candidates by agencies and HR, discarded 50 or more as not meeting my minimum requirements on paper, interviewed 15+, and hired 3. This process took me the better part of 9 months.

> **Comments:**
> **username_1**: And to complement, what I feel missing in your post is a description of what you feel was missing, saying there was some lacks without guidance on how to present things to cover these lacks doesn't help to get a better situation  
> **username_9**: If people do not submit a resume tuned to the job posting minimum requirements then they don't meet my minimum requirement to progress further in the process. If a person really wants to be considered for a position then they need to show it with some effort on their part. As a hiring manager it is my point of view that counts because I know what I'm looking for.  
> **username_1**: Sounds like a good advice to add 'posting a resume tuned to the job'. That's easier to check than guessing your requirement on the paper. if your requirements are the bullet points above then maybe ´my requirements above on the paper' could be a better wording  
> **username_9**: Unfortunately the bulleted list above is what I need to discern from the interview. My minimum requirements and my preferred requirements are clearly spelled out in the job postings I make, and they change based on what skills I need to round out a team. The applicant usually gets an interview if they meet the minimum requirements and almost always if they meet the minimum requirements plus some of the preferred requirements.  While this may seem vague, I am quite specific in each job posting I make as to what I'm looking for in a successful candidate.  
> **username_9**: There is a percentage of candidates that falsely claim what's on their resume that simple fact checking uncovers. These applicants never get an interview with me. Example: claim you have a Scrum Alliance certification, since I have a few of their certifications, I can log in and check yours.  
> **username_5**: I think you should try to integrate/move your comments in your actual answer.  

---

### Answer by username_10 on 2017-06-27. Score: 1

Aside other questions I believe the following answer is yet missing - I want to summarize what I have learned so far in a mostly humble tone:

Introducing DevOps skills to your team is probably not enough (that is to consider that you cannot hire a DevOps)! (Like asking on a lower level what are best tools to make things work, here you seem to want your organization work).

The real question is: what is your oganizations digital transformation strategy and **how much good DevOps will help you to create more customer value and reduce your costs**, still having a good climate?

DevOps reveals the need for change, and change requires taking responsibility.

Imagine a situation were working DevOps might introduce pressure on other teams. DevOps is sometimes a result of evolution from Agile and Continous Integration - what are your assets here?


---

