Business Analyst

RemoteMiddle

We are a team developing a Core platform for processing SMS messages under high load. It’s the heart of the entire system: routing, integration with providers, billing, and message delivery logic. We are currently undergoing an architectural transformation: rethinking business processes and updating key system components. We expect the business analyst to take an active role in researching and formalizing processes—through stakeholder interviews, analysis of user scenarios, and observation of operational activities. The analyst works closely with the product manager, designer and systems analyst to ensure the completeness of requirements and the integrity of business logic.

Responsibilities

Gather, analyze, and formalize business requirements through communication with stakeholders and analysis of user scenarios
Analyze and visualize business processes, identify bottlenecks, and propose improvements
Decompose features into tasks, maintain up-to-date requirements, and clarify details
Create and maintain documentation in Confluence: describe business logic, parameters, and user scenarios
Participate in UI discussions with the designer, formulate tasks, and validate proposed solutions
Formulate tasks for frontend developers considering UX, business requirements, and architectural constraints
Collaborate with the product manager, systems analyst, architect, frontend/backend developers, and QA engineers
Be part of an Agile team: understand sprint and release processes, participate in planning and prioritization, and support the team at every stage

Requirements

At least 2 years of experience as a business analyst in a product or technical team
Ability to formalize requirements, break down features into tasks, and see not just the mechanics, but the meaning behind them
Experience modeling business processes—knowledge of BPMN, UML notations
Understanding of how web applications work: where business logic resides, how frontend and backend interact, and how this affects requirements
Basic knowledge of REST APIs—designing is not required, but confident participation in interface discussions is important
Flexibility in approaches and communication—the ability to adapt to changes, negotiate, and find workable compromises
English proficiency at B1 level or higher—for reading and discussing project documentation
Experience with tools such as Jira, Confluence, Figma, Swagger, Lucidchart/Camunda, or similar

Nice to Have

Experience in telecommunications (SMS, SMPP, routing, billing)
Understanding of database structure and basic integration principles
Solid understanding of UX approaches: involvement in interface design, close collaboration with designers