Product Analyst / IT Business Analyst

What do we expect from the candidate:

• Higher professional education (IT, system analysis, applied computer science) and work experience as a system or business analyst in IT (preferably B2B SaaS, Enterprise or Cybersecurity);
• Understanding the lifecycle of accounts, access control principles (RBAC, ABAC), and IDM/IGA class systems;
• Confident knowledge of methods for collecting requirements, writing User Stories, Use Cases, and Acceptance Criteria;
• Knowledge of BPMN 2.0 and UML notations, ability to draw understandable process diagrams;
• Understanding High-Level Architecture, Data Flows, client-server architecture, REST API basics (JSON/XML, Swagger) and basic SQL queries;
• Understanding Agile/Scrum/Kanban, ability to decompose tasks and work in Jira, Confluence, Miro;
• Knowledge of the UAT (Acceptance Testing) methodology;
• Understanding the basics of information security and personal data protection requirements.

What you have to do:

1. Requirements management and logic design

• Collect, analyze in detail, coordinate and update requirements from PO and key users;
• Translate business goals into User Stories, Use Cases, functional and non-functional requirements that are understandable to the development team.;
• Describe end-to-end business processes (AS-IS/TO-BE), role models of access, and the logic of the system modules.;
• Create clear Acceptance Criteria and interface layouts/prototypes;
• Evaluate how new changes will affect the existing functionality of the product.

2. Development coordination (PM functions)

• Participate in all regular meetings: sprint and release planning, backlog grooming, and demos;
• Decompose requirements, help evaluate tasks, and add them to the task tracker.;
• Highlight and record risks, limitations, and dependencies on tasks in advance.

3. Team support

• Stay in touch with development and QA: answer questions, provide explanations on the logic of the product;
• Communicate agreed requirements to Technical leaders for database and API design;
• Help the QA department with the context of the requirements to prepare their test cases.

4. Acceptance and documentation

• Conduct final acceptance testing (UAT) and, together with the PO, decide whether the feature is ready for release;
• To keep the Confluence knowledge base and documentation up to date.

Why should you come to us?

• A complex and interesting product: No standard landing pages, just deep product logic at the interface of information security and business processes.;
• Transparent separation of roles: You don't have to write code for developers or create databases – there are strong Technical leads for this.