WeQA Software’s Post

Hidden bugs can surprise users. Surprised users can get annoyed. Annoyed users can give bad reviews. Bad reviews can prevent onboarding new users. Fewer users being onboarded means decreased MRR. --- Avoid all of these by hiring a QA engineer at https://lnkd.in/dj9q-9M5

🗣️: Why Tech Founders Should Hire a QA Engineer? Answer: - Ensure product reliability - Enhance user satisfaction - Save time and resources - Improve brand reputation Hiring a talented QA engineer is essential for tech founders aiming to build user-centric products with long-term success.

Software developers often say they hate hiring QA. The reasons are common, but the issues are fixable. Here are a few reasons why and potential solutions…. Reason: “They didn’t provide enough documentation to reproduce the bug easily” Solution: HOT TAKE - testers should ALWAYS provide screenshots of the bug and the steps leading up to how they produced it. There needs to be more than just a summary title of the bug. There should also be good detailed logging infrastructure the devs provide to make it easier to debug. Reason:“Testers do the bare minimum and only test exactly what you ask.” Solution: “Involve the tester with your product development and explain how the product should work. AND pay them well. Reason: “Testers file bugs that aren’t really bugs. They’re often false positives.” Solution: Usually this comes down to a lack in communication about how the product should work. Sometimes, a product update has occurred, and the dev team didn’t inform QA that the behavior has changed. Engineers should proactively let the testers know the product behavior has changed to avoid this. #softwaretesting #softwareengineering #milestones

Hidden bugs can surprise users. Surprised users can get annoyed. Annoyed users can give bad reviews. Bad reviews can prevent onboarding new users. Fewer users being onboarded means decreased MRR. Avoid all of these by hiring a Software QA expert!

🚧 We should stop hiring for frameworks and languages. 🚧 The three best frontend engineers I hired had zero past experience with the frontend frameworks we used. The team that helped quickly and safely move the most critical and complicated part of our product to Go-based microservices had no previous experience with Go. We built a few native mobile apps with engineers who didn't have previous experience building mobile apps. We perfectly maintained the GCP-based product with the help of engineers who only had AWS experience in the past. It takes days or weeks for a great engineer to start delivering great results with the tools they have zero experience with. It takes years, if at all possible, for a mediocre engineer to start providing great results, no matter how much experience they have with the tools. Learning tools is easy. Learning engineering is hard.

What Stan Ivanov 🇺🇦 has put in words develop your organisation around sound engineering conceptß getting the basics right. Tools and Frameworks are only a means and mutable. Proper approach and thinking have a better rate of success than anything else.

When you have an understanding of the fundamentals, the ability to ask the right questions, and a desire for continuous learning, you can learn any tool quickly and provide value to any team.

Attention Hiring Gurus: While mastering System Design and acing LeetCode are crucial, don't forget—communication skills are the true MVPs. After all, the best code is the one you can explain! In the software industry, the art of making complex info clear and enjoyable is a rare gem. Some folks can deliver a message so succinctly and powerfully it lands with impact, while others add a witty touch that brings a smile. Hiring for senior tech roles? Remember, mastering System Design and LeetCode is great, but the ability to communicate effectively is the real game-changer.

📢 🎉 I'm Hiring! 🎉 📢 We've got several fantastic new positions on the Product and Engineering teams here at Stack Overflow , so here's a quick overview of each one and what we're looking for! **Deep Breath** 🔍 Senior Product Researcher - https://lnkd.in/eg-YqbDU You’d be great for this if: You’re an experienced UX researcher, with a breadth of experience across different products, who wants to apply both qualitative and quantitative research skills to our various products, and help us define what research is at Stack Overflow. 🐈 Technical Product Manager - https://lnkd.in/evWqmJer: You'd be great for this if: You're a product manager that loves partnering with Data Engineers/ML Engineers/Software Engineers, and wants to help us change the way our organization works with our unique, huge set of data. 🤖 Site Reliability Engineer - https://lnkd.in/e-NW5ctF You'd be great for this if: You're an experienced SRE who has worked extensively within an Anti Abuse team, working on stopping malicious activity. 🐈 Senior Product Manager - Product Strategy - https://lnkd.in/eg-YqbDU You'd be great for this if: You're experienced in MVP development, and want to help us build the roadmap for our new Overflow API product. 🔐 Director of Information Security - https://lnkd.in/euY6aAbt You'd be great for this if: You're a Director level InfoSec professional, with a deep understanding of the industry's landscape, and can help us evolve our strategy and compliance procedures over the next several years, as well as manage our existing (and fantastic) team. If you, or someone you know, looks like a good fit for any of these roles, then send an application over and we'll take a look. (If you've already reached out about one of them, thank you and sorry if you’ve not heard back yet. I'm working through my inbox and will be in touch if we think there's a fit!) I'm, of course, very biased, but I think what we're doing here at Stack, both on the product and community side, has a huge impact on the lives and careers of developers and technologists globally. It's a unique challenge, but one that has brought a lot of meaning to my own career, so if you're interested in seeing how your experience could help us as we grow please get in touch!