[Remote] Database Engineering Intern – PostgreSQL & Microservices

Descrição da Vaga

Requisitos

• Currently enrolled in or recently completed a Master's degree in Computer Science
• Currently enrolled in or recently completed a Master's degree in Software Engineering
• Currently enrolled in or recently completed a Master's degree in Data Engineering
• Currently enrolled in or recently completed a Master's degree in Information Systems
• Currently enrolled in or recently completed a Master's degree in a closely related technical field
• Schema design
• Relationships and normalization
• Indexing and constraints
• Solid SQL skills (writing, reading, and reasoning about queries)
• Conceptual understanding of microservices architecture
• Conceptual understanding of modular monoliths
• Conceptual understanding of database ownership and service boundaries
• Ability to read and understand an existing codebase to identify how data is accessed
• Strong technical writing skills — you will be producing documentation developers actually rely on
• Experience with Docker or containerized environments
• Familiarity with Strapi or CMS-backed systems
• Experience creating ER diagrams or schema documentation
• Exposure to database migration tools (Prisma Migrate, TypeORM migrations, Flyway, Liquibase)
• Prior work on systems with more than one database or schema

Responsabilidades

• Analyze the existing database schemas used by the NestJS backend and Strapi CMS
• Document table ownership by backend module (logical microservice boundaries)
• Define and document which backend modules own which tables, which modules/services are allowed to read or write specific data, and future target databases for each logical domain
• Help restructure tables within the existing databases to align with microservices architecture without breaking existing code
• Assist in designing safe migration strategies, including:
• Incremental migrations
• Temporary compatibility layers (e.g., views or aliases where appropriate)
• Rollback considerations
• Build developer-facing database documentation, including:
• Schema dictionaries
• ER diagrams
• Naming conventions
• Data lifecycle and retention rules
• Collaborate with backend engineers to map:
• Tables → modules
• Modules → future microservices
• Help establish internal standards so future schema changes follow a clear, documented process