A solid example of this is the Test Automation Engineer. Writing all that Ruby code with the cucumber and the gherkin, the Test Automation Engineer has added some test automation tools and testing skills to his repertoire but is still a developer. He works with Quality Assurance to help make sure the application is as bug-free as possible. And, since QA folks usually aren’t developers, he can help in ways that other QA persons can’t by bringing development expertise to the rest of the team.
For more information, visit: https://blog.datarobot.com/ai-for-engineers-how-not-to-be-a-data-scientist?utm_medium=(not%20set)&utm_source=google.com&utm_campaign=(not%20set)&utm_term=(not%20provided)