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.
The QA team starts testing a software/product and there are “way too many” defects. Every other scenario is failing, new flows are explored & clarifications sought. What would be the strategy now?
Ideally every team should maintain a bell curve. That being said, this was a recent discussion I had with one of the seniors. ‘Freshers are lenient, reckless & lack professionalism/experience’ he said. But that is the whole point. Everyone was a fresher once. Freshers are enthusiastic to embark on their professional journey, are not bounded by professional processes, can think out-of-the-box. Just that they need proper guidance, relevant training & due diligence.
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.
Micro Management kills the trust. Or it proves that there is no trust at the first place. And Freedom breeds innovation. It is when you give people the power & the freedom that ideas originate. And one out of five/ten ideas works out to be superb. It is when you trust in your team that they perform. When they know you are backing them. You believe in them & in their work. In their potential. A strong manager have full trust is his/her team – it is about the tasks, work and the value-adds, innovation. It is not about ‘controlling’, it’s about ‘managing’. Ever had a micro-management incident in your team? How did it impact the team morale? Or how a strong manager built the trust & team pulse?
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?
Communication is important. “Excellent Communication Skills – a must” is always one of the Job descriptions. If not explicitly written, it is implicitly understood. One of the most important qualities recruiters look for in candidates is their ability to communicate clearly. You might be technically good, but you don’t work in silos. People work & achieve as a team. Communication is not just about the language but putting across your ideas in a simple manner, clear in understanding.
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?
Yeah! Today I am resigning from my current organization. Often asked about ‘Why are you leaving your current Organization?’ – I feel there is no single reason. Leaving a company which has been your half-home for years is a professional as well as emotional decision. It’s an important decision which can be (& mostly is) a result of multiple factors,
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.
Yeah! A thought that crosses every tester’s mind who is searching for a better QA opportunity. Why am I not getting selected? Simple! Because you were not the best fit. Best fit in terms of technology, experience, salary, attitude, skills, behavior, etc. Only QA knowledge is not enough to land you a job. Yes, companies look for the ‘Best Fit’ among the available candidates. Some look for tech-savvy candidates, other focus more on the learning attitude. Every company has its own set of guidelines – what we call as company culture. With this article, I try to elaborate on some of the perspectives around Software Testing interview. It has helped me, and I hope this helps fellow testers as well in their quest for the next dream job.
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.