Lead Database Migration Engineer
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 2d ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 68d ago
The date the source published, not the day we noticed it (2026-07-08). Last seen at its source 3h ago.
Is it remote?
Marked remote on the employer's board
Their board carries a remote setting on this posting — a field they filled in, not wording we read. The location field names somewhere specific, which is usually where the team or the entity sits.
Who may apply?
Mumbai
The description states no restriction of its own. This is the source's own tag.
Pay not stated
Similar roles pay $6,750–7,250/mo
Middle 50% of 9 listings that do state pay — Engineering · all levels · India · USD/month. This employer has published no salary; this is what comparable listings we hold disclose, never converted between currencies or periods. How this is calculated.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
lever employer's own board first seen 38d ago · last seen 3h ago
The listing
Mactores is the agent-native AWS modernization firm. Most modernization work doesn't ship, it stalls in pilots, slips a year, or lands at three times the budget. We exist to ship it: production systems running, legacy retired, outcomes measured. Our delivery is built on Aedeon, the agent platform built by Mactores' founders' sister company, which absorbs the repetitive 60–70% of engagement work, discovery, dependency mapping, validation, test generation, that traditional consulting bills human hours against. Forward-deployed engineers own the rest: architecture, judgment, and cutover, on dates we commit to in the contract.
This is the sharp end of our Application & Database Modernization pillar. Enterprise customers are moving off Oracle and SQL Server license renewals coming due, stored-procedure layers nobody fully understands onto PostgreSQL and Aurora PostgreSQL. You'll own those heterogeneous migrations end to end: run the AWS DMS and SCT toolchain, then do the part the tools can't rebuild procedural business logic in PL/pgSQL when SCT flags a gap it can't close on its own. You ship the runbook, you run the cutover, you validate the result. When the migration lands, it's yours.
What you'll do?
- Lead end-to-end database migration initiatives: assessment, planning, schema conversion, execution, and post-migration validation.
- Design, configure, and manage AWS DMS and SCT environments and own migration quality, performance, and reliability.
- Author the migration runbooks the cutover lives or dies by: execution procedures, validation checkpoints, rollback plans, operational readiness.
- Perform migration assessments, dependency analysis, compatibility reviews, and migration strategy recommendations.
- Work with infrastructure, application, security, and platform teams to land migration outcomes.
- Drive migration testing: functional validation, performance testing, failover testing, production readiness reviews.
- Provide technical leadership to migration teams and hold the line on AWS migration best practices and governance standards.
- Lead conversion and refactoring of procedural database code Oracle PL/SQL (packages, procedures, functions, triggers, cursors) and SQL Server T-SQL (stored procedures, functions, triggers) into PostgreSQL/Aurora PostgreSQL PL/pgSQL, resolving the semantic and behavioral differences SCT identifies.
What we're looking for?
You'll be preferred if
- You've tuned production database performance, backup and restore strategy, and failover testing in high-stakes environments.
- You've led migration teams or mentored engineers through complex conversions.
- You bring experience with broader AWS cloud migration programs beyond the database layer.