{"id":999882163,"date":"2013-09-20T13:39:00","date_gmt":"2013-09-20T13:39:00","guid":{"rendered":"https:\/\/dice.npgdev.com\/?p=691786941"},"modified":"2013-09-20T13:39:00","modified_gmt":"2013-09-20T13:39:00","slug":"quality-assurance-engineer","status":"publish","type":"post","link":"https:\/\/dice.npgdev.com\/hiring\/recruitment\/quality-assurance-engineer","title":{"rendered":"Tech Hiring Guide: Quality Assurance Engineer"},"content":{"rendered":"

Return to Technical Hiring Guide<\/a><\/p>\n

QA engineers are almost always on the software-building side of the organization, and are responsible for making sure that software meets the quality bar. Their responsibilities include testing software by using it (like you do when you visit a website and click around), and writing programs to automate various tasks or tests for the system. Some of these roles may require very little coding or scripting knowledge, and others may require a lot \u2013 it really depends on the organization and software they are testing. Regardless, strong attention to detail is important. Many QA engineers are responsible for coming up with test plans and test cases (imagine a big list of everything you would need to test to make sure something worked), as well as executing these plans. People in this role should know how to break things, and be rigorous and thorough. This role tends to involve a lot of communication with engineers, designs, and product people to verify functionality, so they should also be a good team player with strong written and verbal skills. Questions for Quality Assurance Engineers:<\/span><\/strong><\/p>\n