Senior Business and System Analyst m/f/d

There are projects that end after a year. There are also those that develop for years and have a real impact on thousands of users. With us, you will join the latter category. We work in the area of social insurance – a stable, complex, and analytically challenging field. The project is long-term and there is no indication that it will end. Why is it worth it? You will work on the largest IT project in Central and Eastern Europe, in a business system developed over years – without "project shutdowns in six months," you have a real impact on solutions, not just fulfilling a backlog, you combine business, system, and technical analysis – without artificial division of responsibility, you work closely with developers and clients – without corporate walls between teams, you create solutions that actually work in production, not just look good in documentation, you have room for autonomy, proposing improvements, and making decisions, you work with people who like concrete results, cooperation, and a partnership approach. Location: Wrocław Work format: hybrid Recruitment: remote (interview → 2 meetings → decision) How we work? SCRUM, close cooperation between analysts and developers, real impact on technical solutions, lots of conversation and little "process for process's sake." Technologies and tools we use: CASE tools (Enterprise Architect preferred), UML, BPMN, SQL and relational databases, JSON / XML / XSD, under the hood: C++, Java 17, and Angular, Jira, Confluence. Team You will join one of two teams: A 6-person development-analyst team + Product Owner, A 5-person team with a tester, analysts, and developers + Product Owner. We care not only about competencies but also about matching people to the team's work style. Who are we looking for? Someone who: Can talk to both business and developers, Thinks process-wise and system-wise – sees dependencies, not just individual functionalities, Can ask difficult questions and clarify requirements, Is independent, concrete, and well-organized, Can work on details without losing sight of the whole, Feels responsible for the quality of the solution, not just "their part." What will you be doing? Conducting workshops and meetings with clients, Analyzing business and system requirements, Analyzing the impact of changes on existing functionalities, Designing application solutions, Creating analytical, technical, and executive documentation, Modeling processes and data structures, Creating Use Cases and acceptance criteria, Designing test scenarios and cases, Functional testing of software, Supporting error diagnosis and analyzing reports, Collaborating with programmers to clarify technical solutions, For a Senior – also leading analytical work as a leader. What does the work process look like? Analyzing materials from the client (project agreements) Clarifying requirements – questions, workshops, meetings (e.g., Webex) Agreeing on scope and estimating work Preparing analytical and design documentation Collaborating with programmers, analysts, architects during implementation Functional testing of solutions created by the team (checking solution compliance with requirements) Acceptance testing with the client Unifying and finalizing documentation What will you need to perform your assigned tasks? For an Analyst: minimum 3 years of experience in business-system analysis and client work. For a Senior Analyst: minimum 5 years of experience and independence in conducting analyses and coordinating analytical work. Additionally: Experience in projects related to software development and maintenance, Ability to model UML and BPMN, Practical knowledge of SQL and relational databases, Knowledge of CASE tools (Enterprise Architect preferred), Ability to define requirements, interface contracts, and acceptance criteria, Experience in creating analytical and technical documentation, Knowledge of data exchange standards (JSON, XML, XSD), Ability to collaborate with a development team, Very good communication and analytical skills, Accuracy, meticulousness, and good work organization. Nice to have: Knowledge of software complexity estimation methods (e.g., COSMIC), Experience with non-functional requirements, Basic code reading ability, Analysis of application logs, Optimization of SQL queries, Knowledge of Git, Jira, and Confluence, Knowledge of agile software development methodologies (Scrum). If you are looking for a place where an analyst is not a "secretary for requirements" but a partner in creating solutions – let's talk.