Get started

Quality Assurance engineering is all about making sure that the software you build meets the acceptance criteria.

It’s a core role in every agile engineering team, and as the market focuses more on quality as a differentiator, it’s an exciting time to be in QA.

At Codility we care a lot about QA, and like many engineering teams we favor a continuous integration system, with end-to-end automated tests to ensure our tech recruitment platform works properly.

“With distributed teams and version control becoming commonplace, QA engineers are crucial for ensuring merges will not break existing code. They save the engineering team a ton of time and allow them to focus more on building the app.”

Michal Lipinski, QA, Codility

QA in a nutshell:

Before shipping a new feature or application to end-users, it needs to be tested to make sure it works as intended. QA Engineers are the proxy between your engineering team and your end-users, spending their time verifying whether the application works as it’s supposed to – even factoring in the most invisible, edge-cases. They partner with Product Managers to provide valuable information about the state of the application and work within engineering teams to make sure their work is of sufficient quality.

What sets great QA Engineers apart?

It takes more than test automation and Selenium knowledge to have great QA Engineer skills. The best QA engineers are master communicators with a strong eye for details. They need to be able to clearly explain bugs and issues to engineering teams, while also speaking with client-facing parts of the team to understand the expected user behavior. They should be familiar with xpath, timeouts, edge cases, API, and be able to read existing code as they may need to design tests according to implementation.

What questions should be considered in the interview process?

  1. How good is the candidate at understanding the end-users’ perspective?
  2. When code testing, how does the candidate think through edge cases and consider all possibilities in the code?
  3. A great QA engineer never settles on flaky tests. How skilled is your candidate at ironing out kinks?
  4. Does the candidate have a hunger to keep improving their code testing and test automation skills? How do they learn?

Using Codility to assess QA Engineer skills in the interview process

We’ve recently shipped a suite of tasks designed to assess candidates on the core skills a QA engineer needs. These tasks provide a way to screen or interview candidates in a way that’s reflective of their typical day-to-day in an engineering team. The candidate will code testing to verify whether the page meets all the acceptance criteria and spots all of the problems that could come up with the page. When paired with a coding task (in the tech they use – ie. Python or Java) or a QA knowledge question, you’ll get a comprehensive candidate test report to help your hiring team decide which candidates to advance in the interview process.

If you’d like to try our latest QA Tasks or learn about our tech recruitment platform, take a tour here.

Marketing Specialist at Codility, Jeff is passionate about empowering hiring teams to connect with candidates. He draws on his own experiences as a recruiter to create meaningful content. Outside of work, you can find him on the soccer field or catching the latest Sci-Fi flick.

Connect on LinkedIn