End-to-End QA, QC, Manual Testing, Security Review & Issue Resolution for NAMA Travel SaaS Platform

We are looking for a highly experienced QA/QC specialist or small testing team to conduct a complete end-to-end quality audit of NAMA, a travel SaaS platform for travel agencies, DMCs, tour operators, and white-label partners. This is not basic testing. We need someone who can deeply understand the product, test every workflow like a real user, identify issues, document them clearly, and also help resolve or coordinate fixes where possible. The platform is already live/in production and is preparing for a wider launch. The goal is to make sure the application is stable, secure, responsive, functional, and ready for real users. Website/Application: NAMA: getnama.app Scope of Work: You will be expected to perform a complete deep-dive QA/QC review covering the full application, including but not limited to: End-to-End Manual Testing Landing page Registration flow Login/logout Trial activation Free and paid plan flows User onboarding Dashboard Navigation Role-based access DMC workflows Travel agency workflows White-label workflows Admin workflows Staff workflows Lead management Itinerary/workflow modules AI-assisted features Sales and command-center modules Calendar/demo booking modules Notifications, emails, forms, buttons, links, CTAs Error handling and edge cases Workflow Testing Please test every workflow from start to finish as a real user would. Examples: A new travel agency registers and starts using the platform A DMC registers and manages its profile/services A user tries different subscription/trial scenarios A staff/admin user manages platform activity A white-label partner flow is tested A user enters wrong data, incomplete data, duplicate data, or invalid data A user moves across desktop and mobile devices A user gets stuck, confused, or encounters broken flows Security Review We need a practical security review covering: Authentication and session handling Role-based access control Unauthorized page access Data exposure between users, agencies, DMCs, admins, and partners API exposure or weak endpoints Form validation File upload risks, if applicable Sensitive data handling Public/private route checks Basic OWASP-style checks Broken access control Input validation Rate limiting issues, if visible Error messages exposing technical details This is not expected to be a full enterprise penetration test, but we do expect strong security awareness and practical testing. Mobile Responsiveness & Cross-Browser Testing Test across: Chrome Safari Edge Firefox, if possible Desktop Tablet Mobile Android and iPhone viewports Please check: Layout issues Broken buttons Overflowing content Alignment issues Mobile menu Forms on mobile Dashboard usability on mobile Touch usability Font sizes and readability UI/UX Review We need observations on: Confusing flows Missing instructions Poor wording Broken or unclear CTAs Screens where users may drop off Forms that are too long or unclear Unclear pricing or subscription messaging Missing success/error messages Poor empty states Poor loading states Inconsistent design Any area that does not look launch-ready Bug Reporting Each issue must be documented clearly with: Module/page name User role tested Device/browser used Steps to reproduce Expected result Actual result Screenshot or screen recording Severity: Critical, High, Medium, Low Suggested fix, where possible Whether the issue blocks launch or not Issue Resolution / Coordination We prefer someone who can not only identify issues but also help resolve them or coordinate with our developer. Please mention clearly whether you can: Fix frontend bugs Fix backend/API issues Fix responsive design issues Fix workflow bugs Fix security issues Work with an existing developer Re-test after fixes Maintain a bug tracker Final Deliverables We expect: A detailed QA/QC report A module-wise issue list Screenshots and/or screen recordings Security observations Mobile responsiveness report Browser compatibility report Workflow-wise testing status Launch blocker list Suggested improvements Retesting report after fixes Final launch-readiness status Important Modules to Give Extra Attention To The following modules are especially important and should be tested in depth: Travel Trade Intelligence Layer NAMA Sales Command Center NAMA autonomous QA/security platform Calendar/demo booking flow DMC workflows Travel agency workflows White-label/B2B2C workflows Admin and role-based workflows Landing page and registration flow Subscription/trial/payment-related flows, wherever applicable Ideal Candidate You should have: Strong experience in SaaS QA/QC Strong manual testing experience Good understanding of web applications Good eye for UI/UX issues Security testing awareness Experience with role-based applications Experience testing CRM, travel, booking, marketplace, or B2B SaaS platforms is a plus Ability to write clear reports Ability to communicate with developers Ability to re-test fixes Ability to work independently without needing too much hand-holding Please Include in Your Proposal Please answer these questions when applying: Have you done end-to-end QA for a SaaS or marketplace platform before? Please share examples. Can you test workflows manually from a real-user perspective? Can you identify security and role-access issues? Can you test both desktop and mobile responsiveness? Can you provide screenshots and screen recordings? Can you also help resolve issues, or only report them? What tools do you use for QA, bug tracking, screen recording, and security checks? How will you structure the QA report? How quickly can you start? Are you comfortable testing a live production application carefully without disturbing real users? Expected Working Style We want someone detail-oriented, practical, and thorough. Please do not apply if you only do surface-level testing. We are looking for someone who will test the platform as if they are responsible for making sure it is ready for launch. The final goal is simple: NAMA should be stable, secure, responsive, user-friendly, and ready for real users without major launch blockers. To confirm that you have read this properly, start your proposal with: “I will test NAMA end-to-end, not just click around