Tester → QA Specialist Track

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 — which is exactly why this role exists as a starting point, not an end state.

The role

This is a Tester role, not a Quality Assurance Specialist role — but it's the explicit entry point to it. At Profitroom, testers who build deep business and product domain knowledge grow into Quality Assurance Specialists: domain experts who guide developers before they build, explore production systematically, and own the quality health of a whole product area. Tester is where that journey starts.

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.

→ Tech stack

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.

What's unique

• 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

What we're looking for

• 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

You'll thrive here 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 — you don't stop at the obvious edge case, you look for the one nobody thought of.
  
• You embrace AI — you use AI tools to test smarter and faster, and you're not threatened by them handling the repetitive part.
  
• You improve systems — you notice a broken process and you want to fix it, not just work around it.
  
• You communicate factually — you're comfortable reporting a bug clearly and factually (it's information, not an accusation).
  
• You want real growth — not "tester forever," but domain mastery that eventually makes you the person developers consult before they build.
  

Bonus points:

• Workflow automation — you've automated part of your own workflow (docs, reporting, test data) with AI tools without anyone asking you to.
  
• Domain exposure — you have exposure to a specific business domain (travel, hospitality, e-commerce, fintech) beyond just testing tools.
  
• AI familiarity — you've used Claude Code, ChatGPT, or similar tools in your own work or personal projects.
  
• Proven strategy — 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.