Neo4J Platform Architect

Neo4j Platform Architect

• Lead discovery and define the target architecture — including options for consolidating existing databases, instance sizing, and the overall tenancy model.
• Decide how workloads get deployed — building a clear framework for choosing between self-hosted infrastructure and managed SaaS (Neo4j AuraDB), based on regulatory, data residency, and security requirements.
• Design the cluster architecture — topology, high availability, and disaster recovery, tailored to each workload’s criticality tier.
• Own the migration strategy end-to-end — how databases get consolidated, how cutover happens, how you validate success, and how you’d roll back if something goes wrong.
• Produce the core planning documents — sizing and cost model inputs, and a consolidated Discovery & Assessment Findings Report with a prioritized roadmap leadership can act on.
• Set the platform standards — security, access control, monitoring, backups, and release management that the whole platform will run on.
• Act as the design authority for the engineering team — reviewing and approving build and migration work before it ships.
• Present to stakeholders — walking client leadership and steering committees through architecture options, trade-offs, and your recommendations.

• 8+ years in data platform architecture, including 4+ years of hands-on work with Neo4j Enterprise
• A track record of architecting and defending technical recommendations in front of client stakeholders, backed by clear design documentation

• Deep understanding of Neo4j causal clustering — Raft consensus, quorum behavior, and leader election
• Solid grasp of multi-database tenancy, database-level RBAC, and isolation models
• Strong command of Neo4j sizing: page cache and heap configuration, licensable-core sizing, storage and transaction-log volume planning
• Hands-on experience with migration mechanics: neo4j-admin dump/load, online backup and restore, delta synchronization, and read-replica seeding
• Experience planning version upgrades and end-of-life transitions across Neo4j major versions
• Solid cloud infrastructure architecture skills, ideally on AWS — compute selection, network topology, and private connectivity patterns
• Proven experience consolidating fragmented database estates into a shared or multi-tenant platform

• Experience architecting on Neo4j AuraDB — its limits, architecture, and private endpoint connectivity
• Familiarity with Graph Data Science and Bloom deployment and licensing
• Experience in a regulated industry (life sciences, pharma, financial services), including qualification and validation processes
• Infrastructure-as-Code experience (Terraform or CloudFormation)
• Neo4j Certified Professional and/or AWS Solutions Architect Professional certification
• Exposure to FinOps or software asset management concepts