IT Analyst
Job Description
For our client we are looking for an IT Analyst to their CRMAS Change Team
The client has started to process deep-dives in Group compliance core processes with an ambition to identify improvement potentials from different perspectives (people, process, data&technology). They are currently finalizing it for the first process however they will go forward wit with other processes in the list. This analysis entails creation of process as-is status with an extended SIPOC study (supplier, input, process, output, customer) for each process substeps. Ambition is to design the future state of the processes also from data and technology perspective (considering the applications and tools used during the process, how to automate manual steps etc.)
Top Skills
Have strong business and technical background and great data analytical skills
Have good requirement specification skills including NFRs
Have ability to work both independently and as a part of a team
Are familiar with agile way of working and methods
Are proactive, structured, detail-oriented and quality driven
Your experience and background
Have good requirement (functional and non-functional) management skills including defining acceptance criteria (preferably using Gherkin syntax), Definition of Done, Definition of Ready, others.
Have business and technical background and great analytical skills
Experience of agile way of working and methods (SAFe, Scrum, XP, Kanban, etc.)
Being familiar with most popular requirement management standards (IIBA, IREB, etc,)
Experience of using Jira and Confluence,
Merital
Practical knowledge of SQL and creating SQL queries (nice to have),
Practical knowledge of Process Modelling and UML (nice to have)
Practical knowledge of BPMN (nice to have)
Communication skills, professional level of English
Experience with DevOps mindset will be an advantage
Currently, the client also have an enterprise architect working on HLD in the same topic. With the IT analyst, they would like to convert the HLD into low level technical details. Therefore, its good to have more of a technical profile and less of scrum master type of profile.