Business Analyst - CRM (PowerApps / Dataverse)

About the project

Anttix is a software development company focused on technology solutions for CFD brokers and financial services. We’re building our own CRM platform using Power Apps (model-driven) and Dataverse as the core data layer, integrating it tightly with trading, KYC, payments, and marketing systems.

We work in small, senior teams that ship fast, don’t tolerate unnecessary bureaucracy, and care about building systems that actually get used in production.

The platform is delivered by a remote engineering team that owns the full stack behind the broker: the CRM, the trading integration, the payment orchestration, the mobile and web clients, and the back-office tooling used by Compliance, Sales, and Customer Service. The CRM is the system of record for everything customer-related — identity, KYC state, deposits and withdrawals, bonuses, MT5 account assignment — and is where most new business logic lands first. Tech-wise it is a PowerApps / Dataverse solution backed by Power Automate flows and a set of Java microservices; we'll go into the details in the interview.

We’re looking for a experienced business analyst who can translate business requirements into development tasks.

You will work directly with the CTO, Project Manager, two backend developers, a PowerApps/Dataverse developer, a frontend developer, two QA engineers, and DevOps, plus regular contact with Backoffice, Compliance, Payments, and Sales stakeholders on the business side.

Role summary

We are looking for a Business Analyst to own the requirements, data, and acceptance layer of the VCG CRM platform. You will translate regulatory, commercial, and operational needs into Dataverse entity models, Power Automate flow specifications, gRPC API contracts, and UAT scenarios — then verify that what we deliver matches what the business asked for.

This is a hands-on BA role on a real, complex financial product. You will read Power Automate flow JSON, query Dataverse, sit in MT5 trading sessions, and write acceptance criteria that actually catch bugs. You will not be producing slide decks.

What you'll do

Requirements & discovery

• Capture and document behaviour across the CRM (user lifecycle, deposit/withdrawal routing, KYC transitions, bonus logic, MT5 group assignment) from production flows, Confluence docs, and direct observation of the live system.
• Interview Backoffice, Compliance, Payments, and Sales stakeholders; convert their needs into documented requirements tied to specific Jira epics.
• Decompose epics into user stories with clear acceptance criteria that developers can implement without follow-up questions.

Data & process modelling

• Own the logical data model for custom Dataverse entities: contacts, trading accounts, transactions, bonuses, consents, state-machine audit.
• Document field semantics, alternate keys, and cross-system mismatches (e.g., "Id" vs "Guid", timezone offsets between MT5 UTC+2 and Dataverse UTC) that trip up integrations.
• Model business processes (user state machine Demo → Limited → KYC → Full, deposit routing per provider, MT5 group assignment per country/affiliate, account closure reasons) as flowcharts and state diagrams — Mermaid preferred, Lucidchart acceptable.

Flow & rules specification

• Specify Power Automate flows and Dataverse business rules: triggers, conditions, branches, error paths, compensating actions.
• Review existing flows in production, decide which need rework as requirements change, and shepherd the changes through delivery.
• Define event contracts published to Azure Service Bus (event name, payload schema, ordering guarantees, idempotency keys).

Test & acceptance

• Run data validation when onboarding new data sources or migrating between environments, using SQL / Fetch XML / Snowflake queries you author yourself.
• Own UAT sign-off: coordinate with QA, Backoffice, and Compliance; track defects in Jira; make the call on go/no-go criteria for each release.

Documentation & communication

• Maintain project documentation in Confluence, mirrored to the git repo.
• Keep the Jira backlog current: groom it, link specs to tickets, attach acceptance criteria to every story before it enters a sprint.
• Write clear, terse documentation. No filler. Diagrams where they help, tables where they help, prose only when nothing else does.

Required experience

• 3+ years as a Business Analyst on software products, at least one of them on a data-heavy or regulated domain (fintech, trading, payments, iGaming, insurance, healthcare).
• Translating business requirements into technical specifications is the core of this role. You can sit with a Compliance officer, a Payments lead, or a Sales manager, understand what they actually need (vs. what they first ask for), and turn it into something a developer can build without coming back for clarification.
• Strong process and data thinking: you naturally reach for state diagrams, flowcharts, and entity relationships when describing a problem, and you can spot inconsistencies in a process before code is written.
• Comfortable working with structured data and basic SQL — enough to validate that the system does what the spec says, without waiting for an engineer.
• General technical literacy: you can read an API contract, follow a workflow definition, and discuss trade-offs with engineers — you don't need to write the code, but you understand the shape of what's being built.
• Practical grasp of state machines, workflow logic, and master data concepts.
• Written English strong enough to produce specifications that developers implement without coming back for clarification.
• You do not need to be a developer. The team includes a dedicated PowerApps/Dataverse developer, backend and frontend engineers, QA, and DevOps — the BA's job is to make sure they're building the right thing, not to build it.

Nice to have

• Experience with retail CFD / FX / trading platforms; familiarity with MetaTrader 5 concepts (groups, deals, positions, margin, leverage, demo vs live accounts).
• Experience with payment orchestration (Praxis, TotalProcessing, regional LatAm/MEA PSPs, card vs APM routing).
• Experience with KYC/AML vendors (SumSub, Onfido, Veriff) and the associated compliance workflows.
• Experience with messaging / campaign tools (Braze, SendGrid, Mixpanel) for transactional notifications and lifecycle campaigns.
• Experience operating a live production financial system — releases, incidents, hotfixes with real customer funds at stake.
• Exposure to AI-assisted development (Claude, Copilot, Cursor) — this project uses AI aggressively for code generation, test generation, and data validation. You will use the same tools to accelerate specification and analysis.

How we work

• Remote-first, distributed team across Europe. Core overlap hours roughly 10:00–18:00 EET.
• Tooling: Jira, Confluence, Git (GitHub + Bitbucket), PowerApps, Dataverse, AWS, Azure, Snowflake, Grafana, CloudWatch.
• Documentation in git: specs and plans are markdown files committed alongside the code, reviewed via pull requests like anything else.
• English is the working language for written artefacts; spoken language is flexible within the team but all specs, tickets, and review comments are in English.
• Ownership: you own your deliverables end-to-end — from stakeholder interview through UAT sign-off. We do not hand work off between "requirements" and "analysis" and "testing" — those are the same job.

Engagement

• Full-time contract, long-term. The CRM is the backbone of the business and the BA role is a permanent seat on the team — new features, new payment providers, new regulatory requirements, new markets are continuously in flight.