There are really no key requirements for you to be hired as QA in any company. At least I’ve never worked as one before but was hired for my history as system administrator and developer.
I have also done some tests in the past that were needed for my work, but have never seen a real test plan and have never written one or followed one. In my past work, everything we write was tested by ourselves. It was not a separate job, but was part of the work process. You write, you test.(If you have not read the previous 3 articles, you may find part 1 describing the basics of the QA workflow, part 2 getting some details on the ways of How to test as QA and part 3 describing few details of the actual methods of testing. In all cases, those methods may vary a bit in the company that will hire you in their ranks.)
The job description and requirements themselves, may surprise you. That’s what was written in the Job Advertisement I saw when applying:
Telco Systems (a subsidiary of BATM Advanced Communications) is a well-known manufacturer of a wide range of switches and routers destined for telecommunications and corporate networks. BATM specializes in the design and implementation of network equipment for IP switching and routing, and provides means for high-speed data transfer over optical and copper media. The company offers products with highest throughput, reliability and quality along with technical support for broadband transmission of video, voice and digital data over IP.
Telco Systems is looking to recruit a QA (Software Quality Assurance Engineer).
As part of an international team of software engineers you will:
- Design, develop and perform testing procedures for verification of state-of-the-art embedded systems software for a range of network applications;
- Maintain detailed testing documentation;
- Be involved in the full implementation cycle of specific modules in Telco’s integrated whole-range-of-platforms networking operating system
- Help Software developer teams in testing of comprehensive functionality
- Help Technical support teams in initial on-site installation of new or enhanced modules
- Maintain sophisticated knowledge in relevant networking standards, be part of the new features design brainstorming sessions
- Willingness to develop testing procedures
- Strong analytical abilities and troubleshooting skills
- Experience in Unix/Linux environment
- CCNA finished course is an advantage
- QA experience is an advantage
- Experience in networking is an advantage
- Experience in script languages is an advantage
- Fluent in English
- A challenging and dynamic area of work involving competition against world’s leaders in networking
- Professional environment, working in a team of qualified engineers;
- Competitive remuneration package;
For most of Its part, this job advertisement, should not scare you. You don’t have to start from zero. In most cases someone has already made templates about everything you need to do and there will be someone to mentor over you and provide help until you are ready to go delve deeper. When I started learning what is required of me, there was already a big data base with test plans and detailed test cases. I only need to build over them. Testing documentation was already above 1700 pages and small work was required to keep it up to date only. The requirements were only guidelines of what a person should know to apply for this job, but were not all “must haves”. If a person is a good in what he/she does. No CCNA and no specific certificates are really needed. Only a desire to work. (one of my female colleagues does not even speak English well, but she is good technician and even English fluency is not 100% required in such cases).
Any experience in the field of the company products or relevant may be more than enough to start working as QA specialist in such company.
The salaries vary per country. The best payment goes in USA, ranging from 5 to 6 digits in year, while in India the salary varies from 100 to 600k rupees (14-to-100k EUR or 20-to-150k USD). It is normal for underdeveloped or developing countries the salary to be low. It is also normal for those countries to have LOTS of outsourced big companies. It is a shame, that in Bulgaria, those digits don’t even go Half-that-good. Our QA engineers are happy if they make 5 digits/year in EUR.
But I got away with this, and forget the important aspects of this work:
- It is interesting!
- It pays in another way – you learn new stuff.
- It makes your mind very able to analyze problems.
- It is not hard to do.
- Takes about 6 months to learn, but is like the bicycle and swimming. You can’t forget It.
- Gives you a firm grasp on some white hat techniques you can’t learn by normal means.
- Helps you learn some script programming in the process.
- Gives inner details of company products you can’t find in the WWW.
- It is actually quite fun to break through someone else’s code and find nasty bugs.
- Allows you to break it again after the developer decides “it’s working”.
- Creates firm connections with 3 categories of IT specialists that can come handy in personal aspect if you want to evolve. Developers, System administrators and Technical writers.
So, IF you think this work is for you, go to your local Job market and apply to the 10 most promising QA entries there. I will try to help you with advices and ready test scripts in my blog.
Keep in touch 😉