For those who are tight, QA can be enjoyable. Similar to a buddy of mine who is essentially unable to cook bread without discovering a problem in the toaster. He is well-known. I keep assuring him that it’s “only you” experiencing what’s happening to him. You are the only one who experiences this.

Essentially, your duties include communicating with programmers, tracking issues, and testing software. Additionally, you must monitor any recurrence of bugs, as they typically result from an unauthorized version control merging.

Here’s the problem, though. QA varies from firm to company. There’s no company with comparable requirements or QA. Some commonalities exist, such as version control systems and bug tracking software.

Some companies allow you to learn on the job, but the job usually does not pay very well, but I think that is a fair deal.

Now. I don’t know your background. But I doubt any company will hire someone just off the streets. You need to talk the talk. You are dealing with programmers and it is your job telling them they made a mistake, usually not enviable position to be in. You need to send tickets back saying not finished.

Now, depending on the type of QA, you might need to code a little, be able to read code so you understand what it is doing, not completely understanding it but the basics. You need to use some testing tools, those you need to learn, Selenium is a good one to start with.