Time's up! We are no longer accepting applications.
For a client in the IT sector, we are looking for an experienced IT architect focused on relational database systems (RDBMS) to take responsibility for the solution design of a new data-intensive application.
Typical tasks:
Analyzing existing system landscapes and gathering business and technical requirements for data storage.
Designing and conceptualizing a scalable, highly available, and secure RDBMS architecture (e.g., based on PostgreSQL, Oracle, or MS SQL Server).
Creating and optimizing data models (physical, logical) and defining data flows.
Advising the development team on implementing database structures, stored procedures, and queries.
Planning and supporting data migration strategies from legacy systems.
Defining standards for backup, recovery, and disaster-recovery scenarios.
Relevant technologies, tools, or methods:
RDBMS: PostgreSQL, Oracle, MS SQL Server, MySQL/MariaDB
Cloud platforms: AWS RDS, Azure SQL, Google Cloud SQL
Modeling tools: ER/Studio, Sparx Enterprise Architect, draw.io
DevOps & IaC: Terraform, Ansible, Jenkins for automating DB deployments
Monitoring: Prometheus, Grafana, specialized DB monitoring tools (e.g., pgAdmin, Oracle Enterprise Manager)
Typical KPIs or success metrics:
System availability and uptime (>99.95%)
Response times for critical database queries (<200ms)
Meeting RTO/RPO targets (Recovery Time/Point Objective)
Scalability: performance under load simulation (e.g., 2x user growth)
Reduction of database operational costs through optimized design.
Key challenges, risks, or specifics:
Ensuring data consistency and integrity in distributed systems.
Managing schema changes in production (zero-downtime deployment).
Balancing normalization and performance optimization (denormalization).
Securing sensitive data according to GDPR and other compliance requirements.
Concrete deliverables:
Final solution architecture document for the database solution.
Implemented and approved data model.
Proof-of-concept for critical non-functional requirements (e.g., high availability).
Migration plan and test protocols.
Lessons learned/best practices:
Early involvement of development and operations teams is essential.
Automated tests for database schema changes prevent regressions.
Consider security-by-design from the start, not as an add-on.