IT Requirements Engineer

3/2021 – 9/2025

1. Requirements’ elicitation and documentation:
o Through workshops (remote and onsite) with the customer (internal and external).
o Requirements extraction from bidding documents / customer’s document.
o Importing requirements into Jira.
2. High-level requirements analysis:
o Classifying requirements according to execution mode (out-of-the-box or customization) based on review of the system’s documentations and actual test scenarios on the system.
o Compiling a list of questions for unclear requirements.
o Conducting workshops to clarify open questions.
o Documentation of workshop outcomes.
3. Detailed requirements analysis:
o Identification of use cases and user stories.
o Internal discussion with the different teams (PM, DEV, QA, PO, System Engineering, Product Management, Sales… etc.) to align on the best approaches to fulfill the requirements.
o Conducting buy-build analysis to decide whether to use white-label solutions or build new modules.
o Creation of use cases and user stories tickets in Jira using UML diagrams where needed to ensure clarity.
o Review of use cases internally and with the customer and making any necessary adjustments till all stakeholders reach a common understanding.
o Creation of a detailed solution design document for the customer.
4. Community of Practice participation:
o Hold regular meetings with fellow requirements engineers to document and streamline the requirements engineering process within the company and to address any team, cross-team, or cross-departmental friction points to ensure a streamlined workflow.
o Experience sharing within the team after a project completion.
5. Vendor management:
o Handle the outsourcing of development work packages to external vendors.
o Adaptation of requirements for outsourcing including removing any customer-specific or confidential details.
o Design of Proof of concepts that would serve as criteria for vendor selection.
6. Bidding support:
o Assistance to sales team during bidding on new projects.
7. Creation of KPIs:
o Creation of Jira dashboards, traceability matrices and coverage pages to keep track of the project execution and to avoid any gaps.
8. Quality management:
o Holding meetings with the QA team to ensure that created use cases are clear to them.
o Review of the test cases created by the QA team to ensure sufficient coverage of the different scenarios.
o Participation in sprint reviews to ensure stories implementation satisfies all acceptance criteria.

Apache Kafka, Confluence, Internet of Things (IoT), Jira, Requirement Analyse, UML, Web Services