Quality Assurance Engineer

Role summary

We are looking for a mid-level QA Engineer to test Tiger Technology’s hybrid cloud storage software before it reaches customers. The work combines manual and automated testing with building realistic test environments, which often include third-party storage, cloud and infrastructure products that our software works with.

The QA Engineer works closely with engineers and product owners, and is trusted to plan testing independently, find real problems early, and report them clearly. The QA Engineer reports to CTO.

Responsibilities

Plan and test

• Review requirements and designs, and turn them into test plans and test cases.
• Run manual tests on new features, fixes and releases, including exploratory testing where scripted cases are not enough.
• Test functionality, compatibility, performance and failure scenarios of our software with the products it integrates with.

Build and maintain test environments

• Set up and maintain complex test environments that include third-party products, for example storage systems, cloud services, operating systems and network components.
• Reproduce customer setups and issues as closely as practical.
• Keep environments documented, repeatable and cost-aware.

Automate

• Create and maintain automated tests and regression suites, and run them as part of regular builds and releases.
• Decide what is worth automating, and keep the suites reliable and fast enough to be used.

Report and improve

• Log defects in our issue tracker with clear steps, evidence and impact, and follow them through to verification.
• Give product owners and engineers an honest view of quality and release risk.
• Suggest improvements to our test practices and tools, including the use of AI in testing.

Requirements

• 3 to 5 years of professional experience in software QA.
• Solid manual testing skills: test design, exploratory testing, and clear bug reports.
• Practical experience with test automation, using one or more common frameworks and a scripting or programming language (Python, PowerShell, C# or similar).
• Experience setting up and maintaining complex test environments, including third-party products, with virtual machines, networking and operating systems (Windows and Linux).
• Experience with an issue tracker such as Mantis, Jira or similar.
• Understanding of the software development and release cycle, and of regression and release testing.
• Regular, practical use of AI tools in daily work, with the judgement to verify their output.
• Clear written and spoken English.

Nice to have

• Experience with Mantis.
• Experience with storage systems, file systems or cloud storage (AWS, Azure, Google Cloud).
• Experience testing in regulated or data-sensitive environments such as healthcare or video surveillance.
• Experience with CI/CD pipelines, containers or infrastructure as code for building test environments.
• Experience using AI to generate test cases, test data or automation code.
• Relevant testing certification (for example ISTQB).

What we look for

• Thoroughness. Notices what others miss, and tests what could go wrong as well as what should work.
• Technical curiosity. Wants to understand how the product and the third-party systems around it actually behave.
• Persistence. Keeps working through difficult setups and hard-to-reproduce problems until the cause is clear.
• Honest reporting. Describes quality and risk as they are, including when the news is unwelcome.
• Clear communication. Writes defect reports that an engineer can act on without asking questions.
• Willingness to improve. Learns new tools and methods, and improves how testing is done.

First 3 months

Understands our products and test practices, uses our issue tracker and tools, and tests features and releases independently.

By 6 months

Has built or rebuilt at least one complex test environment with third-party products, and has contributed to the automated regression suite.

By 12 months

Owns testing of a product area, including its environments and automation, and has suggested improvements to our test practices that the team has adopted.