Data & Migration Engineer

Planet Depos ships enterprise software for the legal industry, and the certified record is our product: if the data is wrong, the business is wrong. This role owns the data layer of our platform, and that is three jobs in one. Design: the data models and data contracts that our product teams, our low-code estate, our integrations, and our analytics all build against. Migration: we are replacing the legacy system the business runs on, which means moving two decades of operational data out of an undocumented database safely and provably while the business keeps running on it. Quality: the feeds, reconciliation, and monitoring that make the data trustworthy every day, not just on cutover day.

ESSENTIAL JOB RESPONSIBILITIES:

• Own the target data model in partnership with the Group Architect: the canonical entities the platform is built around, identity and access-bearing structures, and the boundaries with systems that own their own truth (CRM, finance)
• Own the data workstream of the legacy-platform replacement end to end: profiling, mapping, extraction, transformation, load, verification, and a staged, rehearsed cutover
• Build and operate the ongoing synchronization that keeps the new platform current through the transition, engineered for a fragile legacy source: rate limits respected, timeouts and retries handled, silent feed breaks made impossible by monitoring
• Design the data contracts our integrations run on: the supported surfaces and interchange formats that let customer systems and partner tools consume our data without bespoke plumbing
• Give the low-code estate a safe foundation: supported data surfaces for the citizen-developer applications and flows the business runs on, replacing direct database access over time
• Build the reconciliation and data-quality evidence: automated counts and checksums, exception queues, and human-readable verification reports
• Create and maintain sanitized and synthetic datasets from production, and manage dataset promotion across environments, so non-production work never requires production data
• Lay the analytics foundation with the platform team: safe read paths (replicas, sanitized exports) and data structures the business can query without touching production
• Steward database design standards with the platform team: DevOps owns infrastructure operations; this seat owns how data is modeled, accessed, and kept trustworthy
• Document the models, mappings, and pipelines so they are auditable and transferable, readable by both humans and agents

REQUIRED WORK OPERATING STANDARDS:

• Evidence over assertion. The number is right because the reconciliation proves it, not because the script ran.
• You make your work legible: entity models, mapping documents, runbooks, and pipelines someone else could operate.
• You raise solutions alongside your objections, with an owner and a date.
• You have worked in a fast-moving environment and stayed effective when priorities shifted under you.
• You can disagree, and then commit wholeheartedly once a call is made.
• You treat access to sensitive data as a responsibility to design around, not a convenience to accumulate.

REQUIRED EXPERIENCES:

You have moved production data between live systems without losing any.

You have executed at least one legacy-to-modern migration of a business-critical system, with the discipline that implies: reverse-engineering an undocumented source schema, building the field-level crosswalk from what the data actually contains, staged runs, parallel verification windows, documented reconciliation, and a rollback plan you could actually invoke. You know a migration is done when the evidence says so, not when the script exits zero.

Evidence looks like: "Migrated the operational database of a revenue-carrying system with row-level reconciliation and zero unexplained variance," or the mapping document for a several-hundred-table legacy schema that became the build contract for the replacement. In an interview, you can walk through the migration that went sideways, what the reconciliation caught, and what you changed.

You have designed data models and data contracts that a whole estate runs on.

You have owned an operational data model with many consumers: product applications, low-code and citizen-developer workloads, third-party integrations, and analytics, each pulling in a different direction. You know how to define the canonical entities, decide which system is the source of truth for what, and draw the boundary where another system's model stops being yours. You design the supported surfaces (views, APIs, contracts) that let those consumers buil