Systems Analyst (Requirements)

EducationBachelor's degree in progress in Information Technology, or completion of any bachelor's degree accompanied by a postgraduate certificate (specialization, master's, or doctorate) in Information Technology with a minimum of 360 hours.

Mandatory Experience for the Role

• Minimum of 3 years of experience as a requirements analyst or in similar roles in software development projects;

• Proven experience in agile environments and interacting with cross-functional teams;

• Skills in process and requirements modeling, using techniques such as UML or BPMN;

• Experience with documentation and prototyping tools (e.g., Figma, Balsamiq Mockup).

Mandatory Technical Knowledge

• Experience with project management tools, especially Azure DevOps.

• Knowledge of agile methodologies, especially Scrum;

• Skills in process and requirements modeling, using techniques such as UML or BPMN;

• Familiarity with documentation and prototyping tools (e.g., Figma, Balsamiq Mockup).

Desirable/Differential Knowledge

• Knowledge of software testing and requirements validation techniques;

• Knowledge of Function Point Analysis for measuring system requirements and functionalities.

Behavioral Skills/Soft Skills

• Enthusiasm for learning;

• Negotiation and communication;

• Interpersonal relationship skills;

• Analysis, abstraction, and extrapolation;

• Planning and activity management;

• Initiative and creativity.

Duties and Responsibilities to be Performed

• Gather, analyze, and document the project scope, including the Domain Model design and other information that enables clear understanding and definition of the product backlog to be developed;

• Conduct information gathering through meetings with end clients and other stakeholders, analyzing them to understand needs and enable the creation of documents used in building systems and applications;

• Document requirements for system and application development in a way that is easily interpretable by both developers and clients;

• Prototype system screens to help clarify what needs to be developed;

• Create Flow, State, Activity, and other diagrams as needed to complement requirements documentation and facilitate understanding of demands;

• Map and design business processes to complement requirements documentation, aiming to increase overall clarity and facilitate understanding of what must be developed and delivered;

• Conduct requirements handovers to the development team and be available to address team questions throughout the entire requirements lifecycle;

• Monitor items developed by the team to ensure value deliveries are made in each cycle for our clients;

• Manage change requests and improvements, keeping requirements always up to date;

• Provide support when necessary, identifying client needs, proposing process and function changes, negotiating alternative solutions, and proposing adoption of new methods and techniques, aiming to adapt solutions to client needs.