1. Context and positioning of the position
@fric Payment Solutions (@PS) is the fintech subsidiary of the @fric group. In a regulated environment, demanding in terms of data availability and security, the DBA occupies a critical function: he/she guarantees the reliability, performance and security of all databases supporting the group’s applications.
2. General Mission
The DBA is responsible for the governance, performance, availability, and security of the databases within the @PS ecosystem, whether NoSQL (MongoDB) or relational (SQL). They proactively monitor production environments, support application teams in optimizing data access, and contribute to automation, business intelligence reporting, and Level 3 (N3) support for the IT HelpDesk.
3. Key Responsibilities
3.1 Governance and mapping of databases
To have a comprehensive, documented and controlled view of all the databases used by the group’s applications.
Main activities
ā¢ Create and maintain a complete inventory of databases (type, version, size, environment).
ā¢ Produce standardized technical documentation (diagram, flow, application dependencies).
ā¢ Centralize documentation on a shared platform (internal wiki / Git).
Associated performance indicators
ā 100% of databases identified and documented.
ā Documentation validated and updated at least once per quarter.
ā Average time to identify a base or a scheme < 5 minutes.
3.2 MongoDB administration and optimization
Strengthen internal expertise on MongoDB in order to optimize the performance, scalability and resilience of systems.
Main activities
ā¢ Master advanced concepts: Replica Set, Sharding, Aggregation Pipeline, Transactions.
ā¢ Conduct a review of the existing MongoDB architecture.
ā¢ Suggest improvements (partitioning, indexing, replication).
Associated performance indicators
ā At least one structural optimization implemented per critical MongoDB application.
ā Reduction in average response time for critical requests ā„ 30%.
ā MongoDB availability ā„ 99.9%.
3.3 Administration and optimization of relational databases (SQL)
Ensure the day-to-day administration and optimization of relational databases (SQL) in order to guarantee their performance, integrity and availability.
Main activities
ā¢ Ensure the day-to-day administration of relational databases (creation, user and rights management, maintenance).
ā¢ Optimize SQL queries and analyze execution plans.
ā¢ Manage the indexing, partitioning and evolution of relational schemas.
ā¢ Review the alignment of the data model with application requirements.
Associated performance indicators
ā Reduction in the average execution time of critical SQL queries ā„ 25%.
ā Availability of critical relational databases ā„ 99.9%.
ā 100% of production relational databases covered by a planned maintenance policy (update, reindexing, etc.).
3.4 Database Observability and Monitoring
Implement observability tools to enable proactive monitoring of databases.
Main activities
ā¢ Deploy monitoring tools (performance, latency, load, connections).
ā¢ Set up automatic alerts on critical thresholds.
ā¢ Regularly analyze production metrics.
Associated performance indicators
ā 100% of production bases supervised.
ā Mean time to detect incident (MTTD) < 5 minutes.
ā Reduction of critical database-related incidents ā„ 40%.
3.5 Interaction with application layers (Java / Spring)
Acquire the necessary basics in Java / Spring in order to better analyze application interactions with databases.
Main activities
ā¢ Master the fundamentals of Java / Spring Boot.
ā¢ Understanding ORM mechanisms (JPA / Hibernate).
ā¢ Read and analyze the data access code.
Associated performance indicators
ā Ability to audit 100% of the modules providing access to critical databases.
ā Optimization recommendations validated regularly with the backend team.
3.6 Application-side MongoDB access optimization
Improve the performance of MongoDB queries by analyzing the connection modules used in projects.
Main activities
ā¢ Analyze drivers, connection pools, and application configurations.
ā¢ Perform a review of slow queries.
ā¢ Propose targeted technical optimizations.
Associated performance indicators
ā Reduction in the number of slow requests ā„ 50%.
ā Reduction in the average execution time of critical queries by at least 25%.
3.7 Review and optimization of Spring Boot projects
Ensure optimal use of relational and NoSQL databases in Spring Boot projects.
Main activities
ā¢ Analyze repositories (native JPA / SQL).
ā¢ Audit complex indexes and queries.
ā¢ Formulate optimization recommendations.
Associated performance indicators
ā Audit performed on 100% of active Spring Boot projects.
ā Adoption rate of recommendations ā„ 70%.
ā Measurable improvement in application performance.
3.8 Resilience and continuity of service of relational databases
Ensuring continuity of service and high availability of relational databases.
Main activities
ā¢ Analyze existing architectures.
ā¢ Propose replication/failover mechanisms.
ā¢ Perform failure scenario tests.
Associated performance indicators
ā Implementation of at least one recovery strategy (HA/DR).
ā Recovery time (RTO) in line with the objectives set.
ā Data loss (RPO) close to zero.
3.9 Backup and Recovery Policy
Secure critical data through a robust and tested backup policy.
Main activities
ā¢ Define backup strategies (frequency, retention, storage).
ā¢ Automate backups.
ā¢ Perform regular restoration tests.
Associated performance indicators
ā 100% of production databases are automatically backed up.
ā Restoration tests carried out at least twice a year.
ā Restoration success rate ā„ 99%.
3.10 Automation and scripting (Python)
Use Python to automate recurring administration and reporting tasks.
Main activities
ā¢ Master the basics of the Python language.
ā¢ Develop audit, backup and monitoring scripts.
ā¢ Integrate these scripts into existing processes.
Associated performance indicators
ā Automation of at least five critical tasks.
ā Operational time savings ā„ 20%.
3.11 Dashboards and decision-making reporting
Provide clear dashboards for monitoring applications in production (@fric Remit, MdA).
Main activities
ā¢ Define the key indicators (volume, performance, errors).
ā¢ Design dynamic dashboards.
ā¢ Make the dashboards available to the relevant teams.
Associated performance indicators
ā 100% of critical applications covered by dashboards.
ā Internal user satisfaction ā„ 80%.
ā Data updates in near real-time.
3.12 Level 3 Support ā IT HelpDesk Support
Strengthen the capacity to resolve critical database-related incidents by providing level 3 (N3) support to the IT HelpDesk team.
Main activities
ā¢ Handle complex incidents involving databases (MongoDB, relational databases).
ā¢ Conduct in-depth root cause analysis (RCA) of critical incidents.
ā¢ Collaborate closely with the IT HelpDesk (N1/N2), Backend and Infrastructure teams.
ā¢ Contribute to the documentation of recurring incidents and resolution procedures.
ā¢ Train and transfer skills to the IT HelpDesk on common database issues.
Associated performance indicators
ā N3 level BD incident resolution rate ā„ 95%.
ā Mean time to resolve (MTTR) of critical incidents reduced by at least 30%.
HOW TO APPLY:
Send your CV to cheformylene@gmail.com