Manual QA Engineer (Junior)

We respond to every candidate. Your application will not be ignored. Please write why you would like to work together.

If you see this vacancy in several weeks/ month - write anyway, we often hire people of different levels.

The main information (if you don't like reading long descriptions) fully remote - you need to get dressed just for occasional boring meetings full-time strong QA Team experience: 0-1 year English: B1+ start date: as soon as possible number of people needed: 3 long-term cooperation: we want you to work with us for as long as you can :)

About Us This position is a direct contract with a leading UK company.

The Company builds B2B legal technology that helps law firms deliver faster, higher-quality work. The Company’s platform streamlines legal workflows involved in a niche area of law so lawyers can accelerate drafting, negotiation, and compliance at scale.

Tech highlights (as if it’s important for a QA position) - we operate a single-tenant SaaS architecture hosted on AWS across multiple regions, built with a modern stack: Python/ Django 6, React 18/TypeScript, PostgreSQL, Redis, Elasticsearch/ OpenSearch, S3, ECS, and Lambda.

Our teams work in Agile Scrum squads, supported by strong CI/CD, IaC (Terraform/ Terragrunt), and security-first practices (SOPS, KMS). It’s only a web application, no mobile.

About Team At the moment, our team is mainly located in Europe - Developers, Manual QAs, Automation QAs, Project Managers, UI/UX Designers, DevOps Engineers.

We value: speaking up (good ideas are welcome) growth (we’ll help you get there) learning & innovation (we like experiments that don’t break Prod)

About You have up to 1 year of experience in QA or relevant practical training (courses, internships, or personal projects) see bugs where other people don’t understand the basics of best practices in the QA process, testing, and test cases management want to work with test cases and auto tests have a stable internet connection. Start your response with "net" have an understanding of API testing It would be cool if you also have basic knowledge of Gherkin have basic SQL knowledge

Your tasks will mainly be rigorous testing bug reporting creating/ updating test cases reviewing auto tests results

The hiring process screening questions (10-15 mins) a test assignment (up to 90 mins) a job interview with the Head of QA (1-2 hours) possibly a job interview with CTO (30 mins)

Our benefits environment where you can learn a lot (strong QA team + challenging product and tasks) possibility to work from any place in the world as long as you have an internet connection and a laptop professional trainings, conferences, and certifications covered by the company

Our culture no micromanagement no bureaucracy (well, almost :) no useless tasks satisfaction from work work-life balance respect & trust support

Q&A Is there a contract?

• Yes, we sign a contract

Is it a monthly fixed-priced or hourly-based payment?

• Monthly fixed-priced

Do you hire people for several months?

• No, it's a long-term position (can be 5+ years)

What testing will I need to do?

• Mainly functional, UI, usability, integration, API; smoke, regression

What tools do you use?

• Mainly Xray, Jira, Confluence, Slack, Zoom, Gsuite, Postman, or similar for API testing

Do you have auto tests?

• Yes, we have auto tests written using Python, Playwright, pytest, GitHub actions, and Allure reports

Is it possible to change the position to Automation QA in the future?

• Yes, we support moving to Automation QA or any other direction if you're interested (PM, UI/UX, etc.)

What rate will I have?

• We usually ask for a desirable rate and then offer a position to people who have the best rate/ skills ratio. Over time, your rate will increase multiple times with good performance

Do you provide laptops/ devices?

• For now, no. This is considered by management in 2026

Is there a min/ max hours limit for a month?

• We're looking for full-time candidates, so preferably not less than 160h per month

What language do you use?

• English/ Ukrainian/ rus is used for communication. English - for documentation, bug reports, test cases, etc.

Oh, may I ask XXXX XXXX?..

• Yes :)