QA Engineer (API, Database, Project Support)

• Test strategy:Design and execute comprehensive test plans covering functional regression integration and exploratory testing across DREEFs web applications and backend services.
• API testing:Test APIs thoroughly using Postman and Swagger/OpenAPI specs - validating contracts schemas status codes error handling edge cases and performance.
• Postman automation:Write and maintain Postman collections and environments; build reusable requests tests and data-driven flows that can be shared with engineers and run in CI.
• Spec verification:Use Swagger/OpenAPI as a source of truth - cross-checking implementation against spec flagging drift and helping engineers keep documentation accurate.
• Database validation:Validate data correctness directly in the database - writing SQL queries to inspect records verify migrations and confirm that APIs and UI behave consistently with stored data.
• Test data and environments:Build and maintain test data sets and fixtures; manage test environments so that issues are reproducible and fixes can be verified with confidence.
• Bug reporting:File clear well-scoped bug reports with reproduction steps expected vs. actual behavior and the smallest example that demonstrates the issue.
• Release QA:Participate in release processes - running regression passes signing off on changes tracking hotfixes and verifying deployments in staging and production.
• Project support:Support projects across the team help run stand-ups and ceremonies where useful track action items keep boards tidy in Azure DevOps and keep stakeholders informed on progress and risks.
• Git workflows:Use Git effectively to pull branches inspect changes review PRs for testability and collaborate with engineers on fixes.
• Continuous improvement:Continuously improve QA practices: automation coverage test documentation bug triage and the feedback loop between QA engineering and product.

• Experience:2-3 years of professional QA / software testing experience on production web applications and APIs.
• Postman:Deep proficiency with Postman: collections environments variables scripting (pre-request and test scripts) collection runners and data-driven testing.
• Swagger / OpenAPI:Strong working knowledge of Swagger/OpenAPI: reading specs validating endpoints against spec identifying gaps and collaborating with engineers to keep specs accurate.
• Databases:Comfortable working directly with databases (MySQL or similar): writing SQL queries to verify data joining across tables and understanding indexes transactions and migrations at a practical level.
• Git:Strong Git fundamentals: branching pulling diffing and reviewing changes; comfortable operating inside a pull-request workflow.
• Project support:Experience contributing to project support work - tracking tickets coordinating releases maintaining boards and unblocking teammates - ideally within Azure DevOps or similar (Jira Linear).
• API fundamentals:Solid understanding of HTTP REST status codes authentication (tokens OAuth) and common API failure modes.
• Communication:Clear written communication - bug reports test plans release notes and stakeholder updates that are easy to act on.
• Quality mindset:A sharp eye for edge cases regressions and the small details that separate a working feature from a truly reliable one.

Nice to Have

• Experience with automated testing frameworks (Playwright Cypress Selenium or similar).
• Experience integrating Postman/Newman runs into CI/CD pipelines in Azure DevOps.
• Experience with load and performance testing (k6 JMeter Locust).
• Familiarity with gRPC testing.
• Basic scripting ability (JavaScript Python or Bash) for test automation and data setup.
• Exposure to the energy climate utilities or IoT domains.
• Experience using Claude Code or similar AI tools to accelerate test-writing data setup and exploratory scripting.

Qualities We Value

• Ownership:A strong sense of ownership and follow-through - you finish what you start.
• Detail orientation:Deep attention to detail - you notice the things other people miss.
• Pragmatism:Pragmatism - you focus your testing on the risks that matter rather than chasing coverage for its own sake.
• Communication:Clear respectful communication with engineers product and stakeholders especially when raising quality concerns.
• Curiosity:Curiosity and a bias for learning including staying current with modern QA and AI-assisted testing practices.
• Collaboration:Respect and kindness - we work hard push each others thinking and look out for one another.
• Availability:Reachable and responsive via text message and phone call during agreed working hours especially around releases and incident response.