Profisee MDM Architect with C#.NET - REMOTE


Depends on Experience
Accepts corp to corp applications
Contract - W2
Contract - 12 Month(s)


Profisee MDM Engineer

Job Details

Profisee MDM Architect with C#.NET

12+Months Contract

Remote Job (with Travel)



  1. Should have 12+ years of IT experience and 6+ years of experience in MDM architecture, design, development and support with leading MDM tools
  2. Extensive MDM experience in Profisee MDM Tool
  3. Should have 6+ years of experience in ETL development, support and operations with emphasis on Data quality
  4. Should have in depth knowledge on Bill Inmon and Ralph Kimball methodologies to design data warehouses
  5. Should have in depth understanding on Data Warehousing, Data Analysis, Data Profiling, Data Cataloging, Master Data Management (MDM), Data Quality, Data Lineage, Data Dictionary, Data Mapping, Data Policy and Data Governance
  6. Should have thorough understanding of Master Data hierarchy and implemented multi-Domain MDM for Fortune 100 organizations
  7. Should have done extensive Data Cataloguing using Purview Tool
  8. Comprehensive knowledge and experience in process improvement, normalization/de-normalization, data extraction, data cleansing and data manipulation
  9. Should have participated in MDM workshops with business and technology stakeholders
  10. Should have written complex SQL queries for data analysis and profiling
  11. Should have cross global location experience and been part of a team of atleast 10+ members in a global delivery model
  12. Should have experience in gathering business requirements by collaborating with business users, stakeholders and SMEs
  13. Should have experience in working with product managers, project managers, business users, applications development teams, DBA teams and Data Governance team on a daily basis to analyze requirements, design, development and deployment technical solutions
  14. Should have excellent communication and leadership skills
  15. Able to articulate ideas to both technical and non-technical stakeholders.


Guru Nagaraj