8 days ago
Reach out directly about this role
Work Format
Remote
Employment
Full-time
By job title
AI writes it from your resume. You only have to send it.
Hi! We are looking for a Manual QA Engineer for a music B2C product.
✅ Format: remote ✅ Employment: fulltime ✅ Product: mobile apps + web + public API ✅ No autotests — we test manually
⭐ About the product
A service for independent artists: from track idea to release, promotion, and results analysis. Mobile applications, web, public API, integrations with external platforms, real-time interaction, AI functionality.
There are no autotests currently — the project is actively changing, and it's too early to write them. But if you have an opinion on what and when should be automated, that's a plus.
🔧 What to do
— Test the product as a whole: mobile apps, web, API, service interactions between each other — Check not only what is described in the acceptance criteria, but the system as a whole: edge cases, integration failures, behavior with poor network and parallel actions — Maintain test documentation in such a way that another person can follow it — Participate in requirement analysis before development starts, not after — Suggest changes to the testing process when the current one ceases to cope
✅ What should be in your experience (all mandatory):
🔸 Working with REST API manually: analyzing requests and responses, reproducing issues via Postman, reading logs 🔸 Browser DevTools: network, console, storage — as an investigation tool, not just for viewing 🔸 Mobile application testing: different OS versions and devices, behavior on network loss, traffic interception 🔸 SQL: go to the database and check that the data is stored as expected 🔸 Test cases and bug reports that can be reproduced from the first attempt based on the description
➕ Will be a plus
Asynchronous systems and queues (RabbitMQ / Kafka / NATS) · testing AI functionality and nondeterministic scenarios · LLM and AI API · MCP · using AI tools in QA work
🤝 How we work
Remotely. Everyone has bugs — we discuss the problem, not the person. We argue about implementation, priorities, and severity, but not with each other. Priorities change throughout the day — this is normal. An unspoken idea is worse than a bad one.
📋 Selection process
1️⃣ Apply: resume + answers to the three questions below 2️⃣ 30-minute call 3️⃣ 60-minute technical interview 4️⃣ Offer
📨 How to apply
Resume + answers to three questions, briefly and to the point (5–10 sentences for each):
1️⃣ The last bug you found that wasn't visible in the acceptance criteria: how you found it, how you reproduced it, what was the cause. 2️⃣ A situation where your bug was closed as "not a bug", and you disagreed: what you did and how it ended. 3️⃣ A bug that reached production with your involvement: why it slipped through and what you changed in the process afterward.
💰 Please state your salary expectations in your response.
❗ Applications without answers to the questions will not be considered.
📲 Apply — via Telegram: