Description

 Own architectural direction and review across the build

 Validate the data model against what a CRM genuinely requires, not only what the

current requirements name

 Guide the multi-tenancy implementation and the boundaries between modules

 Define how the application integrates with external systems it does not own

 Decide when a module is ready to become its own service, and when it is not

 Set the review standard for the team

What we need

 You have built or deeply owned a CRM, not only configured one. Salesforce,

Dynamics or a custom platform all count

 Java and Spring Boot architecture at a level where you can review code and

schema, not only diagrams

 PostgreSQL, including multi-tenant design and row-level security

 Azure, ideally including AKS and Entra ID

 Integration design across systems under different ownership

 Comfortable telling a team their design is wrong, including after they have started

 Excellent Communication Skills

Helpful

 A CRM implementation that went badly, and a clear account of why

 Taking a modular monolith through a later split into services

 Data migration or consolidation at scale

Key Skills

Education

Bachelor's degree