QA Engineer
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 2h ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 102d ago
The date the source published, not the day we noticed it (2026-07-02). Last seen at its source 1h ago.
Is it remote?
Marked remote on the employer's board
Their board carries a remote setting on this posting — a field they filled in, not wording we read. The location field names somewhere specific, which is usually where the team or the entity sits.
Who may apply?
Poland
The description states no restriction of its own. This is the source's own tag.
Pay
PLN 100–120/hr
Published by the source in its own salary field. Shown in the posting's own currency and period; we never convert.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
Recruitee employer's own board first seen 2h ago · last seen 1h ago
The listing
At Digital Forms we help mid-sized service businesses go through digital transformation — part consulting, part building the software ourselves. And when you build the software yourself, quality isn't a checkbox at the end. It's where the whole promise gets kept or broken.
We're kicking off a new module of a platform we've already built for an existing client from the USA, operating in a regulated domain. Design work (UX/UI and architecture) starts now, and development follows right after — which means we want a QA Engineer in the room from the very beginning, not called in once the bugs start piling up.
The good news: requirements are already defined. You won't spend your first month guessing what to test. You can get hands-on from day one — shaping the test strategy, writing test cases, and owning the QA scope end-to-end as the module takes shape around you.
It's a hands-on role in an international setup: the team is mostly Polish, the client is American, and all project documentation, specifications, and bug reports are in English — with regular meetings with the client team.
The engagement: full-time. Around 60% of your time will go to the new module — that project runs from mid-July to 10 November — with the rest supporting other projects across our portfolio. And if the collaboration works well, we're open to continuing beyond November.
What you'll be doing
Functional and regression testing of web portal applications
Integration testing across platform components
Testing in AWS-based environments
Writing and maintaining test cases, test plans, and bug reports in English
Collaborating with developers, PM, and the international client team
Participating in QA process definition and continuous improvement — if you see a better way to do things, we want to hear it
Requirements
Hard skills:
2–4 years of hands-on experience in software QA / testing
Solid experience with functional and regression testing of web applications
Familiarity with standard testing tools (e.g. Selenium, Cypress, Postman, or similar)
Experience testing in cloud environments — AWS preferred
Jira proficiency
Ability to work independently and take ownership of your QA scope
Soft skills & logistics:
Strong English, both written and spoken (B2+) — you'll use it daily with the client team
Availability until 18:00 CET on working days (occasional client meetings may fall close to this window)
Nice to have
Polish language — the core team is Polish, so it makes day-to-day collaboration easier
Experience in a regulated domain (insurance, healthcare, medtech, pharma, or similar)
ISTQB certification
API testing and CI/CD pipeline experience
Previous experience in fast-paced consulting or client-facing projects
What we offer
100–120 PLN/h net (B2B, VAT invoice — a Polish business entity keeps things simplest)
100% remote, full-time
A new module with requirements already defined — hands-on work from day one
International project for a US client in a meaningful, regulated domain — with an AI/automation element in scope
A clear rhythm: daily standups, bi-weekly planning and review/demo, team retros as agreed with the team
Collaborative, flat team structure — your voice on QA process counts
Strong extension potential beyond the first project