We are looking for an experienced Business Analyst for a contract-based cooperation.
⏰Regarding engagement: part-time (minimum 4–5 hours per day) or full-time.
What is this project about?
This is a cutting-edge FinTech project from the US. Its main goal is to manage and schedule debts for US customers using a popular payment system.
The digital collection strategy allows clients to pay at their own pace on a customizable plan that works for them.
The customers have a proprietary online portal to manage their accounts. The platform offers them multiple instalment payment options, nearly instant account updates, and even potential discounts for many accounts.
The mission is to deliver a better consumer experience in the debt repayment process.
About 100,000 clients used the company’s services and successfully resolved their debts.
What does the interview process look like? — Recruitment interview — up to 30 minutes;
— Technical Interview — up to 1 hour;
Requirements: * 3,5+ years of experience as a Business Analyst * Experience in analyzing system behavior, workflows, and business processes Ability to identify business rules, dependencies, constraints, and undocumented requirements * Experience creating structured documentation (BRD, Functional & Non-Functional Requirements, Use Cases, Scenarios) * Experience building Support Knowledge Base, Runbooks, and troubleshooting documentation * Ability to define acceptance criteria, edge cases, risks, and gaps * Experience modeling business processes, user flows, state diagrams, and integration/data flows * Hands-on experience with Confluence, Jira, and diagramming tools (Miro, Lucidchart, Whimsical, or similar) * Strong communication skills and ability to collaborate with technical teams * Ability to work with incomplete or conflicting information * At least Upper-Intermediate level of English
Responsibilities: * Analyze the existing system behavior and workflows * Identify actual business rules, constraints, and dependencies * Design a single, coherent documentation structure usable by both delivery and support teams * Building the initial structure of the Support Knowledge Base * Create Support Runbooks * Conduct Validation workshops with the customer * Incident Management Guide (together with other team members) * Define acceptance criteria, edge cases, and constraints * Identify common user and system issues * Identify gaps, contradictions, and risks in existing behavior and requirements
