Mactores is a trusted leader among businesses in providing modern data platform solutions. Since 2008, Mactores have been enabling businesses to accelerate their value through automation by providing End-to-End Data Solutions that are automated, agile, and secure. We collaborate with customers to strategize, navigate, and accelerate an ideal path forward with a digital transformation via assessments, migration, or modernization.
You'll own heterogeneous database migrations end to end for enterprise customers moving off Oracle and SQL Server onto PostgreSQL and Aurora PostgreSQL. That means running the AWS DMS and SCT toolchain, then doing the part the tools can't: rebuilding 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.
What you'll do?
Lead end-to-end database migration initiatives, including assessment, planning, schema conversion, execution, and post-migration validation.
Design, configure, and manage AWS DMS and SCT environments while ensuring migration quality, performance, and reliability.
Author comprehensive migration runbooks that define execution procedures, validation checkpoints, rollback plans, and operational readiness activities.
Perform database migration assessments, dependency analysis, compatibility reviews, and migration strategy recommendations.
Collaborate with infrastructure, application, security, and platform teams to ensure successful migration outcomes.
Drive migration testing activities, including functional validation, performance testing, failover testing, and production readiness reviews.
Provide technical leadership and guidance to migration teams while ensuring adherence to 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 semantic and behavioral differences identified by SCT.
What we're looking for?
8–12 years of professional experience in database architecture and migration delivery
Hands-on expertise in AWS Database Migration Service (DMS) and AWS Schema Conversion Tool (SCT) for enterprise-scale database migrations
Deep proficiency in Oracle, SQL Server, PostgreSQL, and Aurora PostgreSQL environments, including migration planning, execution, and optimization
Proven background in delivering heterogeneous database migrations across on-premises, cloud, and AWS environments
Knowledge of production database operations, including backup and restore strategies, parameter tuning, performance optimization, and failover testing
Skills in authoring and executing migration runbooks, validation plans, cutover procedures, rollback strategies, and post-migration stabilization activities
Strong understanding of AWS database services, migration best practices, and integration with broader cloud migration programs
Experience engaging directly with enterprise customers, architecture teams, and migration stakeholders to drive successful delivery outcomes
Strong hands-on experience converting Oracle PL/SQL and SQL Server T-SQL business logic to PL/pgSQL, including handling of exception handling models, cursor semantics, autonomous transactions, sequences/identity columns, implicit data type conversions, and proprietary built-in packages/functions with no native PostgreSQL equivalent
Ability to identify and remediate SCT action items and manual conversion gaps in procedural code (e.g., DBMS_* packages, UTL_* utilities, SQL Server system procedures, dynamic SQL, and nested/recursive procedure calls) and validate converted logic through functional and regression testing.
You'll be preferred if you
Have tuned production database performance, backup and restore strategy, and failover testing in high-stakes environments.
Have led migration teams or mentored engineers through complex conversions.
Bring experience with broader AWS cloud migration programs beyond the database layer.
