QA Engineer

Fully Remote · SaaS · Cloud

TopTechPhoto is a product company building a suite of SaaS tools used by teams around the world. Our products span digital asset management (Pics.io), product information management (Toriut.com), and an AI-powered knowledge hub (Provenyx.ai). Across all three, we process large volumes of data, power complex workflows, and ship to thousands of users daily.

We ship fast, test rigorously, and invest heavily in automation, reliability, and smooth engineering processes.

What We Build

Our ecosystem spans three products and a shared platform underneath them:

Pics.io — a React-based DAM web app with mobile clients and integrations for Adobe, Google Workspace, Shopify, Zoho, WordPress, and more

Toriut.com — a PIM platform handling complex product data structures, bulk operations, and catalog workflows

A Node.js backend powering public APIs across all products

MongoDB, Elasticsearch, and cloud-native services on AWS & GCP

A CI/CD pipeline that deploys multiple times per day

A growing suite of internal tools, automations, and AI-assisted workflows supporting quality and releases

What You'll Work On

As a QA Engineer, you'll ensure that users receive updates frequently, safely, and without regressions. You'll work closely with developers, product managers, and designers throughout the entire development lifecycle — and you'll actively use AI tools to work smarter, not just harder.

Examples of challenges you'll tackle:

Exploring web and mobile-adapted UI flows to identify issues before they reach users

Writing, maintaining, and organising test cases in QASE

Planning and coordinating releases across multiple teams

Automating test scenarios using Playwright in TypeScript/JavaScript

Validating API behaviour, client–server interactions, networking, and performance using Postman or Swagger

Stress-testing complex media workflows — uploading, previewing, transcoding, streaming

Ensuring Pics.io behaves consistently across browsers, devices, and environments

Leveraging AI-assisted tools to generate test cases, analyse failure patterns, accelerate coverage, and reduce repetitive manual work

Who You Are

You're a QA Engineer who enjoys exploring systems, finding edge cases, and ensuring products behave predictably for thousands of users. You think in risk, coverage, and user impact — and you're comfortable using AI as a genuine productivity multiplier, not just a buzzword.

Requirements

2+ years of experience testing web applications

Solid understanding of QA methodologies, SDLC, Agile, and Scrum

Hands-on experience writing automated tests in TypeScript or JavaScript using modern frameworks — Playwright, Cypress, or similar

Experience writing structured test documentation: checklists, test cases, bug reports

Working knowledge of REST APIs; hands-on with Postman and/or Swagger

Proficiency with bug tracking and test management tools — Jira, QASE, or equivalent

Comfortable working in cross-functional teams alongside developers and product managers

Strong analytical thinking and sharp attention to detail

Understanding of how modern web apps work — AJAX, HTTP, CDN, caching, HTML/CSS

Nice to have

Practical experience using AI tools to streamline QA — test generation, failure triage, exploratory assistance, or pipeline automation

Experience with mobile app testing (iOS / Android)

Familiarity with CI/CD pipelines — GitHub Actions, Jenkins, or similar

Experience in release management

Background in security, performance testing, or media/video streaming environments

Curiosity, independence, and attention to detail matter more than ticking every box.

How We Work

We are a senior-leaning distributed team that values high-quality and frequent releases, clear communication, and reliable processes. You'll have autonomy in organising your work, freedom to propose improvements, and full access to the product, dev and ops teams. We support continuous learning through paid tools, courses, conferences, and books — including AI tooling your role benefits from. Remote work is fully supported; your location doesn't matter as long as communication is smooth and consistent.

Test Challenge

To proceed to the interview stage, please complete a practical assignment. Register at Pics.io, explore the product, and complete both parts below.

Part 1 — Testing Plan

Choose any feature in Pics.io that genuinely interests you — we recommend starting with the video player or saved searches, but the choice is yours.

Write a testing plan for your chosen feature. We want to see your approach, structure, and how you think about quality across multiple dimensions — not exhaustive step-by-step descriptions.

Your plan should address:

What you're testing and why you chose it

Which testing aspects you're covering and how — for example: functional behaviour, UI and UX, API and networking, performance, security, edge cases, and cross-browser or cross-device consistency

Core scenarios vs. secondary ones, and how you prioritise

Which areas are worth automating and why

Tools you'd use — including any AI tools that fit naturally

Metrics and benchmarks you'd track

How you'd communicate results and findings to the team

Use any format you like: Google Docs, QASE, TestRail, Notion, and so on.

Note: Avoid features that require testing auth flows or team management — those areas are protected on the backend and won't behave normally under automation or manual probing.

Part 2 — Playwright Automation

Automate a meaningful subset of what you planned in Part 1 — ideally the same feature, so we can see how your thinking translates into code.

What we expect:

A real GitHub repository with your tests committed and pushed — not a zip file or a Gist

Tests written in TypeScript, using Playwright

A README.md that explains what you chose to test, why, and how to run the suite locally

At least one AI tool used somewhere in the process — test generation, code review, selector strategy, whatever felt natural. Briefly mention in the README which tool you used and where it helped

Reviewing the Test Challenge:

We're not counting test cases. We want to see how you structure a suite, how you handle selectors and assertions, how readable your code is, and whether you made a deliberate choice about what's actually worth automating. A small, well-reasoned set of tests beats a large, flimsy one.

There are no deadlines or time limits. Send us links to both your testing plan and your GitHub repository when you're ready.

A note before you answer Qualifying Questions (Контрольні запитання):

We're looking to get to know you as a person, not review a polished AI-generated response. These questions have no right answers — we're genuinely curious how you think. Candidates who answer in their own voice, even imperfectly, will always stand out over those who delegate their personality to a language model. We'll notice the difference.