Context:
We have developed an initial view of the logical architecture - centred on four core entities: Package, Component, Attribute, and Market - but this is a starting point, not a fixed brief. We are looking for an architect who will interrogate that thinking, validate it against real business requirements, and produce a model that genuinely fits how our data needs to work. The initial scope is the market data product estate and the primary research data platform.
Technology choices for physical implementation have not been finalised. Google BigQuery is our existing lakehouse platform and the likely foundation, but decisions on the transformation layer, tooling, and overall implementation approach will be made during this engagement in collaboration with the CTO and Head of Data. The logical model itself is a technology-agnostic deliverable; implementation recommendations are expected alongside it.
The Engagement:
This contract covers the design and architecture phase of the data model project (Phase 1 of a phased delivery programme). The primary output is a signed-off logical data model and a technology implementation recommendation, produced in close collaboration with the CTO and Head of Data. The logical model is a technology-agnostic deliverable; the implementation recommendation should be grounded in Defaqto's existing technology landscape and make a clear case for the chosen approach.
A Senior Data Engineer. permanent hire, to be recruited, will own the build and ongoing implementation once the architecture is agreed. The architect's role is to design the model, recommend the implementation approach, and provide sufficient documentation that the engineering team can execute without ongoing dependency on the contractor.
Scope & Constraints:
In Scope
- Logical model design for the market data product estate - core entities, relationships, and attributes
- Technology implementation recommendation - physical implementation approach suited to the existing stack, presented to CTO and Head of Data
- Compatibility view specification for research platform continuity during transition
- Business rule formalisation for deduplication, ratings hierarchy, and attribute priority logic
- Stakeholder workshops and sign-off facilitation
- Data dictionary and handover documentation
Out of Scope
- Transformation layer build and implementation (owned by Senior Data Engineer)
- Research platform frontend adaptation (Phase 2 workstream)
- Full estate migration beyond the initial market data scope (Phase 2+)
- Ongoing data governance or catalogue ownership
- Graph database design or implementation