Technical Business Analyst

• Be curious, proficient at problem-solving, self-starting and take ownership of issues through to timely resolution.
• Approach problems logically and make informed decisions based on data.
• Have experience presenting analysis findings, in writing and orally, to developers and non-technical stakeholders.
• Have strong analytical and problem-solving capabilities; be able to conceptualise solutions and anticipate future directions and trends.
• Learn quickly and understand businesses, processes and systems.
• Work at pace, communicate clearly, operate independently and work well in a team.
• Be able to perform data analysis using Spark, Scala and Hadoop.

Nice to have:

• A number of years of experience working in banking or financial services.
• Knowledge of HDFS, Unix and Quantexa software.
• Understanding of cloud platforms.

• Take responsibility for deliverables as required.
• Produce consistent, accurate, visual and timely documentation validated before sharing and tailored to its audience.
• Work across platforms and collaborate with support teams.
• Work with business and technology teams to understand business needs and translate them into functional and data solutions, leveraging existing platform features and requesting new ones where appropriate.
• Explain to the business how its requirements can be met with the functional solution.
• Work with solution architects to translate the functional solution into a technical solution that meets business needs, including data analysis to establish data quality and coverage.
• Document requirements, including the business problem, benefits, solution and expected results.
• Work with technology test teams, or undertake testing, to ensure the solution meets expectations, communicate the outcome to the requester and obtain sign-off.
• Support business and technology teams during initial deployment and with subsequent questions or issues.
• Maintain communication with business and technology teams throughout each project stage, using Agile practices and standard project management reporting.

• Occasionally adjust start and finish times to align with the locations of business or technology teams.