Data Migration Engineer positions focus on delivering results in their domain. This page aggregates open Data Migration Engineer roles and what employers typically expect.
## π€πΌ **About gaiia** At gaiia, we're building the leading platform for Communications Service Providers (CSPs) that truly care about their customers. Our core product is an operating system (OS) for telcos that manages billing, operations, automation and everything in between. We're passionate about taking care of our people, and it's not just lip service. We want you to focus on your job while we care for everything else. We offer competitive pay and benefits, flexible vacations, attractive stock options, unparalleled transparency, and a 100% remote environment. We're excited to have you join us for your next career adventure! ## **π Role & Team** We're looking to hire a **Data Migration Engineer** to own the technical execution of data migrations that move customers from legacy systems into gaiia. You'll join the **Migration Solutions** team, which owns the end-to-end delivery of customer migrations. Within that team, you own the data β exploring source systems, exporting it, transforming it into gaiia's standard format, and driving its execution to a validated, production-ready state. You'll partner closely with the **Data Migration Specialist** β who owns the customer relationship and migration design β working from the business context and mapping rules they hand off. You'll also work alongside the **Migration Platform** team, who build and maintain the internal tooling that runs migrations: you'll live in it daily, improve it where you can, and specify the larger needs for them to build. This is a hands-on engineering role for someone who likes turning messy, real-world data into something clean, repeatable, and trusted. **π» What You're Going to Do** - Explore legacy source systems (databases, flat files, reports, APIs) to understand their structure, quality, and relationships in the context of gaiia's data model. - Export source data across a range of access methods β SQL, APIs, manual extracts, and database backups. - Transform exported data into gaiia's standard format by authoring declarative, version-controlled mapping files that encode the business rules defined with the Data Migration Specialist. - Execute migrations end-to-end on the internal migration platform: load, validate against target schemas, reconcile, and import to production. - Build and reuse mappings, templates, and validation rules so each migration is faster and more repeatable than the last. - Contribute small engineering improvements to the migration tooling β new validation rules, transforms, mapping updates β and raise larger needs to the Migration Platform team. - Diagnose and resolve data discrepancies during dry runs, UAT, and post-cutover. - Document mapping specs, transformation logic, and data anomalies so migrations are auditable and repeatable. ### π§ What Success Looks Like - Source data lands in gaiia accurately, completely, and on schedule, with discrepancies caught before go-live. - Transformation and validation work is reusable β later migrations build on your templates and rules rather than starting from scratch. - Data issues are diagnosed and resolved quickly, keeping migrations on schedule. - Tooling gaps are either fixed directly or clearly specified for the Migration Platform team. - The data you deliver is trusted β accurate and well-documented enough to present to customers with confidence. ### **ποΈ Qualifications** - Experience (3-5+ years) in data engineering, data migration, ETL, or a similar hands-on data role. - Strong command of ETL fundamentals β you treat extract β transform β load as a deliberate methodology: staging, repeatable/idempotent loads, full vs. incremental loads, and validation and reconciliation at each stage. - Hands-on data-manipulation fluency β comfortable querying, profiling, and reshaping data across languages (SQL, Python, JSON, or similar) and debugging issues in unfamiliar source schemas. - Experience extracting data from a variety of sources: relational databases, APIs, flat files, andβ¦