Role Overview
Join Efficienza as a QA Engineer focused on delivering reliable, high-quality product experiences. In this role, you will drive manual testing across enterprise web applications, own regression testing cycles, write structured test cases, and validate real-world user workflows and edge cases.
You will work closely with developers, designers, and product teams to identify issues early, improve product quality, and support stable production releases. While manual testing remains the core responsibility, exposure to automation is expected to help improve testing efficiency and coverage over time.
We are looking for someone with strong attention to detail, product thinking, and a proactive approach to quality.
You will excel if you:
- Think from the user’s perspective and approach quality as part of the overall product experience
- Think from the user’s perspective and approach quality as part of the overall product experience
- Treat regression testing as an ongoing quality practice, not just a release activity
- Identify gaps, edge cases, and unclear requirements early in the development cycle
- Use automation thoughtfully to strengthen manual testing efforts and improve coverage
Key Responsibilities
Manual Testing & Test Design
- Write and maintain structured test cases covering functional, edge case, and negative scenarios across assigned product areas
- Perform exploratory testing to surface issues that scripted test cases may miss
- Validate UI behavior against Figma designs, component specs, and acceptance criteria
- Raise well-documented bug reports: clear reproduction steps, expected vs actual, environment, and severity
- Review tickets and requirements in sprint planning — flag ambiguity, missing cases, and untestable criteria before dev starts
- Participate in sprint reviews and demos to validate shipped features against stated goals
Regression Testing
- Own and maintain the regression suite: test cases kept current with every feature change and release
- Execute targeted and full regression cycles before releases, ensuring no silent breakage
- Identify recurring regression patterns: document them, escalate them, and work with developers to address root causes
- Prioritize regression scope by risk: change impact, critical user paths, and high-traffic workflows
- Verify bug fixes without introducing new failures: regression awareness on every re-test
Automation Testing
- Write and maintain automated UI test scripts using Playwright or Cypress for web application flows
- Perform API testing using Postman or similar REST tools: validate contracts, status codes, payloads, and error responses
- Understand and contribute to CI/CD-integrated test runs via GitHub Actions or equivalent: test automation triggered on PRs and releases
- Convert stable, high-priority manual test cases into automated scripts over time
- Use browser DevTools for debugging: network inspection, console errors, element state, and response validation
Backend & API Validation
- Validate API behavior using Postman or similar REST tools across functional and edge-case scenarios
- Verify request payloads, response structures, status codes, authentication flows, and error handling
- Validate frontend-to-backend data consistency across workflows
- Perform basic database or backend validation where required
- Use browser network tools and API logs to investigate integration and workflow issue
Collaboration & Reporting
- Communicate test status, coverage gaps, and release risks clearly in standups and sprint reviews
- Work directly with developers to understand implementation details and test accordingly
- Use JIRA or equivalent to manage bugs, test progress, and sprint-level QA status with structured hygiene
- Contribute to QA documentation: test strategies, edge case libraries, and onboarding guides
Required Technical Knowledge
| Area | Proficiency | Details |
|---|---|---|
| Manual Testing | Core Strength | Test case design, exploratory testing, bug reporting, structured test plans |
| Regression Testing | Core Strength | Full & targeted cycles, suite ownership, risk-based prioritization |
| API Testing | Proficient | Postman, REST validation, status codes, payload & schema correctness |
| Playwright / Cypress | Working Knowledge | UI automation for web flows, selectors, assertions, basic test structure |
| Backend Validation | Working Knowledge | Data consistency checks, API debugging, basic SQL validation |
| JIRA / Test Mgmt. | Proficient | Bug tracking, sprint board hygiene, test case documentation |
| GitHub Actions / CI | Exposure | Understanding pipeline-triggered test runs, PR checks |
| Agile / Scrum | Experienced | Sprint ceremonies, acceptance criteria review, definition of done |
| Browser DevTools | Proficient | Network tab, console, element inspection, response debugging |
| Documentation | Proficient | Test cases, bug write-ups, coverage reports, edge case libraries |
Good to Have
- Cross-browser testing using BrowserStack or LambdaTest
- Basic SQL knowledge for backend data validation alongside frontend testing
- Accessibility testing familiarity — axe DevTools, WCAG 2.1 awareness, screen reader basics
- Visual regression testing exposure — Percy, Chromatic, or similar
- Basic understanding of React component behavior and frontend state to test more intelligently
- Familiarity with test management tools: Zephyr, Xray, or TestRail
- Exposure to performance testing concepts: Lighthouse, basic Web Vitals awareness
Key Deliverables
- Structured, reviewable test case library covering all assigned product areas
- Maintained regression suite with documented coverage scope and known gaps
- Clear, reproducible bug reports that unblock developers without back-and-forth
- Sprint-level test status reports and release readiness sign-off
- Growing automation coverage: stable manual cases converted to scripts over time
What Success Looks Like
- Bugs are identified during QA instead of production, and recurring issues result in stronger future coverage
- Regression cycles remain stable and predictable without last-minute QA bottlenecks
- Developers trust your signoffs because your testing is thorough and reliable
- You identify critical gaps and edge cases before they become production issues
- Product quality improves consistently across releases through stronger testing discipline and better QA processes