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?
A strong manager backing the team is the foundation to a successful team. A team succeeds when you entrust them to deliver & have full confidence in their caliber. It’s like a family, no one should point at your team for weakness 😉 at the same time internally you might need to introspect & keep improving. What say?
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?
For some projects we should rename the ‘Onshore-Offshore’ model to ‘Manager-Worker’ model 😛 Where Offshore team is taken for granted. Additionally Offshore team is at the back-foot by default. But why? We should learn to ‘prioritize’ the work items and respect each other’s personal time. Learning to say ‘No’ in a constructive way is an art you learn via experience.
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?
Adopting technology is important, but blind adoption is different than logical application of Technology. When I see it – looks like everyone wants to fit the tech-term anywhere in the test process and call it tech-driven QA. But how do you measure the ROI from client perspective? Do you compare Super-Tech.QA vs. Functional QA? Or Super-tech-tools are cheaper than the required man power? Nah! Everyone says “All these are long-term benefits, no short-term advantage”, but then eventually forget to measure the ROI in the long run as well 😛 On the other hand, due to all this fuss we have somewhere neglected the original Tester.
Why are some developers not aware of the functional flows? It’s like I am coding this module, why should I know the complete flow. My module is working fine. But you have to have a complete understanding of the system. Isn’t it? It works like that in every sphere – look at the bigger picture. Where do you fit, or where does your code/module fit in the overall flow. System architecture and System’s User perspective go hand-in-hand. Everyone in a project should have a clear understanding of these two aspects.
Cut the crap! Whatever be the debate but still Manual testers are finding it hard to stay relevant in today’s job market. Why? A simple argument – ‘Manual Testing’ & ‘Manual Testers’ are two separate entities. Agree that ‘Manual Testing is NOT dead’, and it never will. But what about Manual Testers?
Recently in an interview I was asked ‘Why do you love Testing?’ This got me thinking…How will you feel if you bought a new smartphone at a high price only to find a fault when used? Frustrated. Disappointed. Cheated. Angry. Sad? Yeah! A tester’s job is to prevent you feeling all those negative aura 🙂 What is your reason to pursue Testing as a career?
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,
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.
Current competencies are important, but we need to have a long-term vision. It’s important to be aware of the IT industry trends. The industry will change. Choice is yours – up-skill now (relatively easy) OR up-skill when you get stuck (it’s hard, believe me).