3 of 3 Contract Domain Models Jobs in the UK excluding London

enterprise data architecture, data domain modelling, and information architecture. Proficient in conceptual, logical, and physical data modelling techniques. Experience defining canonical models, domain models, and analytical models. Good understanding of data governance, data quality, metadata, and lineage. Ability to develop and communicate data strategies … Architect role. Extensive knowledge and understanding of Azure. Active SC Clearance. Experience gathering and translating stakeholder requirements into architectural designs. Understanding of how data models translate into physical cloud implementations. Ability to build data strategy and modelling transition roadmaps. Experience creating architecture principles, standards, and models. Able to explain ...

/or logical data modelling Understanding of data analytics, APIs, databases, and related technologies would also be a plus Building conceptual/logical data models that accurately represent data relationships Working with both technical and business teams to elicit requirements and understand the business Governance and oversight of data … models ensuring they conform to agreed principles and standards Supporting the delivery of change activity and ensuring that Business Domain Models meet the business needs Ability to learn and adapt quickly Ability to work independently and as a part of a team Software development experience Experience ...

datasets, network efficiency, and instrumentation/observability API contract collaboration: Work with backend engineers on predictable API contracts via BFF (pagination, aggregation shapes, response models, error semantics) Security-by-design delivery: Apply secure front-end practices (auth/session hygiene, safe client-side data handling, dependency hygiene) Accessibility & usability … large datasets and frequent UI interactions (virtualisation, event handling) Strong TypeScript capability across: typed component APIs (props/contracts), shared domain models/DTOs, safe typing around API responses, error and async flows, sensible user use of generics/utility types without over-engineering Proven judgement selecting ...