Ukraine only · Full-time · Ukrainian DefTech product · GreenM Talent Partner
About the role
We are looking for a Senior Manual QA Engineer with strong, recent hands-on experience testing Windows Desktop / System applications.
This is not a Web/Mobile QA role with occasional Desktop exposure.
The product is a locally running real-time desktop system that works with external data sources, integrations and connected components, including scenarios with unstable or missing connectivity.
The QA practice already exists: smoke coverage, regression suite, release gates, severity/priority rules and a Senior QA Engineer are already in place.
We are hiring the second Senior QA Engineer who will work as an equal peer and gradually become fully interchangeable within the release cycle.
The main hiring priority right now is short time-to-autonomy. For this reason, we are deliberately prioritising candidates whose recent commercial experience is already close to Desktop/System QA, connectivity, integrations, data consistency and troubleshooting.
Further product details are shared during the hiring process and, where required, after NDA.
This role is likely a strong match if
You have been testing a real Desktop/System product hands-on, preferably on Windows, and your work included more than UI validation.
For example, you have dealt with areas such as:
- installation, configuration, updates or migrations;
- local application state and local data;
- Windows-specific behaviour;
- logs and technical troubleshooting;
- connectivity loss, reconnect or synchronization;
- external integrations, devices or data sources;
- version compatibility;
- inconsistent or delayed data;
- regression and release-readiness decisions;
- defects where the root cause could be in the application, OS, network, configuration, integration or an external component.
Experience with maps, GIS, geodata, tracking, telemetry, sensors, communication protocols or hardware-connected systems is especially relevant.
What you will do
You will work together with the current Senior QA Engineer and take full hands-on ownership of QA execution.
Your responsibilities will include:
- independently running Manual/System QA cycles for releases;
- testing Windows Desktop functionality beyond the UI layer;
- validating installation, configuration, local state and environment-specific behaviour;
- testing degraded-connectivity scenarios, recovery and data consistency;
- investigating integration failures and inconsistencies between different data sources;
- reproducing incidents, gathering logs/evidence and narrowing down the likely failure layer;
- maintaining regression coverage for critical product flows;
- creating and updating test cases, checklists and defect reports;
- participating in severity/priority decisions and release go/no-go discussions;
- sharing context and QA ownership with another Senior QA Engineer so either person can safely pick up the other’s scope.
Automation may appear later as a supporting tool, but this is fundamentally a hands-on Manual/System QA position.
Must-have requirements
1. Recent hands-on Desktop / System QA
You have commercial experience testing installed Desktop applications, preferably Windows-based.
We expect you to be able to describe specific recent cases involving the Desktop client itself — not only a Web interface that happened to be part of the same product.
Your Desktop experience should include several of the following:
installation / update / migration / configuration / local state / logs / OS behaviour / resource constraints / connectivity / integrations / external dependencies / recovery after failures.
If your recent commercial experience is almost entirely Web or Mobile, this role is unlikely to be the right match.
2. Strong Manual QA craft
At least 3+ years of hands-on Manual QA as a meaningful part of your day-to-day work.
You should be able to walk us through real cases involving:
- exploratory testing;
- risk-based prioritisation;
- regression;
- defect investigation;
- incomplete requirements;
- release-risk decisions.
A Lead/QA Manager title is not a problem, but we need evidence that you still personally performed substantial hands-on testing.
3. System / integration thinking
You should be comfortable investigating issues beyond:
“The UI shows the wrong value.”
We expect you to be able to work with evidence such as:
logs → API/integration → database/local state → external data source → network/environment
and determine where an inconsistency begins.
4. Connectivity / resilience understanding
Commercial experience with at least some of the following is highly desirable:
network loss · reconnect · retry · synchronization · stale data · partial updates · delayed events · offline state · recovery after interruption.
Direct real-time experience is preferred.
5. Test documentation
You have personally created and maintained:
test cases, checklists, regression coverage and high-quality bug reports.
Documentation here is part of QA engineering, not administrative paperwork.
We will ask how your test assets were kept current as the product changed.
6. Senior ownership
You are comfortable making QA decisions independently:
- identifying risk;
- asking for missing context;
- prioritising coverage;
- escalating early;
- documenting unresolved risk;
- recommending whether a release is ready.
We are looking for predictable ownership, not last-minute heroics.
7. Peer-level collaboration
You will work with another Senior QA Engineer as an equal peer.
We need someone comfortable with:
shared QA scope, peer review, clean handovers, shared test assets and interchangeability.
A “this area belongs only to me” working style will not fit this team.
8. Structured communication
The team is small and high-sync.
We expect concise communication built around:
problem → evidence → risk → action / next step.
A developer should be able to act on your defect report without several rounds of clarification.
9. Location / format
- Physically based in Ukraine.
- Full-time.
- Available for synchronous collaboration during Ukrainian working hours.
- Comfortable with occasional offline team/testing sessions when required.
- Comfortable working under NDA and strict OPSEC discipline.
- English approximately B1+, sufficient for technical documentation.
Particularly strong match
We will prioritise candidates with commercial experience in one or more of these areas:
GIS / maps / geodata / object tracking
Examples: coordinates, layers, object position/history, tracking, map accuracy, offline maps, spatial data.
Connected devices / sensors / telemetry
Examples: external devices, hubs, controllers, sensors, monitoring systems, telemetry streams.
Network / protocol-heavy systems
Examples: TCP/UDP, custom communication protocols, unreliable connections, reconnect/recovery, streaming data.
Integration-heavy Desktop products
Examples: industrial software, monitoring/control systems, security systems, SCADA-like products, medical/diagnostic desktop software, device-management systems, trading terminals, GIS tools or other complex local clients.
Real-time or operationally critical systems
Products where stale, delayed, missing or incorrect data materially affects the user’s decision.
Direct DefTech/MilTech experience is a strong advantage but is not mandatory if the technical environment is genuinely comparable.
Domain advantages
Additional value:
- UAV / drone software;
- Ground Control Systems;
- ArduPilot;
- MAVLink;
- SITL;
- C2 systems;
- radar/sensor integrations;
- telemetry;
- navigation/tracking;
- mission-critical field software.
We do not expect every candidate to know these technologies already.
However, if your background is far from both the domain and Desktop/System QA, the expected ramp-up will likely be too long for the current hiring need.
This role is probably NOT a fit if
Please consider this before applying.
This role is unlikely to match if your recent experience is primarily:
Web QA without substantial Desktop testing;
Mobile-only QA;
Automation QA with limited recent hands-on Manual work;
QA Management / coordination without daily testing;
process ownership without technical troubleshooting;
browser-based maps without meaningful Desktop/System exposure;
pure UI testing without integrations, logs or system-level investigation.
We prefer fewer highly relevant applications over a large general QA pipeline.
Working with AI
Using AI/LLM tools in QA is welcome when done thoughtfully.
Useful examples include:
- generating test ideas;
- analysing anonymised logs;
- structuring documentation;
- drafting test data or scripts.
We will also discuss what you would never send to an external AI service, particularly in a sensitive product environment.
AI is an advantage, not a substitute for strong Manual/System QA fundamentals.
Team and onboarding
You will join a small product engineering team and work directly with the existing Senior QA Engineer.
The expected progression is:
First month: environment, product/system context, smoke, first independent investigations.
Around 60 days: independently running release testing for your scope and maintaining several critical flows.
Around 90 days: able to operate as a full peer within the QA pair, own part of the regression suite and participate confidently in triage and release-readiness decisions.
The objective is not instant day-one interchangeability, but we are specifically looking for someone whose existing experience allows for a relatively short technical ramp-up.
Work format
Ukraine — Kyiv/Lviv are convenient but not mandatory.
Full-time, remote-first, with synchronous Ukrainian working hours.
Preliminary employment model: staff employment with reservation support. Exact contractual, probation and equipment details are discussed transparently during the process.
Occasional offline sessions or testing activities may be required.
Hiring process
1. TA Interview — 45–60 min
We focus heavily on verifying actual hands-on Desktop/System experience, Manual QA depth, ownership, communication and relevant commercial cases.
2. Technical Interview — up to 90 min
With the Engineering Manager.
Expect practical scenarios around:
Desktop/System QA · connectivity/recovery · integrations · logs/troubleshooting · data consistency · release risk · maps/system behaviour where relevant.
This is primarily a discussion of how you think and investigate problems rather than a theoretical QA quiz.
3. CEO / CTO interview — 30–60 min
Ownership, collaboration, mission fit and working style.
No take-home assignment.
Before applying
To help us process applications faster, please make sure your CV/profile makes it clear:
1. Which Desktop products you personally tested.
2. When this experience was and how recent it is.
3. What you personally tested beyond the UI.
4. Whether you worked with connectivity/offline/reconnect/integrations/logs.
5. Whether you have GIS/maps, sensors/devices, telemetry or protocol experience.
If these areas are not visible in the CV, please add 2–4 sentences in your application message.
We value strong engineering fundamentals, responsibility and honest communication. For this hiring cycle, however, we are intentionally prioritising direct relevance and short time-to-autonomy over broader general QA experience.
Відгукнутись на вакансію