<p>Yes, there absolutely should be an assessment, however it would be a good idea to agree upfront with one of the few DevOps people you know to validate the content and results.</p>

<p>Regarding the contents of the assessment, there are some questions still remaining after your edits. Key one is how your operations are done. Possible options are: you already have someone doing your server infrastructure and operations and looking for a purely CI/CD person, or you do not have good operations support (i.e. developers doing that and you're unhappy) and you need DevOps person to do server management too. Note, that if it's the later case, you'd probably need more than person over time but you need somebody senior to start with.</p>

<p>Note, that for larger organizations you'd find more specialization within DevOps (i.e. things like Release Management, DevSecOps and others), but for smaller companies those two - CI/CD vs Infra Operations are two main ones in my experience. You still need to keep those differences in mind if you're considering taking someone from a larger company.</p>

<p>Now, after answering those questions, you need to first establish the seniority level of a person you're looking to hire. If it's your first DevOps person - you would probably want somebody more senior, but it depends on other people in your existing team. Next you scope your assessment to the on-job tasks. My take - always give take-at-home assignments, I usually give it to candidates over weekend and I make sure they take no more than 3-4 hours.</p>

<p>For CI/CD case you may ask them for a simple CI pipeline in their tool of choice, built from scratch over some sample project. You should add extra questions about failure handling, parallelizing, caching, handling of automation tests.</p>

<p>For CI/CD + operations case you should add tasks about shell scripting, cloud security, terraform.</p>

<p>Also for the first DevOps / senior person it's always a good idea to add some questions about interacting with other teams. I.e. what developers would need to do and how the interaction process with them should be built.</p>

<p>Again, start with one of the few DevOps people you know and get them onboard as a consultant to assess and hire that first person, otherwise you're taking a lot of chances there - and DevOps is a pretty sensitive part of your business.</p>

CC BY-SA 4.0
2020-05-04T14:08:35.357Z
2020-05-04T14:08:35.357Z
taleodor
<p>Yes. Although DevOps is a culture and not a role, one should assess the mindset and technical skills of a candidate.</p>
<p>At my previous work we conducted two interviews. The first one was a conversation about the mindset. If my colleague and I were positive then we offered the candidate the possibility to prepare a demo for the second interview. He or she could choose to demonstrate an autodeploy or the candidate could come up with another proposal.</p>
<p>During the second and technical interview, the candidate had to bring his or her laptop and demonstrate what he or she prepared. During the demo, my colleague and I were asking questions. By doing this we got an impression about the technical knowledge as well.</p>
<blockquote>
<p>We need to hire a DevOps Engineer to bootstrap our all DevOps
process/culture</p>
</blockquote>
<p>In my opinion, your current Developers should deploy the code they created, themselves. &quot;You build it, you run it.&quot;. Although it can be hard to get started with CI, the documentation of various platforms like, Gitlab, Bitbucket, Jenkins is comprehensive and they can implement it. If you hire some person for this, you will create silos and it will be a negative effect on a DevOps culture. It will promote a &quot;throw it over the wall mindset&quot; and &quot;What I am?&quot;, &quot;You are IT of Dev&quot; mindset.</p>
<p>The more I think about the question, the more I think you just should hire a freelancer for a couple of sprints that motivates and instructs developers to implement the pipelines themselves. Once a CI is running well, it can be applied to all projects and the person or freelancer you are trying to hire will be superfluous.</p>

CC BY-SA 4.0
2020-05-04T19:16:24.100Z
2021-08-29T11:38:06.267Z
2021-08-29T11:38:06.267Z
030
<p>We're a software team currently trying to hire a DevOps Engineer.</p>

<p>We have an assessment for Software Developer candidates and we're currently evaluating the idea of having an assessment for our DevOps Engineer candidates. Since we have not hired DevOps people before and barely know a few, it would help us greatly.</p>

<p>What would be your advice ? 
If you support there should be an assessment, then what would be the content ?</p>

<h3>EDIT(Additional Info):</h3>

<ul>
<li>We need to hire a DevOps Engineer to bootstrap our all DevOps process/culture.</li>
<li><p>We have more than 100 servers. Around 20 different apps on them.</p></li>
<li><p>We want him/her to;</p>

<ul>
<li>Install a main devops tool like Jenkins or Teamcity </li>
<li>Build the pipelines for all this apps and servers</li>
<li>CIntegration, CDelivery, CDeployment depending on what app does</li>
<li>help migrate to Linux and/or docker</li>
</ul></li>
</ul>

<h3>About assessment</h3>

<ul>
<li>It must be about building and deploying a few apps interacting with each other to different targets with different configurations.</li>
</ul>

<h3>EDIT 2(answers):</h3>

<p>Thanks for answers. While reading them, I'll answer the questions to make the backstory clearer.</p>

<p>@taleodor</p>

<ul>
<li>Developers including me are doing provisioning/build/deployments. We're very unhappy about that.</li>
<li>Unfortunately, we can only hire one person for all our expectations. 

<ul>
<li>We have plenty of time to put everything together, so it should not be problem for anyone who's willing to do all the stuff.</li>
</ul></li>
<li>Assignment will be take-at-home and candidates will be given a few days to complete. No problem about that. After all assessment is complementary to interview.</li>
<li>I know a few DevOps people. I may get their help for evaluating assessments.</li>
</ul>

<p>@030</p>

<p>I agree the devs automating their stuff is much better than another person doing that. But we have a big backlog about devops. We need someone to show us the way while doing the bulk of it himself/herself. We are not considering to totally forget the process. We want exact opposite: we want to do things right but we don't know where to start and don't have time.</p>

<p>I installed Jenkins. Set up pipelines for some of the projects. But I am a senior developer. Neither me nor my executive wants my all time spent on this.</p>

<h3>EDIT 3(What I came up with):</h3>

<p>This is roughly the assignment I brought together. What do you think ? What else can be here ?</p>

<ul>
<li>Install Jenkins on a platform on your choice</li>
<li>Dockerize .net project given.</li>
<li>Build two pipelines with unit test automation.</li>
<li>Build and host database.</li>
<li>You must be delivering us your scripts and an account to jenkins.</li>
</ul>

CC BY-SA 4.0
2020-05-04T09:33:38.587Z
Hi! This sounds like quite an open-ended question, making it very difficult to answer. Can you edit it please, with some details of what exactly you are trying to achieve? it's safe to assume that anyone you plan to hire should be assessed - the real question is _how_ or _what_ should be assessed? Perhaps indicate what your focus is - building a team, automation, etc.
Bruce Becker
CC BY-SA 4.0
2020-05-09T12:27:06.077Z
you risk hiring an "ops" person who "knows Jenkins" and them spending their days clicking on the web interface. this doesn't actually work well as it creates a silo containing a single person doing menial work. A better approach is to hire someone who is a developer who knows how to do automation with tools like Jenkins and ansible etc and ask them to write scripts and templates that make it easy for others to "setup pipelines". if they are good at their job they should eventually run out of interesting work. at which point they should be allowed to develop regular features on your system.
simbo1905
<project-management><software-engineering><human-resources>
Should I give an assessment to DevOps Candidate
Doruk
# Should I give an assessment to DevOps Candidate

(Asked by: username_0 on 2020-05-04)

We're a software team currently trying to hire a DevOps Engineer.

We have an assessment for Software Developer candidates and we're currently evaluating the idea of having an assessment for our DevOps Engineer candidates. Since we have not hired DevOps people before and barely know a few, it would help us greatly.

What would be your advice ?
If you support there should be an assessment, then what would be the content ?

### EDIT(Additional Info):

* We need to hire a DevOps Engineer to bootstrap our all DevOps process/culture.
* We have more than 100 servers. Around 20 different apps on them.
* We want him/her to;

  + Install a main devops tool like Jenkins or Teamcity
  + Build the pipelines for all this apps and servers
  + CIntegration, CDelivery, CDeployment depending on what app does
  + help migrate to Linux and/or docker

### About assessment

* It must be about building and deploying a few apps interacting with each other to different targets with different configurations.

### EDIT 2(answers):

Thanks for answers. While reading them, I'll answer the questions to make the backstory clearer.

@username_3

* Developers including me are doing provisioning/build/deployments. We're very unhappy about that.
* Unfortunately, we can only hire one person for all our expectations.
  + We have plenty of time to put everything together, so it should not be problem for anyone who's willing to do all the stuff.
* Assignment will be take-at-home and candidates will be given a few days to complete. No problem about that. After all assessment is complementary to interview.
* I know a few DevOps people. I may get their help for evaluating assessments.

@username_4

I agree the devs automating their stuff is much better than another person doing that. But we have a big backlog about devops. We need someone to show us the way while doing the bulk of it himself/herself. We are not considering to totally forget the process. We want exact opposite: we want to do things right but we don't know where to start and don't have time.

I installed Jenkins. Set up pipelines for some of the projects. But I am a senior developer. Neither me nor my executive wants my all time spent on this.

### EDIT 3(What I came up with):

This is roughly the assignment I brought together. What do you think ? What else can be here ?

* Install Jenkins on a platform on your choice
* Dockerize .net project given.
* Build two pipelines with unit test automation.
* Build and host database.
* You must be delivering us your scripts and an account to jenkins.

**Tags:** project-management, software-engineering, human-resources

> **Comments:**
> **username_1**: Hi! This sounds like quite an open-ended question, making it very difficult to answer. Can you edit it please, with some details of what exactly you are trying to achieve? it's safe to assume that anyone you plan to hire should be assessed - the real question is _how_ or _what_ should be assessed? Perhaps indicate what your focus is - building a team, automation, etc.  
> **username_2**: you risk hiring an "ops" person who "knows Jenkins" and them spending their days clicking on the web interface. this doesn't actually work well as it creates a silo containing a single person doing menial work. A better approach is to hire someone who is a developer who knows how to do automation with tools like Jenkins and ansible etc and ask them to write scripts and templates that make it easy for others to "setup pipelines". if they are good at their job they should eventually run out of interesting work. at which point they should be allowed to develop regular features on your system.  

---

## 2 answers

### Answer by username_3 on 2020-05-04. Score: 3 | Accepted answer

Yes, there absolutely should be an assessment, however it would be a good idea to agree upfront with one of the few DevOps people you know to validate the content and results.

Regarding the contents of the assessment, there are some questions still remaining after your edits. Key one is how your operations are done. Possible options are: you already have someone doing your server infrastructure and operations and looking for a purely CI/CD person, or you do not have good operations support (i.e. developers doing that and you're unhappy) and you need DevOps person to do server management too. Note, that if it's the later case, you'd probably need more than person over time but you need somebody senior to start with.

Note, that for larger organizations you'd find more specialization within DevOps (i.e. things like Release Management, DevSecOps and others), but for smaller companies those two - CI/CD vs Infra Operations are two main ones in my experience. You still need to keep those differences in mind if you're considering taking someone from a larger company.

Now, after answering those questions, you need to first establish the seniority level of a person you're looking to hire. If it's your first DevOps person - you would probably want somebody more senior, but it depends on other people in your existing team. Next you scope your assessment to the on-job tasks. My take - always give take-at-home assignments, I usually give it to candidates over weekend and I make sure they take no more than 3-4 hours.

For CI/CD case you may ask them for a simple CI pipeline in their tool of choice, built from scratch over some sample project. You should add extra questions about failure handling, parallelizing, caching, handling of automation tests.

For CI/CD + operations case you should add tasks about shell scripting, cloud security, terraform.

Also for the first DevOps / senior person it's always a good idea to add some questions about interacting with other teams. I.e. what developers would need to do and how the interaction process with them should be built.

Again, start with one of the few DevOps people you know and get them onboard as a consultant to assess and hire that first person, otherwise you're taking a lot of chances there - and DevOps is a pretty sensitive part of your business.


---

### Answer by username_4 on 2020-05-04. Score: 3

Yes. Although DevOps is a culture and not a role, one should assess the mindset and technical skills of a candidate.

At my previous work we conducted two interviews. The first one was a conversation about the mindset. If my colleague and I were positive then we offered the candidate the possibility to prepare a demo for the second interview. He or she could choose to demonstrate an autodeploy or the candidate could come up with another proposal.

During the second and technical interview, the candidate had to bring his or her laptop and demonstrate what he or she prepared. During the demo, my colleague and I were asking questions. By doing this we got an impression about the technical knowledge as well.

> We need to hire a DevOps Engineer to bootstrap our all DevOps
> process/culture

In my opinion, your current Developers should deploy the code they created, themselves. "You build it, you run it.". Although it can be hard to get started with CI, the documentation of various platforms like, Gitlab, Bitbucket, Jenkins is comprehensive and they can implement it. If you hire some person for this, you will create silos and it will be a negative effect on a DevOps culture. It will promote a "throw it over the wall mindset" and "What I am?", "You are IT of Dev" mindset.

The more I think about the question, the more I think you just should hire a freelancer for a couple of sprints that motivates and instructs developers to implement the pipelines themselves. Once a CI is running well, it can be applied to all projects and the person or freelancer you are trying to hire will be superfluous.


---

