About the role
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.
Every database migration has a layer the tools can't finish. AWS SCT converts what it can and flags the rest, the SQL that ran fine on the source engine and behaves differently on the target, the logic no one documented. Senior engineers own the hardest of those calls; this role is where you build toward that, working through the conversion, validation, and reconciliation work with support from senior team members on the calls that need more judgment.
As our Database Migration Engineer, you'll work inside our Application & Database Modernization pillar, supporting hands-on migration work across engagements (Oracle-to-PostgreSQL/Aurora and SQL Server-to-PostgreSQL, depending on project). Aedeon and AWS tooling absorb the repeatable conversion and regression work; you'll handle the conversion, testing, and reconciliation tasks directly, and work closely with senior engineers on the more complex SCT findings and performance edge cases. You'll work with application teams, cloud engineers, and customer stakeholders under the guidance of a lead engineer to land migrations that perform, reconcile, and hold up after go-live.
What you'll do?
What you'll bring?
You'll be preferred if you've:
How we work?
Aedeon absorbs the discovery, mapping, and validation grind — the 60–70% of hours a traditional consulting engagement of equivalent scope staffs for. Your hours go where the tools stop: conversion judgment, cutover strategy, and the procedural-code gaps only an engineer can close. We commit to fixed delivery dates and absorb the overage cost for delays inside our control, so the runbook you write and the cutover you run carry real weight. You embed with the customer's team and own the outcome — not a workstream, the outcome.
Tech jobs straight from company career pages. No recruiters, no middlemen, no spam.