QA Engineer

You’ll be part of the QA team working on a mature, modular social platform used daily by ~250k active users worldwide - a full-featured messenger with 1:1 and group chats, a social timeline, stories, audio/video calls, push notifications, and broadcast.

The codebase spans ~37 Gradle modules and over 300k lines of code, with both legacy and modern paradigms running side by side.

This is not a greenfield project. It’s a living system that requires someone who can navigate complexity, keep shipping, and treat every release sign-off as a genuine commitment.

Salary: 10 500 - 14 000 PLN net/month B2B / 8 788 - 11 717 PLN gross/month UOP

Key responsibilities

1. Analyse new features for business and logical consistency - identify quality risks before implementation begins
2. Design and maintain test scenarios and test sets in TestRail for new functionalities and regression cycles
3. Manually verify sprint tasks across Android, iOS, and Web - validating compliance with business and design requirements
4. Reproduce bugs, document reproduction steps, assess impact and scope, and support the team in root cause analysis
5. Log bugs and improvement proposals in Jira with clear priority, product impact, and a recommendation: current sprint or backlog
6. Oversee release readiness: final quality acceptance and on-schedule delivery verification
7. Triage client-reported bugs - analyse, classify, and route to the right person

What do we need for this position?

Project experience

• Experience independently leading QA for entire features or subsystems with minimal supervision

Testing craft

• Risk-aware test design. You design test plans that account for edge cases, non-functional risks (performance, accessibility, security, data integrity), and - just as importantly - conscious decisions about what not to test, with reasoning
• Exploratory testing instinct. Scripts catch what you anticipated. You find what you didn't
• Documentation discipline. What you write can be handed off to another QA without a follow-up question
• Process awareness. You notice when QA itself slows the team down, and you propose fixes - not just flag it

Collaboration & ownership

• Early involvement. You join requirement and design discussions, not post-sprint reviews
• Honest communication. You tell the team clearly what can and can’t be adequately tested, and why

Nice to have:

• Daily working knowledge of TestRail and Jira
• Experience testing mobile apps (Android, iOS) and web platforms
• Familiarity with release management processes
• English at B2+ - written communication with international clients is part of the role
• Test automation experience for web apps (Cypress)

Our recruitment process

1. Culture & mission fit meeting with Recruitment Team (abt. 45 minutes)
2. AI fluency assessment via AI CRED (aicred.ai) - a short online test measuring competency across 5 AI dimensions
3. Competency interview with the team (abt. 60 minutes)
4. If any additional step is needed, we’ll let you know
5. The decision - and if it’s yes, welcome on board