Ygtjki

Context: As been involved in QA hiring positions from last couple of years in different companies, I have been seeing the trend as QA is getting more and more technical.Now it is reaching to a point where line is getting blurred between QA & Developer in teams working on cutting edge technologies.On the other hand communication has always been and will be important for QA in fact for any position in the agile teams.

I have always observed a strong co-relation between communication & technical skills. In general candidates with higher technical skills are not super communicators and on the other hand excellent communicators are generally not very good technically.Although exceptions always exist but they are few and nobody doubts hiring them!

Dilemma :A lot of times been in dilemma situations where between two candidates it becomes hard to choose where one is excellent communicator vs. other is technically superb but not vice versa.

Question: How to take a call when get into these difficult situations of selecting QA candidates where one is excellent in communications and other is technically expert?

It depends, mainly on the current skill gaps of the team. I would map them, before you make an decision. You could try the Agile Skills Project as it covers all needed skills for a software engineering team.

Technical skills are becoming more important for Testers. I believe we can teach technical skills to everyone who is smart, but not everyone enjoys them. So you want to hire people who like programming, scripting and or dev-ops like work. If your testers need to convince developers to do more test-automation they need the tech-skills for credibility as well.

Communication skills are important in any cross-functional team. I agree they are harder to train, so having a bit of talent here might help.

User-centric skills I do think a third skill is more important. A more high level overview skill. Understanding the domain and how combined features benefit the stakeholders. Bringing a user-centric mindset versus the building mindset of the other engineers in the team.

Personality: We also tend to take personality categories into account. Teams with a lot of different personalities tend to be more successful than teams with a lot of the same type people. We use the short 16personalities test during inteviews. This is not a hard requirement, but it influences our hiring decisions.

It depends who you are looking for, what skills your team needs. In my experience soft skills are much harder to learn then technical skills. Especially if you start to learn those later in your career. One of prominent example Linus Torvalds.

I always choose people who are willing to learn new things(I test it) and who know difference between good and bad. Basically it is about mindset and ethics. If candidate covers those two requirements, I hire even if person has no work experience. Important: do not mix promises with potential.

In my point of view, the communication skill is more important than technical skills, if a person has a lot of technical knowledge but does not know how to express or communicate with others is merely waste. Because he doesn't know how to express his thoughts or how to enable others to understand his thoughts and the person who has communication skills can able to express his thoughts and make others understand he can gain technical skill later, it´s not a big deal for that person.

Actually it depends on the roles and responsibilities of the post you are hiring for.

However, if a person is passionate, dedicated and quick learner, he will improve on the area in which he lacks(technical or communication).

But you also have to keep in mind that any of the above skills will take some amount of time, so if it is feasible then you can make decision accordingly.