Technical QA Engineer (Laravel + Vue 2, post-deploy), EU property-tech + SaaS, remote

Role
We ship small changes to our live platforms often. We want a technical QA engineer with a real developer background: you think like a user, but you can also read the code path, review merge requests, and tell us when the fix or the AI-suggested change should be different. After each release you check that landlords, renters, candidates and companies can still get from A to B to C. You are not the person who builds features full time, but you are close to a half-developer on our stack. Speed and quality, not one at the cost of the other.

About us
We are a European property-tech company. We run several live rental and property platforms on one shared Laravel and Vue 2 codebase, plus a recruitment SaaS where candidates record video intakes for companies and agencies. We use GitLab merge requests. We care about security, privacy, and small reviewable changes.

Where you sit in our flow
We roll out to production often and we want to keep that pace. Developers deploy; you are not a gate before release and you do not own the deploy button. After each production rollout you test on ---------- the journeys that release touched, then the critical paths users depend on, on desktop and mobile, with test accounts and safe paths where we need them. You are the second check after go-live, not a blocker in front of it. When something fails for a real user, you report it fast with steps, expected versus actual, and enough detail that a developer can fix it the same day.

How we work
Our developers work with AI coding assistants and keep their changes small. You test the outcome in the browser and you sanity-check the change in GitLab: read the diff, spot risky patterns, and push back when generated code is sloppy or the wrong layer was touched. If something works on paper but feels wrong in the browser, you say so. You may use AI tools yourself, but the pass or fail comes from what you verified, not from what the model claimed.

What you will do

• After each production rollout, smoke-test the journeys that release touched, on desktop and on mobile
• Re-run the critical journeys per product: listing a property, booking a viewing, uploading documents, recording a video intake, reviewing candidates
• Explore beyond the release note when something looks fragile
• Check that a change on one platform did not break or leak into another platform on the same codebase
• Write clear bug reports: steps to reproduce, expected versus actual, severity, environment, browser and device, screenshot or short video
• Point developers to the file, layer, or request: Blade, Vue component, controller, query, or API response
• Give UX feedback in plain words, for example "a landlord would not know what to do here"
• Review merge requests and recent commits: what changed, what could regress, what should have been tested, what you would do differently
• Suggest concrete improvements to developers (and to AI-generated patches): safer query, clearer validation, better error handling, smaller scope

Requirements

• Strong technical background: you have worked as a developer or as QA embedded with developers, and you can read Laravel and Vue 2 code in a real codebase, not only tutorials
• Hands-on experience with Laravel web applications and Vue 2 front ends in production, or equivalent depth with a similar PHP plus SPA stack and a clear plan to work in our Vue 2 patterns
• Experience with multi-brand or multi-tenant products: one codebase, several sites or customers, and you know how a fix on one brand can break another
• Proven QA on live web products, with examples where your report or your review caught something others missed
• You think in user journeys and in the people behind them
• Clear written English, short and precise
• Solid GitLab or GitHub habits: branches, merge requests, reading diffs, commenting on specific lines
• Browser developer tools: console, network tab, status codes; you tie UI symptoms to backend responses
• Comfortable challenging AI-assisted development: you review output like a senior teammate, not like a checklist-only tester
• Reliable and self-directed: you find the next useful check without being told
• This role is QA and review first. We do not hire you primarily to ship features. Occasional tiny fixes are a bonus, not the job description.

Nice to have

• Accessibility basics: keyboard use, contrast, readable forms
• Ideas for light automated checks or regression notes, without making automation the whole role
• Docker-based local setup or Laravel Mix familiarity

Working hours: full time, 40 hours a week, Monday to Friday, 09:00 to 17:00 Amsterdam time. That is 15:00 to 23:00 in the Philippines in European summer, and 16:00 to 00:00 when Europe switches to winter time. Please state your timezone and the window you can reliably cover each workday.

Paid trial (before full engagement)
A paid trial week of about five working days, full time, at $3 per hour, tracked with TimeProof after signing. We give you test accounts, a short list of recent rollouts to verify the same way you would after go-live, and read-only visibility on merge requests where useful. You test like a real user on desktop and mobile, file bug reports and UX notes, and add technical review comments where you see risk in the change. You may use AI tools, but you must not paste secrets, customer data, production logs, or private business information into external tools. You must be able to explain and defend everything you report and every review comment.

The deal
Remote, full time, long term. Hours are tracked with TimeProof. Rate: $3 per hour to start, reviewed on quality and impact. This is a long-term role, not a one-off project.

How to apply (English, no template letters)
1) Start your message with ABC.
2) One bug you found in production that others missed: how you reproduced it and how you reported it.
3) How you would test a release right after it goes live, without slowing every release down.
4) One example of UX feedback you gave that changed a flow.
5) A form submits and nothing happens. What do you send the developer?
6) One merge request or diff you reviewed: what you looked at in the code, what you worried about, and what you asked the developer to change.
7) Your timezone and the Amsterdam-time window you can cover.

Keep it short. Selected applicants do a short video intake on our platform before we talk.

Do not apply if

• You are not the person who will do the work
• You only know QA in theory and cannot give real examples
• You have never read application code or merge request diffs in a real job
• You only write automated tests and do not think about the people using the product
• You want a pure development role with no testing responsibility
• You cannot write clear English
• You would paste secrets, production logs, or customer data into external tools