Position: Senior QA Engineer, CRM Team
Company: VCG Tech Limited
Location: Remote
Employment Type: Full-Time
ABOUT THE PROJECT
Anttix (VCG Tech Limited) is a software development company building technology solutions for CFD brokers and financial services businesses. We're developing our own CRM platform on Microsoft Power Apps (model-driven), with Dataverse as the core data layer and deep integrations across trading, KYC, payments, and marketing systems.
We work in small, senior engineering teams that move fast, keep bureaucracy to a minimum, and focus on building reliable systems that deliver real value in production.
The CRM serves as the central system of record for the entire customer lifecycle: onboarding and KYC verification, MetaTrader 5 trading account provisioning, deposits and withdrawals across multiple payment providers, sales ownership and client tiering, bonus and promotion management, and marketing communications. Each of these domains comes with its own business rules, state transitions, and regulatory requirements, and the platform must enforce them consistently across the customer journey.
Nothing operates in isolation. A single customer action can pass through gRPC gateway APIs, Power Automate flows, Azure Service Bus events, and multiple third-party integrations before it becomes a record that someone in Backoffice needs to act on.
Our remote engineering team owns this ecosystem end to end, with the CRM team continuously delivering new functionality into a complex, highly integrated production environment.
ROLE PURPOSE
We need a QA Engineer who can verify a CRM feature quickly without letting anything through, and who treats a feature as unfinished until it behaves correctly on production. You work closely with the Business Analyst and the developers: taking a completed feature apart against its specification, verifying behaviour across Dataverse, flows and the downstream systems, and deciding whether a release build is ready.
The subject matter is money and customer state, so correctness is not negotiable - but speed is part of the job description, not a trade against it.
The first priority is high-quality end-to-end manual verification with no gaps, matching what the requirements actually say. CRM functionality then has to be covered by automation as well: the regression suite is written in k6 and grows with every feature you verify. Manual verification comes first and automation follows it, never the other way around.
KEY RESPONSIBILITIES
Feature Verification & Exploratory Testing
- Verify new CRM features end to end - the Dataverse data model, the Power Automate flows behind it, the gRPC API responses, and the effect on MetaTrader 5, payments and marketing systems.
- Turn acceptance criteria into a complete, risk-ordered set of checks, and go deep where money, customer state or compliance is involved.
- Leave no gaps: every state, every branch and every field the feature touches gets verified, and the outcome has to match the original requirement rather than a plausible-looking screen.
- Run structured exploratory testing around every feature to find the edge cases and failure paths nobody wrote down.
- Keep the loop short: findings the same day, reproducible on the first read, no week-long test cycles.
Requirements, Grooming & Collaboration
- Work with requirements efficiently: read a specification, pull out the states and rules it implies, and take ambiguity, missing states and conflicting rules back to the Business Analyst.
- Verify a completed feature against its original requirements, point by point - most verification here happens once development is done, so the specification is your reference.
- Take part in grooming and estimation sessions, and raise testability problems and risky areas while the work is still being shaped.
- Pair with developers on the hard parts - option-set values, flow ordering, retries, idempotency - rather than only reporting the outcome afterwards.
- Improve the feature, not just its defect list: proposals that make the delivered behaviour better are part of what we expect from this role.
- Give the team an honest quality picture at any moment: what is verified, what is risky, what is a known issue we accepted.
Release Verification & Sign-Off
- Own pre-production verification of release builds: regression scope, a smoke pass over the critical customer journeys, and the sign-off decision.
- Run post-production verification after every release and confirm the live behaviour of what actually shipped.
- Watch the first hours of a release for regressions in onboarding, deposits, withdrawals and trading-account provisioning, and escalate with evidence instead of suspicion.
- Keep a repeatable release checklist and sharpen it after each release.
Test Automation & Regression Coverage
- Automate after the manual pass, never instead of it: a feature is verified by hand against its requirements first, then locked in by a test.
- Write and maintain k6 tests against the gRPC gateway APIs, the Dataverse Web API and Power Automate flow endpoints.
- Extend the regression suite as you verify, so that today's manual check becomes tomorrow's automated one.
- Keep the suite trustworthy: self-provisioning test data, one meaningful assertion per property, and no flaky checks the team learns to ignore.
- Run suites against QA and pre-production, triage the failures, and separate a real regression from environment noise.
- Use AI-assisted tooling to write and refactor tests faster - it is standard practice on this team.
Data Validation & Defect Management
- Validate outcomes directly in Dataverse, property by property, using the Web API or FetchXML rather than trusting a screen.
- Verify asynchronous, event-driven behaviour: flow runs, Service Bus events, webhooks, retries, ordering and idempotency.
- Trace one customer action across services, and use logs and observability tooling to reach root cause before filing.
- File defects in Jira with reproduction steps, real test data and evidence, then drive them to a fix and verify it.
- Report results in TestRail and keep test documentation current in Confluence and git.
REQUIRED EXPERIENCE & SKILLS
- 5+ years in QA or test engineering on backend-heavy or data-heavy web products.
- Strong functional and exploratory testing skills, and the discipline to cover a feature completely instead of sampling it.
- The ability to work with requirements efficiently: you can read a specification, pull the testable rules and states out of it, and see what is missing or contradictory in it.
- API testing experience with REST and ideally gRPC, and comfort reading an API contract.
- Hands-on automation in k6, or a comparable code-first framework you can carry over to k6 quickly (JavaScript).
- Confidence querying and validating structured data - SQL, or a data API such as the Dataverse Web API or OData.
- A working understanding of asynchronous and event-driven systems and the failure modes they bring: partial state, retries, duplicate events, out-of-order delivery.
- Experience verifying release builds and owning a go/no-go call.
- Jira, Confluence and a test-management tool such as TestRail.
- Enough written English to work directly with a BA and developers, without a manager relaying messages.
- Results-oriented and team-oriented: you finish what you start, you say plainly when something is not ready, and you help the team ship instead of guarding a gate.
NICE TO HAVE
- CFD, FX, brokerage or payments domain experience.
- MetaTrader 5 familiarity.
- Power Platform experience - model-driven Power Apps, Dataverse, Power Automate.
- KYC and AML vendor integrations such as Sumsub.
- Payment orchestration and PSP integrations.
- Marketing and CRM communication platforms such as Braze.
- CI/CD pipelines running automated suites (Bitbucket Pipelines, GitHub Actions).
- AWS, Azure or Snowflake exposure.
- Performance testing with k6.
- UI automation with Playwright or Selenium - welcome, though not what this role is measured on.
HOW WE WORK
- The CRM team is four developers, one Business Analyst and two QA engineers - you would be the second QA.
- A friendly team, engaged management, and an experienced BA who writes specifications you can genuinely test against.
- Remote-first, distributed across Europe, with core overlap 10:00-18:00 EET.
- Tools: Jira, Confluence, TestRail, git, k6, Power Apps, Dataverse, AWS, Azure, Snowflake.
- Tests and test documentation live in git, as code and as markdown, reviewed by pull request.
- English for written artefacts, flexible spoken language.
- Direct access to the BA, the developers and the stakeholders - no layers between you and the decision.
- AI-assisted development tooling is expected and supported, not merely tolerated.
LANGUAGE REQUIREMENTS
Ukrainian: Native speaker level
English: B2 (Upper-Intermediate) or higher