Software Quality Assurance Expert Onsite

Role Overview

We are currently looking for a Software Quality Assurance Expert who will be the independent quality authority for this engagement, the gatekeeper who decides whether a release wave goes to production or is held back. This person owns the QA Master Plan and executes testing across all functional, regression, performance, and security dimensions for every release across both systems. The role requires genuine independence: the Quality Expert must be willing and empowered to block a release that fails quality gates, regardless of schedule pressure.

• Own the QA Master Plan and define the testing framework, test types, entry and exit criteria for all releases
• Execute functional, regression, performance, and security testing on every development wave before production deployment
• Act as the Go/No-Go gatekeeper for all production releases, signing off or blocking based on objective test evidence; document the decision formally
• Validate SLA compliance through load and performance testing to confirm the system can meet Critical (15min/2hr), High (30min/4hr), Medium (1hr/8hr), and Low (2hr/24hr) SLA tiers under realistic user loads
• Lead UAT coordination with client end users: write UAT test scenarios in Arabic, facilitate UAT sessions, and document acceptance decisions
• Configure and maintain quality gates within the Dev Ops pipeline; automated tests must pass before any code proceeds to UAT
• Track all defects from discovery to verified closure using the agreed defect tracking tool
• Produce formal QA reports and test evidence documents in Arabic for every release

• Fluent Arabic speaker
• Bachelor's degree in Computer Science, Software Engineering, or equivalent
• 7+ years of professional QA and software testing experience
• Experience across functional, performance, and security testing, not just one type
• Experience working in Agile/Dev Ops environments with CI/CD quality gates
• Experience coordinating UAT with non-technical business users; government sector preferred

• Functional test design: equivalence partitioning, boundary value analysis, decision table testing, exploratory testing
• Performance and load testing with JMeter, Gatling, or equivalent; design realistic load scenarios for web applications and interpret results
• Security testing: OWASP Top 10 validation methodology; DAST tools (OWASP ZAP, Burp Suite) at functional level; SAST tool output interpretation; NCA cybersecurity baseline control validation
• API testing:
  Postman or SoapUI; REST API functional and regression testing
• Regression testing: design and maintenance of regression suites for .NET web applications across multiple release cycles
• Defect tracking:
  Azure Dev Ops Boards, Jira, or equivalent; defect lifecycle management, severity/priority classification, metrics reporting
• Dev Ops pipeline quality gates: configuring automated test steps that block the pipeline on failures (Azure Dev Ops or equivalent)
• SLA and performance benchmarking: defining non-functional requirements as measurable test criteria; validating response and resolution time targets
• Test automation:
  Selenium, Playwright, or Cypress for Angular-based front-end regression (strongly beneficial; not mandatory at hire)
• Mobile app testing: functional and compatibility testing on Android and iOS (beneficial – for correspondence system mobile app)
• Arabic document production: test plans, test cases, defect reports, UAT scripts, and QA release reports, all in formal Arabic

• Independent and assertive; must be willing to block a release against delivery pressure with clear documented evidence
• Meticulous documentation: test cases, execution results, defect histories, and acceptance decisions must be fully auditable for client review
• Proactive risk communication: flag quality risks and test debt to the Technical Lead before they become release-day problems
• Strong collaboration with developers during defect resolution: constructive, evidence-based, not adversarial
• User empathy: UAT design test scenarios must reflect how real correspondence and archiving users actually work, not just technical test cases