Technical Analyst
Typical Day in Role:
• First defense line for L2 production support ticketed issues raised as related to using the CreditLens app
• This resource will be on production support and maintenance, working directly with users and developer to help users with problems encountered (e.g. unblocking a user from creating a rating)
• Investigate, create a Jira ticket, and work alongside developer to support the user to solve the issue
• Gather requirements, and resolve issues in a development and production support environment by outlining requirements via Jira
• Updating Confluence pages
• Supporting the Project Lead with day to day activities: pulling statistics/data from JIRA, creating graphs, refreshing e-mail user lists
• Supporting with release activities i.e. closing release, validating release items
• Coordinate testing and validation with business users.
Candidate Requirements/Must Have Skills:
1) 3+ years as a Technical or Business Systems Analyst (including co-op and/or internships)
2) 1+ year experience (low to medium skillset) using Postgres Database and/or any relational database (i.e. SQL, PL/SQL)
3) 1+ year of data analysis experience
4) Recent working experience with Jira and Confluence
Nice-To-Have Skills:
1) Experience with Visio or other visual software diagramming tools
2) Agile/Scrum methodology understanding / worked in an Agile environment
3) Experience with CreditLens application
4) Experience with MS Office Suite (Excel– pivot tables for data organization, PowerPoint)
Soft Skills Required:
• Teamwork
• Communication
• Organization
• Enthusiastic/Passionate Attitude
• Creativity and thinking out of the box
Education:
Degree in a technical/related field
Best VS. Average Candidate:
Being able to understand and interpret the data, analyzing it and creating graphics to interpret;
Main purpose of role is around helping users of the application; what will set a candidate apart is understanding a user’s challenges, remain calm, digest information, and either work with the user to resolve it and take initiative to resolve, if not – be able to break it down for a developer to solve the problem; has a positive attitude that will make the user comfortable and cared for – ensuring constant follow-ups, providing workaround suggestions and being great with customer support; ability to support different roles in the team.