Ilyas A.

Manual + Automation Testing | Project Manager | Agile Delivery

Your QA is only as good as your release process. I run both. I'm a QA Engineer and Project Manager with 5+ years shipping software, web, and app releases for US-based teams. Instead of hiring a tester and a PM who hand work back and forth, you get one person who catches the bugs AND owns the timeline — so nothing slips through the crack between "tested" and "delivered." HOW I WORK Testing - Manual + automated testing (Selenium, Cypress, Playwright) - API testing (Postman, Swagger) - Performance testing (JMeter) - Regression, functional/non-functional, UAT, smoke/sanity, cross-browser, cross-device, end-to-end Delivery - Agile/Scrum: sprint planning, backlog grooming, retrospectives - Jira, Azure DevOps, Asana, ClickUp, Wrike, Swit - Stakeholder communication, risk management, cross-functional coordination TRACK RECORD I've led QA and delivery for teams at Work Sphere, Payfusion, and Ashtra — owning both the test process and the release calendar, so builds went out clean and on schedule, not "clean OR on schedule." WHY THIS COMBO MATTERS A QA engineer without PM context tests in a vacuum. A PM without QA depth can't tell if "done" actually means done. I sit in both seats, so bugs get caught earlier, standups don't need a translator between test and delivery, and you get one point of accountability instead of two. Send me your current testing/PM setup and I'll tell you — honestly — where the gaps are before we even start.