Quality Assurance Specialist, B2B Cooperation

This is a remote position.

Testing in the AI era isn't about running the same regression script every sprint. Test generation has moved from the tester's hands to the developer's — Claude Code writes and runs tests as part of implementation, not as a separate phase afterward. What AI can't replace is domain instinct: knowing how real users actually behave, where the business logic is fragile, and which edge case is the one that matters. That instinct takes time to build.

This is a Tester cooperation, not a Quality Assurance Specialist one — but the domain knowledge you build here is exactly what a Quality Assurance Specialist scope of work requires. At Profitroom, testers who develop deep business and product understanding are the ones positioned for QA Specialist cooperation later: domain experts who guide developers before they build, explore production systematically, and own the quality health of a whole product area.

You'll be manual-first, but manual in the modern sense of the word: comfortable using AI to generate test scenarios, audit coverage, and draft documentation, so your time goes into judgment and domain understanding — not repetitive execution.

"The system is healthy when a Quality Assurance Specialist says it is. Not when all tickets are green." That's the standard this role is building toward.

Scope of cooperation

• Test execution for features before release — built on structured edge-case thinking, not just clicking through a script

• Exploratory testing — regular, independent sessions on production, not limited to what shipped this sprint

• AI-assisted test scenario generation and coverage checks — you use AI to work broader and deeper, not to skip the thinking

• Documentation — accurate product and technical docs, drafted with AI, validated by what you actually know about the domain

• Flagging and fixing broken processes — stale docs, manual reporting, repetitive rituals: you propose the improvement, you don't just work around it

Requirements

You'll thrive in this cooperation if:

• You get curious about how the business actually works — pricing logic, booking flows, customer journeys — not just whether a button click succeeds

• You're meticulous and methodical — you don't stop at the obvious edge case, you look for the one nobody thought of

• You use AI tools to test smarter and faster, and you're not threatened by them handling the repetitive part

• You notice a broken process — a manual doc update, a rotting test suite, a report someone rebuilds by hand every week — and you want to fix it, not just work around it

• You're comfortable reporting a bug clearly and factually — it's information, not an accusation

• You want a real growth path — not "tester forever," but domain mastery that eventually makes you the person developers consult before they build

Bonus points:

• You've automated part of your own workflow (docs, reporting, test data) with AI tools without anyone asking you to

• You have exposure to a specific business domain — travel, hospitality, e-commerce, fintech — beyond just testing tools

• You've used Claude Code, ChatGPT, or similar tools in your own work or personal projects

• You've written a test strategy or edge-case list that developers actually followed

Probably not for you if:

• You want a script to follow and a checklist to tick, not a problem to think through

• You see AI as a threat to your job rather than a tool that removes the boring parts

• You're looking for a test-automation / SDET role where writing automation code is the main skill — that's a different path here

Technical expectations

• Business & domain curiosity — you actively want to understand how the product works end-to-end: pricing, bookings, integrations, not just the surface UI

• Meticulous, methodical testing — structured test scenarios and edge-case lists, not ad-hoc clicking

• AI-assisted testing — hands-on with Claude Code, ChatGPT, or equivalent for generating test scenarios, auditing coverage, and drafting documentation

• Manual testing fundamentals — exploratory testing, test case design, bug reports developers can act on without follow-up questions

• Process awareness — you notice inefficiencies and propose or build the fix, rather than living with them

• Communicative Polish and English — Polish for business-domain depth, English for documentation and cross-team collaboration

Tools & domain focus

Manual testing · Exploratory testing · Edge-case design · Claude Code · AI test-scenario generation · AI-assisted documentation · Jira · Confluence · Bug reporting · API basics (Postman) · Business domain: hospitality & bookings

Benefits

Contract terms: B2B cooperation. Monthly compensation range: 11**,000–15,600 PLN net** , depending on experience and the agreed scope of services.

• Remote-first collaboration model

• International technology and product projects

• Flexible project collaboration setup

• Planned service breaks aligned with contract terms

• Opportunity to collaborate with experienced product and technology teams

• Opportunity to access selected knowledge-sharing initiatives

→ Recruitment process

• Intro call (45 min): With our Recruiter. We cover your background, what you're looking for, and mutual fit.

• Domain & mindset interview (60 min): With the Team Leader and a Quality Assurance Specialist. Expect real business scenarios, edge-case thinking exercises, and questions about how you already use AI in your own testing workflow. We're not testing framework trivia.

• Practical case: A time-boxed exercise: given a short feature description, you produce a structured edge-case list and exploratory test plan. Reviewed together in a follow-up call — we care about your reasoning, not just the length of the list.