CSHQA’s Post

Something other than work. Thur 4th April 2024 21:56. Suppose you think out of the box 80% of the time. Observe all corners, top, sides and bottom. measure and understand pressure, volume, contents. would you. A open. B not open. C ask if there is another question. or answer. All are incorrect. If you think like a box but observe a different shape, excess or other defect unknown. What to do next. Understand. How. Why. What. To do next. Then act. What do you do then. Are you sure? Consider. Carefully. I do. Always. I AM A QAS. Engineer. It is my job. I Act. I observe. I understand. It's what I do. The Job. Required. Thank you. Post. Terry. TPQAOK. waveyline.

Guys, let’s do not be confused about these roles🫡 QA (Quality Assurance): They're like the detectives making sure everything works as it should. They sniff out any problems before they become big headaches. QC (Quality Control): Think of them as the safety inspectors. They double-check everything to make sure it's safe and up to scratch. Testing: These are the brave souls who volunteer to poke and prod your creation, just to make sure it won't fall apart when it matters most. They're like the crash test dummies for your project. So, in short: QA checks for problems, QC makes sure everything's safe, and testing ensures it won't blow up in our faces. It's like a superhero team, but with spreadsheets instead of capes. We shouldn’t require one aspects from another, take care🤙🏻

When does a software Professional gets a kick!?? That one sip and we say, waw, it gives the best kick...let's see when different role in an IT profession should get a kick... 1. Product Owner: when you see the product which you brought to market is being used by some unknown person and he just says - waw! 2. Product Manager: when the product specification gets used without any single question asked (till acceptance of the product), so clear, you made it! 3. Project Manager: we will make him wait till end :) 4. Legal advisor (contract doc reviewer): When all his red lines are accepted without any to n fro :) 5. Hiring manager: Multiple! When there is no renege! when someone is ready to join even before offer is ready! when everything goes well and background verification shows red! when on day 1, candidate calls you at 8 am asks 'where are you, I am in office!' 6. Developer: when max time taken to write a program is = your typing speed! when you finish code before your estimate! when you deliver code without any bug! when your reviewer doesn't find any code review comments! when we see final appraisal remark as 'good job done' and then good word becomes bad for us :) 7. Tester: when in first 30 mins after Dev sign off you find a blocker bug! Or you start the day and you find best blocker bug in first 30 mins! 8. Manager: when all of above team members of yours gets the kick and get it at right time :) Do you want to add when you get that kick!? #ITdevelopment #softwareengineering #officehumor #purposedrivenlife

When I speak with my candidates, we also speak about their values and what is important to them 😎 Do you know what is at the bottom of the list more than 95% of the time? Their "Job Title" 🧐 Of course, your job title CAN tell a future employer about the skills you've most likely acquired, the years of experience under your belt, and the responsibilities you may have 💪 But just like a Senior Developer, QA Manager, or Solution Architect - they can have different responsibilities under each of them depending on the company you're working in 🤓 Most of the candidates I have spoken with don't care about job titles as much, as long as they are happy with the tasks they do and the salary for those tasks they receive. How important are job titles to you? Maija from Smartist.One UG #jobtitle #responsibilities #values #priority #smartistone

I've been reviewing a lot of resumes recently and it's obvious not a lot of people know how to make themselves stand out or even represent anything more than what the responsibilities were for their previous jobs (pretty sure that's not unique to QA roles). Repeated lists of job responsibilities that don't tell me anything about yourself, your actual skills, your results, your impacts, or why I should hire you over the other 100+ applications that all look exactly like yours. Don't tell me what your job responsibilities were, I'm very familiar with those after 20+ years in QA. Tell me about what the results were from what you actually did. Tell me how you made your developers, co-workers, and customers lives better. Tell me how you transformed a process, dealt with a difficult problem, created something innovative, etc.. It's sad just how rare it is to actually see a metric in a QA resume. A great question Phil asks: How can we gauge a potential employee if their chief skill is to make sure nothing happens? Tell me what you actually did to make sure nothing happened or how you stopped the bad thing that was happening. With his great example of the castle (even better with the Monty Python reference): Tell me what you did to ensure the castle didn't sink in the 1st place? What did you change to make sure the next one didn't? How did you make sure other teams in your org learned those same lessons without having to sink castles on their own? The most impressive QA resumes I've seen show me that you can actually Assure and Scale Quality, not just perform testing. They tell me how you built quality into production and development processes, found the bugs earlier and faster in those processes, empowered faster and cleaner development, etc. Personal example from my resume: • Scaled Prime Gaming test and launch capabilities and shifted quality left • Increased the number of content launches tested and released each month by 5X (from 15 to 80+) and decreased the percentage of launches with blocking bugs found during testing each month by 75% The job responsibility was "Managed the QA team for Prime Gaming". And with just that people would know I likely did that base responsibility well enough to not be fired. The truth was driving cross team collaboration over years to root cause the issues AND the production and development processes that were leading to these issues being introduced in the 1st place, working with those teams to improve processes, add better upstream data checking and automation to catch them earlier when they did happen, etc. All the while quickly hiring and growing a new QA team and instilling in each of them that same drive to work with every team they interacted with (both internal and external developers) to improve these processes upstream. Defining metrics for and tracking, reporting on it regularly etc. Convince me that if I hire you I'm going to get the strongest castle in all of England.

Exactly my thoughts on CV writing, if you're looking to improve your applications I recommend reading this post. For me its always Cover letter to get to know you > CV to get to know your professional experiences > Interview to follow up on those two things.

Hello #Benchsalerecruiters I hope you are all doing great! kindly share your profile by email- Nishant@sourceinfotechs.com Role-SAPProject manager Location -Mini polish MN Onsite F2F interview QA PM with Budget exp Qualifications: 6+ years’ experience required. Responsibilities: Responsibilities: Plan and implement projects. Help define project scope, goals , and deliverables. Define tasks and required resources. Manage the project budget and risk. Allocate project resources. Create a project schedule and timeline. Support and direct team. Lead quality assurance. Report on the project status. Present to stakeholders reports on progress as well as problems and solutions. Implement and manage changes when necessary to meet project deliverables. Facilitates the creation of communication plans, ensuring that appropriate information is exchanged among key stakeholders. Determines client requirements and translates requirements into operational plans. Identifies and assembles the appropriate blend of resources to meet project needs and requirements; manages sub-contractors. Determines client requirements and translates requirements into operational plans. Identifies and assembles the appropriate blend of resources to meet project needs and requirements; manages sub-contractors. Establishes appropriate metrics for measuring key project criteria. The projects in scope for ‘application’ role family are any development, support, and maintenance of existing applications or new development work. The projects in scope for the ‘infrastructure’ role family are ongoing maintenance and upgrade/migration of infrastructure assets. '-Leads project planning, scheduling, monitoring, and reporting activities for small to medium projects. #SAPPM #SAPProjectManager #ProjectManagement #BudgetManagement #QualityAssurance #TeamLeadership #StakeholderManagement #RiskManagement #ProjectPlanning #ResourceAllocation #ProjectScheduling #InfrastructureProjects #ApplicationDevelopment #OperationalPlanning #ProjectReporting #ProjectExecution #CommunicationPlan #SubContractorManagement #ProjectMetrics

𝐅𝐫𝐨𝐦 𝐀𝐫𝐦𝐞𝐧𝐢𝐚 𝐭𝐨 𝐭𝐡𝐞 𝐔𝐒𝐀: 𝐖𝐢𝐭𝐧𝐞𝐬𝐬𝐢𝐧𝐠 𝐭𝐡𝐞 𝐈𝐦𝐩𝐚𝐜𝐭 𝐨𝐟 𝐎𝐮𝐫 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞! Ever wonder how your work makes a real difference? Our QA Lead and Project Manager just got back from an incredible trip to the USA! ️ In this quick video, they share a glimpse of their adventure: ⚫Seeing our software in action on construction sites firsthand! ⚫Talking directly to the people who use it every day! ⚫Collaborating with colleagues from the U.S. head office and soaking up the amazing team vibe! It was an inspiring experience that reminded us why we love what we do.💚 Seeing the positive impact our software has on thousands of people is incredibly rewarding. 👷 But the best part? Strengthening our human connections across our borders! This trip is just the beginning, and we can't wait to share more exciting developments in the future. 🌎 𝐖𝐚𝐭𝐜𝐡 𝐭𝐡𝐞 𝐯𝐢𝐝𝐞𝐨 𝐧𝐨𝐰 𝐚𝐧𝐝 𝐬𝐞𝐞 𝐭𝐡𝐞 𝐦𝐚𝐠𝐢𝐜 𝐡𝐚𝐩𝐩𝐞𝐧! #SoftwareImpact #TeamCollaboration #CrossBorderConnections #InspiringWork #ConstructionTechnology #PositiveImpact #GlobalCollaboration #FutureDevelopments

I've been thinking about easy to understand ways to stand out in the QA profession, and I'm coming up a bit short. Other project contributors can share concrete concepts like code or art or music. But what results are tangible from QA? Is it the number of bugs? No, that number can be easily inflated. Is it a clean product release? Maybe, but QA is generally there to inform progress, not dictate it. Is it a series of reports or test plans? No, because those are internal and again serve to inform production, not to drive a product. QA is the quintessential support class if you'll excuse the gaming parlance. It's not often that the cleric or the paladin is given credit for winning an encounter, even if their role is crucial. It's difficult to exemplify one's impact in preventing a castle from burning down, falling over, and then sinking into the swamp, because hopefully the castle is still sitting there quite happily, not doing any of those things. So I ask you, recruiters, producers, hiring managers; what is the best way to gauge a potential employee if their chief skill is trying to make sure nothing happens? And QA professionals, what say you? What is your weapon of choice when it comes to getting hired?

When I speak with my candidates, we also speak about their values and what is important to them 😎 Do you know what is at the bottom of the list more than 95% of the time? Their "Job Title" 🧐 Of course, your job title CAN tell a future employer about the skills you've most likely acquired, the years of experience under your belt, and the responsibilities you may have 💪 But just like a Senior Developer, QA Manager, or Solution Architect - they can have different responsibilities under each of them depending on the company you're working in 🤓 Most of the candidates I have spoken with don't care about job titles as much, as long as they are happy with the tasks they do and the salary for those tasks they receive. How important are job titles to you? Maija from Smartist.One UG #jobtitle #responsibilities #values #priority #smartistone