Database Migration Engineer

Mactores describes itself as an agent native AWS modernisation firm, and its pitch is about finishing work that usually stalls: moving legacy enterprise systems onto AWS, retiring the old estate, and doing it on dates committed in the contract. This role is the database side of that. The posting makes a useful observation about the work, which is that every database migration has a layer the automated tools cannot finish, and that layer is the job. You would convert SQL, stored procedures and database objects into PostgreSQL compatible SQL and PL/pgSQL, work through what AWS Schema Conversion Tool produces, and flag the limitations that need senior review. Around that sits the operational half: maintaining the Flyway migration codebase, supporting PostgreSQL query optimisation, monitoring AWS DMS through full load and change data capture, and reconciling data between source and target so correctness is proven rather than assumed. It is genuinely a mid level role, since the posting repeatedly says the hardest cases escalate to a senior engineer.

What the posting requires

- 3 to 5 years as a database developer or engineer, with exposure to migration work
- Working experience with at least one of Oracle, Microsoft SQL Server, or PostgreSQL and Aurora PostgreSQL
- A bachelor's degree in computer science or a related field

What you would actually be doing

- Converting SQL, stored procedures and database objects into PostgreSQL compatible SQL and PL/pgSQL, escalating complex or ambiguous cases to a senior engineer
- Working through AWS Schema Conversion Tool findings and flagging limitations that need senior review
- Maintaining the Flyway migration codebase: versioned scripts, repeatable migrations and rollbacks
- Identifying and troubleshooting database related application bugs, with support on the harder ones
- Supporting PostgreSQL query optimisation through execution plans, indexing and query rewrites
- Monitoring AWS DMS during full load and change data capture phases, and helping diagnose data and performance issues
- Validating and reconciling data between source and target databases, which the posting describes as proof rather than confidence
- Working with application teams to align SQL behaviour and performance expectations before cutover

Location and working pattern

Mumbai. This is consulting delivery, so the work is organised around client engagements and committed cutover dates.

A good fit if

You are a database engineer who wants AWS depth, or a backend engineer who has drifted into data work and wants to make that the specialism. The escalation path is unusually clearly described, which makes it a reasonable step up rather than a role that quietly expects senior judgement.

Think twice if

You want product engineering. This is client facing modernisation work with the deadlines and delivery pressure that implies, and much of the day is careful, detailed conversion and verification rather than green field building.