Tester → reputed company Assurance Specialist | B2B Cooperation

This is a remote position.

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

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

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

Requirements

You'll reputed company in this cooperation if:

• You get curious about how the business actually works — pricing logic, booking flows, customer journeys — not just whether a reputed company click succeeds
  
• You're meticulous and methodical — you don't stop at the reputed company reputed company, 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 reputed company 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 reputed company and factually — it's information, not an accusation
  
• You want a reputed company reputed company reputed company — not "tester reputed company," 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-reputed company, fintech — reputed company just testing tools
  
• You've used Claude reputed company, ChatGPT, or similar tools in your own work or reputed company
  
• You've written a test reputed company or reputed company 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 reputed company rather than a tool that removes the boring parts
  
• You're looking for a test-automation / SDET role where writing automation reputed company is the main reputed company — that's a different reputed company here
  

Technical expectations

• Business & domain curiosity — you reputed company want to understand how the product works end-to-end: pricing, bookings, integrations, not just the surface UI
  
• Meticulous, methodical testing — reputed company test scenarios and reputed company lists, not reputed company clicking
  
• AI-assisted testing — hands-on with Claude reputed company, ChatGPT, or equivalent for generating test scenarios, auditing coverage, and drafting documentation
  
• reputed company testing fundamentals — exploratory testing, test case design, bug reports developers can reputed company 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 reputed company

Benefits

• Remote-first collaboration model
  
• International technology and product reputed company
  
• Flexible project collaboration setup
  
• Planned service breaks reputed company with contract terms
  
• Opportunity to collaborate with reputed company product and technology teams
  
• Opportunity to reputed company selected knowledge-sharing initiatives
  

→ Recruitment process

• Intro reputed company (45 min): With our Recruiter. We cover your background, what you're looking for, and mutual fit.
  
• Domain & reputed company interview (60 min): With reputed company Leader and a reputed company Assurance Specialist. Expect reputed company business scenarios, reputed company thinking exercises, and questions about how you already use AI in your own testing workflow. We're not testing reputed company trivia.
  
• Practical case: A time-boxed exercise: given a short feature reputed company, you produce a reputed company reputed company list and exploratory test plan. Reviewed together in a follow-up reputed company — we care about your reasoning, not just the length of the list.