Senior QA Engineer
Play a critical role in shaping our quality strategy and building test automation frameworks You’ll partner with developers, product managers, and DevOps to ensure the delivery of high-quality, scalable, and performant software.
- Design, develop, and maintain automated test frameworks for UI, API, and backend systems using Playwright (Node.js).
- Champion the use of tools such as BrowserStack, Applitools, Testim, and other modern QA platforms to improve test coverage and visibility.
- Collaborate with cross-functional teams to define acceptance criteria, test plans, and test cases.
- Own and lead end-to-end testing for major product releases — from planning to production.
- Conduct root cause analysis for critical issues and work across teams to implement long-term fixes.
- Optimize and maintain CI/CD pipelines (e.g., Jenkins, GitHub Actions) for fast, reliable feedback cycles.
- Promote and participate in test management processes, using tools like TestRail, Zephyr, or Xray to track quality metrics, ensure traceability, and drive testing efficiency.
- Advocate for quality in all aspects of the SDLC — including code reviews, architecture discussions, and sprint planning.
- Identify and fill gaps in test coverage across functional, regression, performance, accessibility, and security testing.
Requirements
Key Responsibilities:
- Bachelor’s degree in Computer Science, Engineering, or equivalent.
- >5 years in Software QA.
- Proven expertise with Playwright (Node.js) — must-have.
- Strong understanding of JavaScript/TypeScript or Java .
- Experience testing modern web applications, REST/GraphQL APIs, and backend services.
- Hands-on with CI/CD tools (e.g., Jenkins, GitHub Actions, CircleCI).
- Familiar with tools such as BrowserStack, Applitools, Testim — for cross-browser, visual, and intelligent testing.
- Strong grasp of test management tools (TestRail, Zephyr, Xray, or similar) and test case lifecycle.
- Exposure to performance, accessibility, and security testing practices.
Technical Competencies/Skills:
- Software Development/Testing Lifecycles
- Software Testing Concepts/Techniques
- Mobile Testing Concepts
- API Testing
- Automation Testing
- DB Testing
- Manual Testing:
- Performance Testing
- Sharp Eye for Details
- Agile Methodologies (Scrum)
- Agile Principles
- Productivity
- Troubleshooting
AI Competencies
- Leverage AI-powered tools and agents to improve software testing efficiency, automation, and overall engineering productivity.
- Utilize AI to generate and optimize test cases, automation scripts, test data, and documentation, while validating all AI-generated outputs.
- Apply AI to analyze defects, identify test coverage gaps, and support root cause analysis.
- Explore and adopt emerging AI-driven testing technologies and best practices to continuously improve quality engineering processes.
- Knowledge of (RAG), (MCP), or similar AI integration concepts .
Benefits
- Opportunity to work for a dynamic international company with a flat hierarchical structure, where your voice matters and your impact is seen.
- The company will contribute up to EUR 25 per month towards staff perks
- A company bonus scheme applicable as per bonus scheme rules
- EUR equivalent salaries paid in EGP
Skills
As published by workable · 6 questions · 1 written answer
Basics
First name, Last name, Email, Headline, Phone, Address, Education, Experience, Summary, Resume, Cover letter
Short answers (4)
- What is your expected salary per month (EGP/NET)?
- What is your notice period?
- Walk me through a test automation framework you built or significantly redesigned using Playwright. What design decisions did you make around structure, reusability, and reporting, and what would you do differently if you started it again today?
- Which area in Egypt do you live in?
Pick from a list (1)
- Are you comfortable working onsite 4 days a week, and 1 day from home?
Written answers (1)
- Tell me about a time a critical bug slipped through to production despite your test coverage. How did you approach the root cause analysis, and what did you change afterward — in the tests, the process, or both — to stop it happening again?