There’s no denying that the world is in constant flux. Thanks to the web, automation, and the data processing abilities of modern computers, the border between humans and machines has become fuzzy. How does it affect IT and QA testing in particular? And finally, which QA skills make great QA testers well, great?
The ideal set of QA skills
As we become more dependent on AI and automation, the role of QA testers has changed too. Does an ideal QA tester even exist? Probably not. However, here are the QA skills commonly shared by great QA testers: Read More
Have you ever spent your free time trying to usher a small village of farmers into a space-faring people? It sounds like you’ve played Civilization. If you have spent the last twenty-five years doing something else with your time, Civilization is a series of turn-based strategy games which is famous for a number of things, one of them being its complex technology trees.
The game works more or less like real life. In order to use an advanced technology, you need first make the discoveries that this new technology is built on. So before building a ship, you need to master mathematics and astronomy. In other words, discovering new technologies opens the doors to the further advancement of your civilization.
Civilization isn’t the only place where you can see skills improve in a series of logical steps. Software developers, whether they realize it or not, experience a similar skill progression as they develop in their career. It is no surprise then that the intersection of the Venn Diagram of software developers and Civilization Players is pretty large. This brings us to competency mapping which is based on the same premise: progress built on a comprehensive series of logical steps (as seen in Civilization). Read More
One of the most important but still ignored aspects of hiring a software developer is verifying how candidate is dealing with the code and whether is able to express their thoughts with particular programming language. Usually in IT recruitment we do it by asking candidate to write some code solving particular problem. Candidate can do it alone or as a pair programming with the recruiter (Hit the bull’s eye with coding tests in natural environment [case study]). We do it because writing code is one of the most important things developers do on a daily basis. However we should also remember that developers much more often read than write the source code. So we should not forget about verifying if candidate is able to quickly analyse and understand some code snippets. We can simply show some code printouts or (even better) give IDE with some project and ask questions related to what is happening here. That’s where code review challenge is really helpful. Read More
It can be a serious problem if you want to hire a Java developer but haven’t got a clue what to look for. You can search through a candidate’s LinkedIn profile or a resume all you want. If you can’t tell your JPA from your Gradel you won’t be able to tell if the candidate is a good fit for the position you want to fill. I wrote this article to gather all of the information you need if you are an IT recruiter searching for programmers with Java skills. Read More
You are looking for a person who can not only code, but is also able to resolve your problems and meet your expectations. You post a job offer on a couple of recruiting portals, do a headhunt through LinkedIn or networking and contact recruiting agencies to get as many promising candidates as you can. Every resume or LinkedIn profile states that your candidate can program in specific languages and in certain frameworks. Read More
After publishing a post concerning most common don’ts of hiring programmers we received some questions regarding programming tasks and the way we should verify coding skills.
From my long-term work experience I’ve got a lot of consulting practice on recruiting process of programmers in some of the biggest IT companies based mostly in central-eastern Europe.
We have written a lot on technical interviews. Check out The ultimate guide to the technical interview.