QA Automation Engineer – Freelance

Quick Facts

• Work Policy: 100% Remote, flexible work, CET hours
• Job Type: Freelance (minimum 6-month project, starting beginning of November 2026)
• Pay Rate: Up to 155 PLN/hour, negotiable

About Netguru

Netguru matches freelancers with project work based on their skills, giving them flexibility over when, where, and how they work. This particular engagement sits across industries such as FinTech, B2B software, and e-commerce, and runs as a long-term collaboration rather than a short one-off gig.

What You’ll Do

Although the posting doesn’t break responsibilities out separately, the role is clearly centered on writing and maintaining automated tests from scratch, running them across QA, UAT, and Production environments through CI/CD, tracking test cases and results in a test management tool, and generally taking ownership of the automation suite rather than just contributing to it occasionally. The emphasis throughout is on bringing a developer mindset to testing: making incremental improvements to test code, strengthening existing automation, and reducing reliance on manual testing over time.

What You’ll Need

• Strong JavaScript skills, including writing and maintaining test code from scratch
• Hands-on experience with WebdriverIO for test automation
• Solid experience with Mocha and Chai
• Experience with CI/CD pipelines, preferably Drone CI, running automated tests across QA, UAT, and Production
• Experience with TestRail or similar test management tools
• A developer mindset: making incremental changes to test code, improving existing automation, and relying less on manual testing
• Ability to work independently and take ownership of the automation suite

Nice to Have

• Experience testing Salesforce applications and related architectural changes
• Experience testing standalone React-based applications

Benefits

100% remote, flexible work; the chance to work alongside an experienced developer team and grow both technical and soft skills; development-friendly processes including CI, CD, code review, and bug bashes; and a long-term collaboration on challenging products rather than a quick, disconnected project.