Quality Assurance Engineer

QA Engineer to own quality validation across our Portal, Frontend, Analytics, and Grafana-integrated features, and to serve as our primary Incident Coordinator. This is a hands-on, ownership-heavy role: you'll validate merged code before every release, sign off on features before they reach clients, coordinate incident response (including being the first point of contact during off-hours L1/L2 incidents), and help build out our automated regression suite. This role replaces an existing team member and is expected to be fully operational within the first 60–90 days.

QA Sign-Off & Release Validation

• Validate merged code in both test and production environments before and after release, following the Code Review SOP.

• Own post-merge QA validation in the test environment and perform production smoke tests for every release PR.

• Review and write QA test cases for new features (e.g., document management, form/data-entry flows, dashboard integrations) before development is marked Ready for QA.

• Track QA status and sign-off in Jira; ensure no feature ships without a logged QA outcome.

Incident Coordination & On-Call

• Act as the primary Incident Coordinator: monitor the client support channel (email) and internal Slack incident channel, acknowledge incidents, and create Jira tickets with the correct severity (L1/L2/L3), per the Incident Reporting SOP.

• Serve as the Level 1 on-call contact, with a target acknowledgment time of ≤ 1 hour, including best-effort reachability during off-hours (via phone/WhatsApp) for critical (L1) and major (L2) incidents.

• Validate fixes before incident tickets are closed and confirm resolution with the reporting client or team member.

• Escalate to Level 2/3 engineering contacts when incidents aren't acknowledged or resolved within SLA.

Scheduled & Preventive QA Checks

• Perform monthly scheduled manual checks covering reporting accuracy, portal form validation, and data integrity, per the Scheduled Manual Checks SOP.

• Log each check as a Jira task with findings and outcomes, and escalate critical findings through the Incident Reporting process.

• Support quarterly security and process reviews (e.g., flagging QA-relevant findings from dependency/security scans).

Test Automation

• Build and maintain an automated regression suite (QA Automation repo) using Playwright or Selenium for UI/E2E coverage, plus API-level automation, to reduce reliance on manual regression testing over time.

• Maintain and expand regression coverage in line with each release; document coverage changes in release notes.

• Web Portal: Django (backend), React (frontend)

• Data & Dashboards: Grafana, InfluxDB, MQTT-based IoT data pipelines

• Tooling: Jira, GitHub Actions (CI/CD), SonarQube (static analysis), Slack, Playwright/Selenium (test automation)

• Process: Two-week sprints, PR-based code review with a single Tech Lead approver, staged branch promotion (dev/staging → main)

• 2–4 years of hands-on QA/software testing experience, ideally on a web application product (backend + frontend).

• Strong manual testing skills: writing test cases, exploratory testing, regression testing, and production smoke testing.

• Must have hands-on automation testing experience with Playwright or Selenium — able to write and maintain automated test scripts, not just execute manual scripts.

• Working knowledge of API testing (e.g., Postman, or automation frameworks such as pytest/requests) and appetite to build out automated coverage.

• Comfortable reading data and validating dashboards/reports for correctness (experience with Grafana or similar BI/dashboarding tools is a plus).

• Familiarity with Jira-based workflows and bug lifecycle management.

• Clear, calm communicator — this role is client- and team-facing during incidents and requires writing precise bug reports and status updates.

• Willingness to be reachable during off-hours for critical incident response, per the on-call rotation.

• Prior experience in SaaS, IoT, industrial monitoring, or similarly data-heavy domains is a plus but not required.

• Exposure to SQL and basic data validation queries.

• Experience with AWS-hosted applications (EC2, RDS, S3) from a QA/operations perspective.

• Prior experience as an incident coordinator or on-call responder.