Business Analyst / Associate Product Manager

Що робити

Product work
Own Features End to End: Take a business need - merchants can't withdraw their own balance, fees are opaque, a region needs a new provider - and drive it to release. Define the outcome, the scope, and what's explicitly out of scope for the first phase.
Scope to a Minimal Complete Scenario: Identify the smallest business flow that works end to end and delivers value - including its provider dependencies, finance dependencies, and the operational procedures that have to exist for it to run in production.
Close Questions, Escalate Risks: Propose a reasoned option rather than a list of alternatives. Document assumptions and trade-offs, resolve questions within agreed authority, and escalate material risks early rather than late.
Prioritise: Argue why this feature before that one, using actual data - transaction volumes, failure rates, support load, provider costs.

3+ years as a BA, Product Analyst or Product Owner in fintech, billing, e-commerce or another domain where money is counted and reconciled.
Ownership Mindset: You bring a recommended option with reasoning, flag what you assumed and what you traded away, and know which decisions are yours and which belong to someone else.
Requirements Writing: Specs with clear scope, acceptance criteria and explicit non-goals - not a list of wishes. User stories, use cases, process modelling.
API Literacy: Comfortable with OpenAPI specs, JSON payloads, REST semantics, webhooks and asynchronous callbacks. You don't write code, but you can reason about idempotency and state transitions.
Data Skills: SQL at a level that lets you check how a rule behaves on real data before writing it into a spec, and read your own metrics after release.