QA & Release Engineer — Windows Software (Part-Time, Ongoing)

Remote · ~10 hrs/week baseline (more on release weeks) · Long-term The role We build Windows desktop software used by IT providers and their customers. We need one sharp, meticulous person to own, build and manage the full application testing cycle — making sure every release is genuinely ready to go into production. You are the quality gate between "a dev fixed it" and "it's safe in front of customers." What you'll do Own the full testing cycle. Build it, run it, and keep it current — so every release is production-ready, not "probably fine." Build thorough test plans — both manual checklists and automated tests — and keep them up to date as the app evolves. Run end-user simulation testing. Testing isn't limited to build verification. You test the app the way a real user in a real environment uses it — representative Windows setups, real printers, drivers and print queues, the actual workflows end users run — and confirm the real-world result. Grow the automated suite. Turn real-world bugs into permanent regression tests (capture the input, lock in the correct output, wire it in) so a fixed bug can never silently come back. Triage incoming issues. Turn messy helpdesk reports into clear, well-defined tickets for the dev team. Watch the rollout. We release to a small group of customers first and monitor logs/telemetry before going wider — you keep an eye on it and flag anything off. You're a strong fit if you Take real ownership and are reliable. When you own the gate, nothing slips through because someone got sloppy or went quiet. This is the single most important trait. Have solid technical capability with Windows operating systems — comfortable across versions, configs and the guts of how Windows behaves. Have experience with Windows printing — drivers, printer queues, print processors, and how print actually behaves in the real world. Have built thorough test plans before — both manual checklists and automated testing — and know the difference between testing that looks complete and testing that is. Can script enough to build, run and extend automated tests — Python / pytest or similar. You don't need to architect the core framework (our developers build that), but you must be comfortable working in it and reading log output. Are meticulous and communicate clearly in written English, with a tidy, predictable workflow. Nice to have Background in MSP / managed IT, or Microsoft 365. Experience with CI pipelines, log tooling (OpenSearch / ELK), or release management. The engagement Ongoing and long-term — we keep good people for years, not one-off jobs. ~10 hrs/week baseline, flexing higher in a release week. We release roughly every 3 weeks. Heads-up — the first ~2 months run hotter (~15–20 hrs/week) while we clear a testing backlog and get the suite established. It settles into the ongoing rhythm after that. Rate Tell us your rate. We care far more about finding the right person than the cheapest one — strong, reliable, detail-driven people are worth it, and we'll happily pay for that. To apply, send us: Start your reply with the word "spooler" — so we know you actually read this. A testing cycle or release process you've owned, and one specific bug you caught before it shipped. Your experience with Windows printing / drivers / queues — a real example. Your experience with automated testing — what framework, and what it covered. Your hourly rate and weekly availability.