At Broadridge, we've built a culture where the highest goal is to empower others to accomplish more. If you’re passionate about developing your career, while helping others along the way, come join the Broadridge team.
Broadridge is looking for a proficient Data Analyst with advanced RDBM and Excel skills to define data ontology and data mapping for integration of multiple mission critical systems that are being used heavily by the capital market clients.
Define and document data model of different systems and mapping of them to a common data model
Work on defining the data ontology needed for the integration of multiple systems
Help developers and architect to verify and validate the system
Performing statistical analysis of data
Using tools and techniques to visualise data in easy-to-understand formats, such as diagrams and graphs
Preparing reports and presenting these to management or clients
Monitoring data quality and removing corrupt data
Communicating with stakeholders to understand data content and business requirements
Proficiency with relational databases
An understanding of data modelling principles, including dimensional modelling, entity relationship tools (ER tools), and semantic modelling.
The ability to work with XML, XSLT2, XQuery, XPath and XSD
The ability to work with JSON, to understand the distinctions between the JSON Data Model (JSDM) and the XML Data model (XDM).
The ability to work with RDF, RDFS, OWL, Sparql 1.1, SPIN or similar extension system, and (increasingly) SHACL.
Be able to write SQL in various variants, to distinguish between DML and DDL, to know the distinguishing characteristics of inner, outer and cross joins, understand the various normal forms, and be able to talk knowledgeably about the advantages of normalized vs. denormalized forms.
Be able to communicate effectively in writing and in person.
Be able to use data visualization tools effectively.
Understand data governance
Love data and concepts.
Good knowledge of MS Office (Excel and Word)
Attention to detail - using a hyphen rather than an underscore, consistent naming - and be precise about terminology.