Role Overview
The QA Engineer is responsible for ensuring Inventeer ships reliable, predictable software by designing and executing quality processes that scale with the team.
This role is delivery-focused: success is measured by fewer escaped defects, faster feedback cycles, clear release confidence, and repeatable test coverage—not by being the last person to “check” features. QA works as an enablement function: improving engineering quality through test strategy, automation, and tight collaboration with Product Engineers.
Key Responsibilities
Test Strategy & Quality System
- Define and evolve test strategy across products: what we test, how we test, and where automation pays off.
- Establish quality gates aligned with Inventeer’s Definition of Done (risk-based, pragmatic, enforceable).
- Maintain testing standards, templates, and repeatable practices to reduce ambiguity and rework.
Manual QA & Exploratory Testing
- Perform exploratory testing to uncover edge cases, regressions, and UX-breaking issues.
- Validate new features against acceptance criteria, including negative paths and permission boundaries.
- Reproduce issues reliably and provide high-signal bug reports (steps, expected vs actual, logs, screenshots).
Test Automation (E2E / Integration / API)
- Build and maintain automated test suites (UI and API) to protect core workflows and prevent regressions.
- Create stable test data strategies and fixtures aligned with real usage patterns.
- Integrate automated tests into CI to provide fast, actionable feedback to engineers.
Release Confidence & Regression Protection
- Coordinate regression test cycles for releases and hotfixes.
- Help define release checklists and readiness criteria (including rollback validation where relevant).
- Track defect trends and propose targeted improvements to reduce repeat failures.
Collaboration & Enablement
- Partner with Product Engineers early (during planning) to clarify acceptance criteria and testability.
- Advocate for testable design: observability, predictable states, clear error handling, and feature flags when appropriate.
- Drive quality learning loops: post-release issues → root causes → improved tests/standards.
Required Technical Skills
- Strong fundamentals in QA methodologies: exploratory testing, regression strategy, risk-based testing.
- Experience testing web applications end-to-end (UI + API + data validation).
- Ability to design and maintain automated tests (framework-agnostic: Playwright/Cypress/Selenium equivalents).
- Experience with API testing (REST/GraphQL), including auth, rate limits, and negative testing.
- Familiarity with CI workflows (e.g., GitHub Actions) and integrating test suites into pipelines.
- Strong bug reporting discipline: reproduction steps, evidence, prioritization, and clear communication.
- Comfort working with databases at a basic level (querying/verifying data, understanding relational integrity).
Nice to Have
- Experience with performance testing and basic load/stress methodologies.
- Experience with security-minded testing (permissions, tenant isolation, input validation).
- Experience building test infrastructure: mock services, seeded environments, test data factories.
- Familiarity with observability tooling (logs, tracing, metrics) to speed up debugging.
- Experience working in fast iteration environments where quality must scale without slowing delivery.
Behavioral Expectations
- Quality ownership: treats quality as a system, not a phase.
- High-signal communication: writes bugs that engineers can fix quickly and confidently.
- Automation mindset: prioritizes repeatable protection over repeated manual effort.
- Pragmatic rigor: balances speed and confidence; focuses on highest-risk paths first.
- Collaborative: works upstream with engineers to prevent defects, not just catch them.
- Consistency: maintains standards and keeps test suites stable, readable, and useful.