Want to know if this job is worth applying to?
Montpellier, Occitanie, France
Onsite
Available
Responsabilités principales :
Compétences et expérience requises:
Ce dont vous serez propriétaire
Pourquoi nous rejoindre ?
Stack Technique:
Qualification requise :
Bac+ 5 Master ou équivalent dans le domaine Informatique
--------------------------
Core Responsibilities
Architecting Abstraction: Design and maintain a Repository/Unit-of-Work layer that abstracts storage implementation, enabling us to swap database providers without impacting core business domains.
Multi-Engine Management: Manage the lifecycle of diverse data engines (PostgreSQL, SQL Server, MongoDB). You will define the "Standardized Interface" through which microservices access these engines.
Performance Engineering: Optimize complex queries, define indexing strategies, and implement CQRS/Read-Model patterns to ensure sub-100ms dashboard latency.
K8s-Native Operations: Lead the automation of database maintenance, including backups, point-in-time recovery (PITR), and seamless schema updates within a Kubernetes cluster (using Operators or Helm-based workflows).
Resiliency & Scalability: Implement Circuit Breaker patterns for data access and design horizontal scaling strategies for our persistent layers.
Required Skills & Experience
Deep Persistence Knowledge: Expert-level experience with both relational (PostgreSQL, SQL Server) and NoSQL (MongoDB) databases. You understand when to choose ACID compliance over eventual consistency.
Abstraction Patterns: Strong proficiency in Repository, Unit-of-Work, and CQRS patterns. You have experience building internal data-access libraries that hide ORM/Driver complexities.
Cloud-Native Data Ops: Experience managing database instances within Kubernetes. You know how to leverage K8s Operators for database lifecycle management (backup/restore/patching).
Performance Tuning: Proven ability to diagnose and fix performance bottlenecks (e.g., query execution plans, locking issues, indexing strategies, and connection pooling).
What You Will Own
The Data SDK: You will own the "Core Data Library" that all other teams use to communicate with our persistence layer.
System Reliability: You will define the RTO (Recovery Time Objective) and RPO (Recovery Point Objective) for all mission-critical data.
Evolutionary Architecture: You will lead the "Strangler Fig" migration efforts to move our existing monolithic database usage toward our new, decoupled architecture.
Why Join Us?
Architectural Decision: You will be actively involved in choosing the right tool for the job—whether that’s a traditional RDBMS or a specialized NoSQL store.
Platform Impact: Your work will be the foundation of our entire event-driven architecture, enabling the team to handle grid-scale telemetry.
Technological Maturity: we engineer how our services consume them. You will be driving a project focused on modernizing data access for the next gen.
Technical stack:
Language for Abstraction: C#, typescript
Patterns: CQRS, Unit-of-Work
K8s Ops: Postgres / timesclaleDB
IaC : Crossplane
Resiliency: Circuit Breakers
Performances: Redis (Read-Models)
Observability: OpenTelemetry
Relocation Assistance Provided: No
