Neo4J Admin

ONLY OPEN TO W2 EMPLOYEES



Role: Neo4j Admin

Must Have Technical/Functional Skills

1. Large-scale DBA skills

a. Strong understanding of database concepts: ACID, transactions, consistency, durability, concurrency, isolation, indexing, and query planning.
b. Experience with data modeling principles (entity vs. relationship modeling) and translating business requirements into graph models.
c. Familiarity with common DB admin duties: backups, restores, capacity planning, high availability, failover, upgrades.

2. Infrastructure, deployment, and automation

a. Operating systems and servers: strong Linux administration skills (systemd, networking, storage).
b. Containers and orchestration: Docker, Kubernetes; running Neo4j in containerized environments.
c. Cloud platforms: deploying and operating Neo4j on Azure, or Google Cloud Platform.
d. Automation and IaC: experience with Ansible, Terraform, or similar tools to automate deployments and configuration.
e. CI/CD and release processes for database migrations and schema changes.

3. Security and compliance
a. Authentication and authorization: role-based access control, LDAP/Active Directory integration.
b. Encryption: TLS for client-server and intra-cluster communication, data-at-rest encryption if used.
c. Auditing and compliance: logging, audit trails, and compliance requirements relevant to your organization.

4. Programming, integration, and tooling
a. Drivers and APIs: familiarity with official drivers (Java, JavaScript, Python, .NET) and transactional vs. reactive usage.
b. Scripting and automation: Python, or other scripting languages for maintenance tasks and automation.
c. Integration patterns: using Neo4j in microservices or ETL pipelines; knowledge of Kafka, stream processing, or messaging integrations.

5. Neo4j-specific technical skills (Could be upskilled via Neo4j Certs)
a. Cypher query language: writing, optimizing, and profiling queries.
b. Indexing and constraints: when and how to use property indexes, fulltext indexes, and unique constraints.
c. Data import tools: neo4j-admin import, LOAD CSV, APOC import procedures.
d. APOC and user-defined procedures: using APOC library for ETL, graph algorithms, and helper functions.
e. Neo4j architecture: knowledge of single-instance vs. causal clusters, read replicas, core/raft quorum concepts.
f. Backup and recovery: online backups, incremental backups, point-in-time recovery approaches.
g. Upgrades and patching: rolling upgrades in clusters, migration strategies between major versions.