Technical Information Architect

Job description

The primary function of the role is to work as part of the Corporate Investment Bank (CIB) Information Architecture team providing development support in order to deliver and maintain components and tools that deliver to the wider function of Information Architecture and Data Management.
Information Architecture and Data Management continues to be a critical element to delivering on our business objectives and it’s something that is required in order to support the reduction of costs, lowering risk, increasing performance and enabling the transparency of business performance and client satisfaction. There are a number of associated objectives required of our Information Architecture and Data Management function.
·  Create and maintain accurate, complete and consistent governed Metamodels and Data Models with lineage and implementation traceability metadata
·  Collaboration to create, maintain, govern and use Controlled Vocabularies, Data Sourcing and Authority (System Of Record and Authoritative Data Source) with our Business Partners and the Chief Data Office
·  Actively engage with development teams to use Information Architecture as part of the development process and the associated deliverables
·  Incrementally standardize and simplify the Data and Information Architecture through the rationalization and reduction of interfaces and databases
·  Deliver to firm-wide, CIB and sub-LOBs Data Policy and Standards (such as the System of Record and Authoritative Data Sourcing registration and CIB Business Data Taxonomy, Data Modelling and Representation)
·  Contribute towards the incremental delivery of the Data Strategy (for example building out of the Shared Data Platform and common data components)
·  Work with other teams across JPMC to order to coordinate on data quality, data usage and delivery (Reference Data, Data Science, Finance, Risk and Regulatory)
The Technical Information Architect (IA), will work as part of the CIB Information Architecture and Information Engineering federated team to achieve a number of strategic objectives to negotiate, agree and deliver artefacts such as the Business Entity Model, State Model, Controlled Vocabulary and Communication Contracts and govern their implementation and traceability from Logical and Physical schemas as part of a Model Engineering processes.

The Information Architect will be considered the Subject Matter Expert on Data and Information Architecture and Management working closely and collaboratively with business subject matter experts and project development teams, ensuring that the design is implementable and that delivery is consistent with the agreed design.

The Information Architect will also work with the JPMC firm-wide, Chief Data Office (CDO), CIB and LOB core architecture teams on standards, tooling and production of standard on-going Information Architecture deliverables such as Data Lineage, Lifecycle Management, Quality Monitoring and Metadata Management.

Engaging with Business Operations, Product Management and Technology groups across the firm, the IA ensures that business requirements are translated into fit-for-purpose data requirements and that accurate traceability and lineage is both defined and documented. The IA will work with Business, Application and Technology Architects to review (and where necessary contribute to) business drivers, needs and strategies whilst assessing the implications and impact to the Data and Information Architecture.  The IA will be considered a key trusted advisor on options, risks, and cost versus benefits and will communicate business data prioritization decisions to the relevant technology organizations.

The Information Architect will be able to engage confidently across all organizational levels management, evangelizing the benefits and importance of Information Architecture and Data Management. They will also be able to interchange between operating independently and in conjunction with other team members as required, whilst working on a number of assignments simultaneously.

Experience & Knowledge

Essential

·  Strong experience of several major technology implementation projects, ideally with a strong data orientation
·  Knowledge of various Data Architecture patterns including ODS, Data Lake, Data Warehousing, OLTP, Data Vault and OLAP.
·  Strong working knowledge and experience of Data Modelling and Meta-modelling (preferably with UML) and the principles and working practices of Model Driven Development (MDA).
·  Experience with the development of meta-languages and knowledge of existing metadata management standards such as OMG MOF, ISO 11170 and Eclipse JCORE.
·  Software Engineering experience across the SDLC and some practical experience of programming languages such as Java, Python and Scala and Data Communication Formats such as XML, JSON, Google Protocol Buffers, Avro and RDF.
·  Experience of identifying and architecting alternative data integration patterns to support the requirements.
·  Knowledge and experience of the Software Engineering Methodologies
·  Knowledge of core Information Architecture capabilities, including Master and Reference Data Management, Data Quality (DQ), Metadata Management, Data Classification, Taxonomy, Data Integration, Data Migration and Data Modelling
·  Experience in creating, contributing to and reviewing Architecture and Development artefacts such as Technical Specifications,
·  Ability to collaborate with business teams in order to understand, translate, review and playback requirements into Logical Data Models, Interface Specifications, Taxonomies and Controlled Vocabularies
·  Understand development methodologies particularly in a lean/agile environment.

Desirable

·  Knowledge of Financial Services particularly Investment Banking and Corporate Banking.
·  TOGAF and/or DAMA certification
·  Versioning Control Systems and Version and Change Management particularly in the context of Model and Taxonomy Management.
·  Familiar or close partnering with Business Data Management and Chief Data Office functions for the specification and management of Controlled Vocabularies, Business Information Models, Coarse-grain Lineage and Provenance and Authority of Data Sourcing.
·  Construction of grammars, parsers and lexers for the expression of meta-languages and the construction and execution of implementation agnostic of rules

Key Duties

·  Specification and detail-design of meta-based languages for defining Data and Information Architecture Standards and Artefacts of a metadata framework.
·  Championing design traceability and provenance framework (allowing audit-trail based data quality control) within the metadata framework.
·  Ensuring all cross-management areas, regulatory data standards and data requirements are addressed within the metadata framework.
·  Collaborating with firm-wide IA and Architecture group to develop consistent, accurate, documented and complete IA artefact for the CIB
·  Working with the Chief Data Office for the architectural technical representation, sourcing and evidence of application of Data Management standards across the CIB
·  Developing and maintaining logical, platform independent Component models and working closely with the Information Engineering development team to create CIB Information Architecture componentry.
·  Working with business-aligned IA and LDAs to technically design metadata solutions within or extensions of the metadata framework.

Deliverables of the Technical Information Architect :
·  Specification and design artefacts for the satisfaction of Information Architecture and Data Management requirements for the development of processes and tools across the CIB to
·  Communication specification languages and transformations to meet business requirements.
·  Define the process for the development and communication of Controlled Vocabularies and usage of the Group Banking Technology/Chief Data Office Enterprise Controlled Vocabulary
·  Coordinate development and traceability between Logical Data Model, Communication and Physical Data Models and their implementations.
·  Roadmap for development of key technical metadata architecture components
·  Metadata Lifecycle Management Solution Approach for the use of Technical Metadata Components.

General Skills

Domain Knowledge

An understanding of (in no particular order):
·  Forward engineering approaches to Information Architecture and Data Management
·  Development of decoupled Software Architectures such as Component-Based Architecture, Service-Oriented Architecture, Model-View-Controller, N-Layer Architecture, Aspect Oriented Development etc. (The more, the better)
·  Meta-Object Frameworks (OMG MOF, Eclipse ECORE)
·  UML and UML Customizations as source models for software and data specifications
·  Schema-less Messaging i.e. Java serialization / deserialization to/from a range of data transfer formats e.g. JSON, XML using @Annotations, XMI
·  Data Driven Applications (where we avoid hard-coding as much as possible and drive configuration and behavior from rules & configuration metadata)
·  Working knowledge of data formats, for example XML Schema, JSON, CSV, Avro, COBOL Copybooks

Technical Skills

·  Agile Architecture and the Software Development Lifecycle (SDLC)
·  Continuous Integration & Testing (CIT) environments
·  Automated Build and Release environments
·  Design for Change approaches i.e. designing non-breaking solutions to continually evolving requirements
·  Database Management Technology Standards, such as SQL, DBMS Partitioning, Index Creation, Physical Data Models, RDF, SPARQL
·  Construction of Domain Specific Languages and mapping into Target Specific Languages

Personal Skills

Intellectual Demands

·  Ability to identify software implementation patterns common across multiple programing languages and technology stacks
·  Abstraction and generalization of solutions into design patterns
·  Ability to envisage and compare potential solutions prior to implementation

Communication

·  Effective communication and facilitation with Business & Technology stakeholders to translate requirements into software  that represent progress towards a target state of best engineering practice, simplification and standardization
·  Ability to unambiguously communicate through multiple channels such as Presentations, Word Documents , Workshops and Agile Development Meetings
·  Collaborate with the business technical teams, exchanging and transferring technical knowledge, developing and evolving standards, guidelines, etc.