Must Haves:
- 5+ years of Quality Assurance and Testing experience over a range of implementation environments.
- 3+ years of experience with automating tests using Python on data pipelines.
- 3+ years of SQL (specifically T-SQL on MS SQL Server Databases) experience validating complex database schemas and data pipelines.
- 3+ years of experience with data modelling for both transactional and analytics databases
- 1+ years of experience with load and performance testing in systems built on IoT & cloud software.
Nice to Haves:
- Azure Cloud Platform and Azure DevOps.
- Oil and gas knowledge would be an asset, specifically fracturing and completions.
- Web-based front ends in TypeScript and React.
- WebAPI backends in .net core using C# and F#.
- Writing comprehensive unit tests in xUnit.
- The ideal candidate has an engineering or software degree, along with good oral and written
communications. You must be a team player with excellent communication skills.
What is required in the role:
- Validate the work of the development team and test new and existing features.
- Oil and gas knowledge would be an asset, specifically fracturing and completions.
- Create and implement test plans.
- Develop, maintain, and enhance QA processes and procedures.
- Review and improve documentation.
- Develop automated test scripts to automate manual, repeatable time-intensive tasks.
- Play an active role in testing both new features and bugs, develop and utilize software to capture
performance data, and evaluate individual aspects of the software.
- Troubleshoot issues and help determine root causes of software problems.
Expertise and Skills
- Quality Assurance, QA Analyst 5 - 7 years
Priority Requirements
- Must-have: Please outline your experience as an Intermediate QA Analyst who has performed
automated testing (Python) as well as SQL and Data Modeling in a software development team.
- Nice-to-have: How do you feel about the various software development methodologies (e.g. Agile vs.
Waterfall)?
- Must-have: What do you feel are the pros and cons of automated testing?
- Must-have: What do you feel is the difference between testing a feature with good documentation and
one without?