<p>Understand that the term <strong>DevOps</strong> refers to both a <em>Strategies</em> and <em>Tactics</em>.<br>
For instance, the <em>strategies</em> of Continuous deployment and Consistent development/production environment.<br>
The <em>tactics</em> may be using Kubernetics for deployment to the cluster with Docker for development/production environment.<br>
With that said, a DevOps shop will likely use Kubernetics and Docker as their tactical tools and would look for people with those skillsets.</p>

<p><strong>ALSO</strong>, they would look for people who are a CULTURAL fit who would work well in a collaborative environment.  If your background is let's say operational and your not open to learning programming skills(or learn what the programmers need), don't take ownership of a project or work well in a team...you will <strong>NOT</strong> be a fit for the company (<em>you won't get hired</em>).</p>

<p>As far as the best place to find a DevOps related job?</p>

<p>I would look at going to a DevOps <a href="https://meetup.com/" rel="nofollow noreferrer">Meetup</a>, go to trainings/seminars where DevOps tactics and tools are taught (i.e. Docker, Vagrant, Ansible, Kubernetics, etc.), look for certain keywords in the posts such as <a href="https://en.wikipedia.org/wiki/Site_Reliability_Engineering" rel="nofollow noreferrer">SRE (Site Reliability Engineer)</a>, Systems Automation, etc... and do some research on companies that are moving to or have <a href="https://techbeacon.com/10-companies-killing-it-devops" rel="nofollow noreferrer">embraced DevOps Strategy</a>.</p>

<p>If you understand these things, I believe it will give you a great advantage at landing a job in one of those companies.</p>

CC BY-SA 4.0
2018-12-19T04:06:56.580Z
2018-12-19T04:06:56.580Z
Roadkillon101
<p>Companies either have straight-away openings for DevOps Engineers, either under this specific title or (since the title is a bit misplaced if you really think about what it means in the opinion of some people); or you can look for positions that have some other title but mention DevOps and similar things (for example, "automation", "tooling", "CI/CD" etc.) in the description.</p>

<p>Or in other words - they find jobs the same way everybody else does. It's not <em>that</em> magical of a job description...</p>

<p>What they look for, in my experience from plenty of interviews, is simply working with all the tooling/automation we have these days, and most times with a focus on doing as little straightaway programming as possible (i.e., programming in the non-DevOps way; domain-based programming). This separates them mainly from developers who <em>also</em> can do the "DevOps" stuff.</p>

CC BY-SA 4.0
2018-12-18T22:19:41.247Z
2018-12-18T22:19:41.247Z
AnoE
<p>It can happen that your next DevOps job finds <em>you</em> if you have a well elaborated LinkedIn profile and patient enough to deal with and filter/process requests.</p>

<p>Though, my market observations are that many offerings are like:</p>

<ul>
<li><p>DevOps Engineers seen as "full stack developer 2.0", that is as an addon to specific developer skill set you can also setup automation pipelines and deploy to production.</p></li>
<li><p>DevOps Engineers seen as "admin 2.0" to build up automated operational infrastructures</p></li>
<li><p>DevOps Engineers seen as "teams glue" i.e. a company resource pool used to fire up slow/less successfull teams, here at least there is an understanding of how important beyond tech also culture/human communication is, too.</p></li>
<li><p>Sometimes you get also a weird skill set list where nobody really knows where it comes from and what exactly the role is expected to deliver. Buzz wording detected.</p></li>
</ul>

<p>Please consider also this post: <a href="https://devops.stackexchange.com/questions/797/why-shouldnt-i-try-to-hire-a-devops-engineer">Why shouldn't I try to hire a 'DevOps Engineer'</a>?</p>

CC BY-SA 4.0
2018-12-19T17:58:00.720Z
2018-12-19T17:58:00.720Z
Ta Mu
<p>Where do DevOp Engineers find their next opportunity? Users Groups, Associations, Job Boards?</p>

<p>What do DevOps look for in their next role?</p>

CC BY-SA 4.0
2018-12-19T18:04:19.547Z
hi and welcome @michaelg! I have allowed myself to give your question a more precise title. Hope that's okay.
Ta Mu
<azure-devops>
Where would DevOps Engineers mostly look for their next opportunity and what would it be?
michaelg
# Where would DevOps Engineers mostly look for their next opportunity and what would it be?

(Asked by: username_0 on 2018-12-18)

Where do DevOp Engineers find their next opportunity? Users Groups, Associations, Job Boards?

What do DevOps look for in their next role?

**Tags:** azure-devops

> **Comments:**
> **username_1**: hi and welcome @username_0! I have allowed myself to give your question a more precise title. Hope that's okay.  

---

## 3 answers

### Answer by username_2 on 2018-12-19. Score: 1

Understand that the term **DevOps** refers to both a *Strategies* and *Tactics*.  
For instance, the *strategies* of Continuous deployment and Consistent development/production environment.  
The *tactics* may be using Kubernetics for deployment to the cluster with Docker for development/production environment.  
With that said, a DevOps shop will likely use Kubernetics and Docker as their tactical tools and would look for people with those skillsets.

**ALSO**, they would look for people who are a CULTURAL fit who would work well in a collaborative environment. If your background is let's say operational and your not open to learning programming skills(or learn what the programmers need), don't take ownership of a project or work well in a team...you will **NOT** be a fit for the company (*you won't get hired*).

As far as the best place to find a DevOps related job?

I would look at going to a DevOps [Meetup](https://meetup.com/), go to trainings/seminars where DevOps tactics and tools are taught (i.e. Docker, Vagrant, Ansible, Kubernetics, etc.), look for certain keywords in the posts such as [SRE (Site Reliability Engineer)](https://en.wikipedia.org/wiki/Site_Reliability_Engineering), Systems Automation, etc... and do some research on companies that are moving to or have [embraced DevOps Strategy](https://techbeacon.com/10-companies-killing-it-devops).

If you understand these things, I believe it will give you a great advantage at landing a job in one of those companies.


---

### Answer by username_1 on 2018-12-19. Score: 1

It can happen that your next DevOps job finds *you* if you have a well elaborated LinkedIn profile and patient enough to deal with and filter/process requests.

Though, my market observations are that many offerings are like:

* DevOps Engineers seen as "full stack developer 2.0", that is as an addon to specific developer skill set you can also setup automation pipelines and deploy to production.
* DevOps Engineers seen as "admin 2.0" to build up automated operational infrastructures
* DevOps Engineers seen as "teams glue" i.e. a company resource pool used to fire up slow/less successfull teams, here at least there is an understanding of how important beyond tech also culture/human communication is, too.
* Sometimes you get also a weird skill set list where nobody really knows where it comes from and what exactly the role is expected to deliver. Buzz wording detected.

Please consider also this post: [Why shouldn't I try to hire a 'DevOps Engineer'](https://devops.stackexchange.com/questions/797/why-shouldnt-i-try-to-hire-a-devops-engineer)?


---

### Answer by username_3 on 2018-12-18. Score: 0

Companies either have straight-away openings for DevOps Engineers, either under this specific title or (since the title is a bit misplaced if you really think about what it means in the opinion of some people); or you can look for positions that have some other title but mention DevOps and similar things (for example, "automation", "tooling", "CI/CD" etc.) in the description.

Or in other words - they find jobs the same way everybody else does. It's not *that* magical of a job description...

What they look for, in my experience from plenty of interviews, is simply working with all the tooling/automation we have these days, and most times with a focus on doing as little straightaway programming as possible (i.e., programming in the non-DevOps way; domain-based programming). This separates them mainly from developers who *also* can do the "DevOps" stuff.


---

