Answers: <p>You might want to check the accepted answer to this question:
  <a href="https://devops.stackexchange.com/questions/797/why-shouldnt-i-try-to-hire-a-devops-engineer">Why shouldn&#39;t I try to hire a &#39;DevOps Engineer&#39;?</a></p>
  
  <p>Or maybe the article "<a href="https://techbeacon.com/7-devops-roles-you-need-succeed" rel="nofollow noreferrer">7 DevOps roles you need to succeed</a>", which includes these (critical?) roles:</p>
  
  <ol>
  <li>DevOps evangelist</li>
  <li>Release manager</li>
  <li>Automation architect</li>
  <li>Software developer/tester</li>
  <li>Experience assurance (XA) professional</li>
  <li>Security engineer</li>
  <li>Utility technology player</li>
  </ol>
  
Answers: CC BY-SA 3.0
Answers: 2017-08-31T14:28:39.717Z
Answers: Hey Mr. "J" ... the article you linked to doesn't mention a role like "BA for DevOps", any idea why not? And/or what such "BA for DevOps" actually means?
Answers: Pierre.Vriens
Answers: CC BY-SA 3.0
Answers: 2017-08-31T15:05:28.000Z
Answers: Links are helpful, but it's encouraged that you [provide context](https://devops.stackexchange.com/help/how-to-answer) and quote relevant sections, plus add your own commentary. See: [Your answer is in another castle: when is an answer not an answer?](https://meta.stackexchange.com/questions/225370/your-answer-is-in-another-castle-when-is-an-answer-not-an-answer) for the current guidelines for answering with a link.
Answers: Aurora0001
Answers: CC BY-SA 3.0
Answers: 2017-08-31T15:16:39.457Z
Answers: Hey Mr. "J" (again) ... please QA-review the edit I applied to your post, trying to address the comment (and possibly downvote?) from @Aurora0001 ... feel free to rollback if you don't like my edit at all ... PS: where is the DevOps "***Manager***" in that article (= the one who doesn't have to do anything, if everybody else does his/her job, except from approving budgets and things like that)?
Answers: Pierre.Vriens
Answers: CC BY-SA 3.0
Answers: 2017-08-31T17:33:41.837Z
Answers: Hi @Pierre.Vriens - thanks for editing. PM might be quite unrelated to DevOps context. DevOps BA is sth I would like to establish. Give me 15 minutes to add two relevant links here. In short, BA (Business Analyst) in scrum terms means product owner, e.g. CI/CD infrastructure is an internal organizational  product.
Answers: Ta Mu
Answers: CC BY-SA 3.0
Answers: 2017-08-31T17:48:38.923Z
Answers: ^^ [1] DevOps for PM https://www.agilealliance.org/resources/sessions/a-gentle-introduction-to-devops-project-manager-edition/  [2] https://www.google.de/amp/s/amp.reddit.com/r/ITCareerQuestions/comments/4fz5vf/in_the_age_of_devopscloudautomation_where_does/
Answers: Ta Mu
Answers: CC BY-SA 3.0
Answers: 2017-08-31T13:56:54.630Z
Answers: 2017-08-31T15:14:18.180Z
Answers: 2017-08-31T15:14:18.180Z
Answers: Ta Mu
Answers: <p>An <strong><em>architect</em></strong> is somebody who thinks and creates designs.</p>
  
  <p>A <strong><em>consultant</em></strong> is somebody who gets hired for things like "Teach us how to do so and so", or to answer questions like "What's your opinion about this design?".</p>
  
  <p>An <strong><em>engineer</em></strong> is the one who is objective oriented and pragmatic, something along the lines like "<em>How can I get that design (created by the architect, and validated by the consultant) implemented and make it work"?</em>.</p>
  
  <p>Their <em>salaries</em> may vary (there are cheap and expensive ones), same for <em>seniority</em> (there are juniors and seniors, while everybody starts as junior, not all of them ever make it to senior). And <em>job demand</em> is pretty variable (by region, over time, economical factors, depending on hypes, etc).</p>
  
  <p>BTW, it doesn't really matter what the actual "subject" is, it could be "IT", it could be "Road Construction", or it could even be "DevOps" ...</p>
  
  <p>PS: What's in a name (or jobtitle), how about a <strong><em>DevOps BA</em></strong>, as shown in <a href="https://www.linkedin.com/feed/update/activity:6309024601095704576/" rel="noreferrer">this post</a> ...</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-08-31T14:47:31.670Z
Answers: Nitpicking about the engineer and object oriented link here (one does not necessarily implies the other) on what is overall an excellent answer !
Answers: Newtopian
Answers: CC BY-SA 3.0
Answers: 2017-08-31T14:54:26.917Z
Answers: @Newtopian merci for the comment, though I'm not sure what "Nitpicking" means (and I don't have a dictionary handy ...). About Object Oriented: that's like in *OOP*, aka Object Oriented Programming, whereas the "Object" is to get the "Programming" done ... (the definition I was ever given by an old school mainframe programmer ...).
Answers: Pierre.Vriens
Answers: CC BY-SA 3.0
Answers: 2017-08-31T15:03:26.613Z
Answers: nitpicking --> "pinailler", "Trébucher sur les fleurs du tapis", "Chercher des poux" etc  as in I was the one doing the nitpicking here pointing this out.  I see now what you meant with Object Oriented and it makes perfect sense.  Might I suggest Objective Oriented as to disambiguate from the programming paradigm OOP towards which my first thoughts went to when I read your post.
Answers: Newtopian
Answers: CC BY-SA 3.0
Answers: 2017-08-31T15:06:45.810Z
Answers: Hey @Newtopian : please go ahead and suggest an edit to my post (I'll probably approve it) ... PS, I found my dictionary ... you mean "***muggezifterij***" (your turn to go find a Dutch dictionary if you want to QA-test my translation ...)
Answers: Pierre.Vriens
Answers: CC BY-SA 3.0
Answers: 2017-08-31T15:12:38.247Z
Answers: Tests passed... 100% coverage and approved for production !
Answers: Newtopian
Answers: CC BY-SA 3.0
Answers: 2017-08-31T15:20:07.913Z
Answers: Merci @Newtopian ... also for the suggested edit ... as you may have noticed: I just issued the final (only in this case ...) approval of it.
Answers: Pierre.Vriens
Answers: CC BY-SA 3.0
Answers: 2017-08-31T14:07:33.940Z
Answers: 2017-08-31T15:17:06.783Z
Answers: 2017-08-31T15:17:06.783Z
Answers: Pierre.Vriens
Body: <p>What is the difference between DevOps engineer Vs DevOps consultant Vs DevOps architect?</p>
  
  <p>Considering Role wise &amp; Salary wise &amp; Seniority wise &amp; job demand wise, etc.</p>
  
Tags: <terminology>
Title: What is the difference between DevOps engineer Vs DevOps consultant Vs DevOps architect?
UserDisplayName: Ashish Karpe
ThreadText: # What is the difference between DevOps engineer Vs DevOps consultant Vs DevOps architect?
  
  (Asked by: username_0 on 2017-08-31)
  
  What is the difference between DevOps engineer Vs DevOps consultant Vs DevOps architect?
  
  Considering Role wise & Salary wise & Seniority wise & job demand wise, etc.
  
  **Tags:** terminology
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2017-08-31. Score: 16 | Accepted answer
  
  An ***architect*** is somebody who thinks and creates designs.
  
  A ***consultant*** is somebody who gets hired for things like "Teach us how to do so and so", or to answer questions like "What's your opinion about this design?".
  
  An ***engineer*** is the one who is objective oriented and pragmatic, something along the lines like "*How can I get that design (created by the architect, and validated by the consultant) implemented and make it work"?*.
  
  Their *salaries* may vary (there are cheap and expensive ones), same for *seniority* (there are juniors and seniors, while everybody starts as junior, not all of them ever make it to senior). And *job demand* is pretty variable (by region, over time, economical factors, depending on hypes, etc).
  
  BTW, it doesn't really matter what the actual "subject" is, it could be "IT", it could be "Road Construction", or it could even be "DevOps" ...
  
  PS: What's in a name (or jobtitle), how about a ***DevOps BA***, as shown in [this post](https://www.linkedin.com/feed/update/activity:6309024601095704576/) ...
  
  > **Comments:**
  > **username_4**: Nitpicking about the engineer and object oriented link here (one does not necessarily implies the other) on what is overall an excellent answer !  
  > **username_2**: @username_4 merci for the comment, though I'm not sure what "Nitpicking" means (and I don't have a dictionary handy ...). About Object Oriented: that's like in *OOP*, aka Object Oriented Programming, whereas the "Object" is to get the "Programming" done ... (the definition I was ever given by an old school mainframe programmer ...).  
  > **username_4**: nitpicking --> "pinailler", "Trébucher sur les fleurs du tapis", "Chercher des poux" etc  as in I was the one doing the nitpicking here pointing this out.  I see now what you meant with Object Oriented and it makes perfect sense.  Might I suggest Objective Oriented as to disambiguate from the programming paradigm OOP towards which my first thoughts went to when I read your post.  
  > **username_2**: Hey @username_4 : please go ahead and suggest an edit to my post (I'll probably approve it) ... PS, I found my dictionary ... you mean "***muggezifterij***" (your turn to go find a Dutch dictionary if you want to QA-test my translation ...)  
  > **username_4**: Tests passed... 100% coverage and approved for production !  
  > **username_2**: Merci @username_4 ... also for the suggested edit ... as you may have noticed: I just issued the final (only in this case ...) approval of it.  
  
  ---
  
  ### Answer by username_1 on 2017-08-31. Score: 4
  
  You might want to check the accepted answer to this question:
  [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)
  
  Or maybe the article "[7 DevOps roles you need to succeed](https://techbeacon.com/7-devops-roles-you-need-succeed)", which includes these (critical?) roles:
  
  1. DevOps evangelist
  2. Release manager
  3. Automation architect
  4. Software developer/tester
  5. Experience assurance (XA) professional
  6. Security engineer
  7. Utility technology player
  
  > **Comments:**
  > **username_2**: Hey Mr. "J" ... the article you linked to doesn't mention a role like "BA for DevOps", any idea why not? And/or what such "BA for DevOps" actually means?  
  > **username_3**: Links are helpful, but it's encouraged that you [provide context](https://devops.stackexchange.com/help/how-to-answer) and quote relevant sections, plus add your own commentary. See: [Your answer is in another castle: when is an answer not an answer?](https://meta.stackexchange.com/questions/225370/your-answer-is-in-another-castle-when-is-an-answer-not-an-answer) for the current guidelines for answering with a link.  
  > **username_2**: Hey Mr. "J" (again) ... please QA-review the edit I applied to your post, trying to address the comment (and possibly downvote?) from @username_3 ... feel free to rollback if you don't like my edit at all ... PS: where is the DevOps "***Manager***" in that article (= the one who doesn't have to do anything, if everybody else does his/her job, except from approving budgets and things like that)?  
  > **username_1**: Hi @username_2 - thanks for editing. PM might be quite unrelated to DevOps context. DevOps BA is sth I would like to establish. Give me 15 minutes to add two relevant links here. In short, BA (Business Analyst) in scrum terms means product owner, e.g. CI/CD infrastructure is an internal organizational  product.  
  > **username_1**: ^^ [1] DevOps for PM https://www.agilealliance.org/resources/sessions/a-gentle-introduction-to-devops-project-manager-edition/  [2] https://www.google.de/amp/s/amp.reddit.com/r/ITCareerQuestions/comments/4fz5vf/in_the_age_of_devopscloudautomation_where_does/  
  
  ---
  
  