A Good Multitasking

There is only one type of multitasking which is not bad for Developers. In fact, it is damn good.
And that is… Coding along with Testing.

Unfortunately, a very large number of developers treat the Testing activity as not part of their work. 
A large number of Testers think that Testing can start only after developers throw their code above the wall in Tester's compound. 
Most unfortunately many Organizations feel it is the right way of building software.

All these things are not only wrong but almost a crime.

If you really want your team works like a well-oiled engine and ship better value faster, ensure that testing takes place as coding/development progresses.

Even better would be the testing performed by the developers themselves as they go along.
A QA Engineer should be mainly paid for visualizing potential pitfalls as early as possible, writing suitable Test Cases for them, and providing those TCs to developers as early as possible. They should not be paid for catching more bugs, but for allowing fewer bugs to creep in.