QA Specialist (Technical Support)

The purpose is to find, reproduce and document defects early, validate that data and behaviour are correct, and give clear technical evidence when an issue needs a developer or infrastructure fix.

Requirements

Key responsibilities

• Investigate application issues using logs, database queries, configuration and environment checks.
• Work in Linux/Unix over SSH for basic OS-level troubleshooting: process, disk, permission, connectivity and service checks.
• Query relational databases to confirm data state, trace transactions and validate expected versus actual results.
• Create, maintain and execute test cases for functional, regression and UAT cycles.
• Run manual tests against agreed requirements and release notes, and record evidence.
• Support automated test runs, review failures and separate environment issues from product defects.
• Identify, reproduce and log defects with steps, data, logs, screenshots and expected results.
• Validate data before and after changes, migrations and fixes.
• Support UAT: prepare data, guide users, capture findings and track retests.
• Work with developers and infrastructure teams to isolate whether a fault sits in the application, data, integration or platform.
• Check monitoring and alerting output where available, and escalate with a clear impact and timeline.
• Confirm fixes in the correct environment before a defect is closed.
• Maintain test evidence, known-issue notes and handover comments for releases.

Requirements

• 5 years’ experience in technical support and/or QA inside a software development environment.
• Application log investigation.
• SQL and relational databases.
• Linux/Unix, including SSH.
• Basic OS-level troubleshooting.
• Manual testing.
• Functional and regression testing.
• UAT participation or coordination.
• Test case creation and execution.
• Defect identification and reporting.
• Data validation.
• A working understanding of software development environments, releases and environments such as dev, test and production.
• Strong troubleshooting and problem-solving, with a habit of proving the cause rather than guessing.

Advantageous

• ELK Stack or similar log search.
• Azure Monitor and broader Azure exposure.
• API testing, including Postman.
• Automated testing.
• CI/CD pipelines.
• Java or other application troubleshooting.
• Database troubleshooting beyond basic selects: locks, bad data, failed jobs.
• DevOps exposure.
• Monitoring tools.
• Experience working day to day with developers and infrastructure teams.