Senior Engineer for Centric PLM Migration (C#/.NET)
Budget: €2 – €6 EUR
Summary
Senior Software Engineer – Centric PLM Migration (C# / .NET)
Duration: 6 months, full-time (~40 hrs/week)
Location: Remote
Overview:
Fabletics is migrating its Product Lifecycle Management system from Centric PLM 7.2 → 8.0.
A migration engine already exists in C# (.NET 4.7.2). This role is to take ownership of that codebase, stabilize it, and drive it to production.
This is not a greenfield build. You will be working with:
- real production data
- live APIs with inconsistent behavior
- complex dependency ordering across product hierarchies
You should be comfortable stepping into an incomplete system and making it reliable.
What You’ll Own:
Migration Engine (C# / .NET 4.7.2)
- Read from Centric 7.2 PostgreSQL HSE tables (ed_style, ed_colorway, ed_sku)
- Write to Centric 8.0 REST APIs (/styles, /product_colors, /skus)
- Enforce strict dependency sequencing:
-- reference data (Seasons, Categories, Size Ranges, etc.)
-- then Style → Colorway → SKU hierarchy
- Resolve foreign key dependencies across multiple reference types
- Ensure the migration is fully idempotent and safe to re-run
Data & Attribute Mapping
- Finalize ~30+ custom attribute mappings in the C8 tenant
- Resolve enum mismatches between C7 and C8
- Fix data type inconsistencies causing API failures
Reliability
- Stabilize API interactions (handling 500s, retries, edge cases)
- Improve logging (NLog) for traceability
- Ensure failed batches can be resumed safely
Success Criteria (First 6–8 Weeks)
- End-to-end migration of a representative datasets. Example: (Style → Colorway → SKU)
- No data integrity issues (no orphaned or mismatched records)
- Migration is fully re-runnable without duplication
- API interactions stabilized (no recurring unexplained failures)
Required Experience
- Strong C# / .NET experience (comfortable in existing production code)
- PostgreSQL and SQL Server (schema analysis, querying across systems)
- REST API integrations (auth flows, debugging, error handling)
- Proven experience with data migrations involving dependency ordering
- Experience building idempotent / re-runnable data pipelines
Strongly Preferred
- Centric PLM (7.x or 8.x)
- PLM / ERP integrations (e.g., SAP, BlueCherry)
- Experience working in legacy .NET environments
AI-Assisted Development
- We expect you to use AI tools effectively.
- In your proposal, include:
-- The tools you use (Copilot, Cursor, Claude Code, etc.)
-- A specific example of how AI helped you understand or modify an unfamiliar codebase
-- How you validate AI-generated code in high-risk scenarios (like migrations)
Who This Is NOT For
- Engineers without hands-on data migration experience
- Developers who primarily work on greenfield builds
- Candidates uncomfortable debugging live APIs and incomplete documentation
To Apply
Include:
- A concise example of a data migration or integration you shipped
-- What were the dependencies?
-- What broke?
-- How did you make it reliable?
- Any experience with Centric PLM or similar systems
- Your AI tool usage (with a concrete example)
- Your availability to start
Senior Software Engineer – Centric PLM Migration (C# / .NET)
Duration: 6 months, full-time (~40 hrs/week)
Location: Remote
Overview:
Fabletics is migrating its Product Lifecycle Management system from Centric PLM 7.2 → 8.0.
A migration engine already exists in C# (.NET 4.7.2). This role is to take ownership of that codebase, stabilize it, and drive it to production.
This is not a greenfield build. You will be working with:
- real production data
- live APIs with inconsistent behavior
- complex dependency ordering across product hierarchies
You should be comfortable stepping into an incomplete system and making it reliable.
What You’ll Own:
Migration Engine (C# / .NET 4.7.2)
- Read from Centric 7.2 PostgreSQL HSE tables (ed_style, ed_colorway, ed_sku)
- Write to Centric 8.0 REST APIs (/styles, /product_colors, /skus)
- Enforce strict dependency sequencing:
-- reference data (Seasons, Categories, Size Ranges, etc.)
-- then Style → Colorway → SKU hierarchy
- Resolve foreign key dependencies across multiple reference types
- Ensure the migration is fully idempotent and safe to re-run
Data & Attribute Mapping
- Finalize ~30+ custom attribute mappings in the C8 tenant
- Resolve enum mismatches between C7 and C8
- Fix data type inconsistencies causing API failures
Reliability
- Stabilize API interactions (handling 500s, retries, edge cases)
- Improve logging (NLog) for traceability
- Ensure failed batches can be resumed safely
Success Criteria (First 6–8 Weeks)
- End-to-end migration of a representative datasets. Example: (Style → Colorway → SKU)
- No data integrity issues (no orphaned or mismatched records)
- Migration is fully re-runnable without duplication
- API interactions stabilized (no recurring unexplained failures)
Required Experience
- Strong C# / .NET experience (comfortable in existing production code)
- PostgreSQL and SQL Server (schema analysis, querying across systems)
- REST API integrations (auth flows, debugging, error handling)
- Proven experience with data migrations involving dependency ordering
- Experience building idempotent / re-runnable data pipelines
Strongly Preferred
- Centric PLM (7.x or 8.x)
- PLM / ERP integrations (e.g., SAP, BlueCherry)
- Experience working in legacy .NET environments
AI-Assisted Development
- We expect you to use AI tools effectively.
- In your proposal, include:
-- The tools you use (Copilot, Cursor, Claude Code, etc.)
-- A specific example of how AI helped you understand or modify an unfamiliar codebase
-- How you validate AI-generated code in high-risk scenarios (like migrations)
Who This Is NOT For
- Engineers without hands-on data migration experience
- Developers who primarily work on greenfield builds
- Candidates uncomfortable debugging live APIs and incomplete documentation
To Apply
Include:
- A concise example of a data migration or integration you shipped
-- What were the dependencies?
-- What broke?
-- How did you make it reliable?
- Any experience with Centric PLM or similar systems
- Your AI tool usage (with a concrete example)
- Your availability to start
Related categories:
.NET
C# Programming
Software Architecture
PostgreSQL
Microsoft SQL Server
API Development
API Integration
REST API