Is Software Testing a good career choice for a Fresher? Many Freshers opt for Testing because it seems to be a non-programming career. We have become engineers but still don’t want to learn programming. Testing seems to be an obvious choice.
Some organizations recruit for Automation and then assign manual functional tests. Some candidates fake Automation to clear the interview, and then learn. What matters is – ‘getting things done’.
What is the ideal time for your first Job switch? Some say 2 Years, others say 3 Years. Is there really an ‘Ideal Time’? First 2-3 years are the most important years from ‘learning’ perspective. That’s when we become ‘Professional’ from a ‘Student’. The comparison is inevitable once you touch 5+ years in your first organization and someone who change at 3 years.
Automation is everywhere. Automation experts are in high demand. Nah! Not in high demand, ONLY Automation Engineers are in demand. All job descriptions mention a set of automation tools and frameworks. Interviews revolve around Java, Python, C#, Selenium, UFT, Appium, Frameworks, Algorithms, and what not. Literally ‘Everybody’ is looking for an Automation engineer.
I assume ‘every’ fellow Tester in my network have experienced this situation at least once in his/her career. One of the most common Testing situation – How do you handle timeline crunch? Since Testing is the last step before client demo, the Test team has to make-up for the delays encountered till the build is deployed in Test environment. Now how do you handle crunch timelines without impacting the quality?
Some say serving notice is just like your ‘honeymoon period’. Is it because you are leaving the firm and no more accountable? Or why put efforts for something you know is soon going to end? Coming late – Going early becomes normal? Why?
Many a times we face these kind of one-off bugs 🙁 which peep-out and then hide somewhere. “It was a one-off bug and now not reproducible – so what can I do?” Wrong! Though one-off but still it is present somewhere in the software and as a Tester it is our responsibility to investigate it. How?
Start-ups give you an opportunity to learn a lot. You need to wear multiple hats. Work in & out. But it pays in the long run. Established MNCs give you a stable job with matured policies. Which one do you prefer if given a chance?
Recently I saw a Job description with title ‘Lead QA Developer’. In my view this is the perfect depiction of today’s changing QA landscape where a Tester is expected to – Lead, i.e. planning, strategy, team management and reporting – Quality Assurance, i.e. Test methodology, process, defects management, agile, requirements analysis, test techniques, etc. and – Developer, i.e. hands-on knowledge of programming languages like Java, Python, C#, etc. to build automation frameworks and tools for validation.
I agree situational interviews are the way-to-go, but some theoretical clarifications won’t do any harm. Every tester needs to know the basics at least. It’s essential to be prepared for a time-boxed interview. Get some basic facts clear before facing the next interview, to avoid embarrassment.
Programming is integral to IT, and automation is no different. What interviewers are looking for is if you can think of the correct logic or algorithm. It gives them an idea about your logical thinking prowess.
Most of the times people are not afraid of too much work or learning something new or stretched working hours. What’s frustrating is the messed up work, not too-much work.
Interview is the most important part of the employment process. It can make or break an opportunity. When it comes to Software Testing, almost all organizations are now looking for Automation engineers, SDETs, Selenium experts, Automation architects and what not. Since Manual testers are finding it tough to land a high-paying job switch, many have started learning the basics of Selenium automation (Yeah! Selenium is one of the most popular automation tool now-a-days). But interviewers demand practical experience. And interview questions reflect that view – starting from basic theoretical knowledge, slowly the interview will move towards – Explain Test Automation framework for your current project.
There are lot of people who have Manual testing experience. When there is a walk-in interview you could see thousands of people with more experience than you have. So you have to differentiate yourself from others by adding extra skills to your resume. In a world where the consumer expects fast-paced delivery, and solutions must support a myriad of devices and platforms, manual testing simply doesn’t enable the delivery pace that the market expects. The rise of automated testing in response to this has been rapid. Are you attempting a switch from Manual Testing to Test Automation? This transition won’t come overnight. It takes months/years to lay the groundwork.