Master Data Management Integration Engineer [REMOTE JOB]

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Preserve all substantive info. We need to parse the job description. Let's extract sections: - About the role: The first paragraph: "The Data Analytics group is seeking an experienced and motivated Integration developer who will work as part of a larger Data Management team to implement a Master Data Management capability, develop and implement data quality rules, evolve our organizational understanding and approach, and accomplish key objectives to our Data Strategy. The Integration Developer will liaise with stakeholders across the business, gain an understanding of different domains, and create a pathway to mastering their data." That's about the role. - Responsibilities: List under "Responsibilities Include, But Are Not Limited To" then bullet points. We need to extract each bullet. List: Execute DG-Data related projects and initiatives Execute processes and maintenance of various Master and Reference Data Management elements to ensure accurate data creation, transformation, and retention Inform DG Data policy, standards and procedures Work with stakeholders across the enterprise to construct processes and define rules for ensuring data validity and consistency across systems of record Collaborate/Coordinate with Data Governance Working Groups to apply governance specifications to the Master Data Support Data Owners/Stewards with strategic prioritization of MDM initiatives that support Business Objectives Implement, Maintain, and Evolve Data Governance and Stewardship Processes associated with the MDM ecosystem Audit and Validate Master Data definitions Leads/participates in defining business requirements to support system configuration changes Integration design/build/create approach for new initiatives/existing Note: The last bullet seems truncated: "Integration design/build/create approach for new initiatives/existing". Probably "Integration design/build/create approach for new initiatives/existing". We'll keep as is. - Required Education, Experience, & Skills: This includes required and also "Preferred Education, Experience, & Skills". We need to separate maybe into Requirements (required) and Qualifications (preferred) and Skills. But the instruction: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. "Required Education, Experience, & Skills" likely maps to Requirements (maybe also Skills). "Preferred Education, Experience, & Skills" maps to Qualifications (maybe also Skills). However we also have a separate Skills heading. We need to avoid duplication. We could put required education/experience under Requirements, preferred under Qualifications, and specific technical skills under Skills. Let's extract required: - Bachelor’s Degree in Computer Science or related field or equalivent combination of education and experience - 6+ Years of career experience, at least 3 years of relevant integration experience - Implement, Maintain, and Evolve Data Governance and Stewardship Processes associated with the MDM ecosystem (actually that's a responsibility, but also appears under required? It appears again in required list: "Implement, Maintain, and Evolve Data Governance and Stewardship Processes associated with the MDM ecosystemAudit and Validate Master Data definitions and Familiar with Agile Methodology". This seems like a mashup. Let's parse: The required list includes: "Implement, Maintain, and Evolve Data Governance and Stewardship Processes associated with the MDM ecosystemAudit and Validate Master Data definitions and Familiar with Agile MethodologyExperience with Python, SQL/PLSQL, Redshift, AWS Step functions, Lamda, Integration using API, Dataiku,Experience with ETL / Master Data Management tools (ie. Informatica, Profisee, Semarchy)Leads/participates in defining business requirements to support system configuration changesStrong analytics skill set and a high degree of proficiency in data profiling and modelingKnowledge of various data integration methodologiesUnderstanding solution architecture / implementing integration design (Ingress/Egress)Ability to develop and maintain strong internal and external relationships" So required includes many skill items. Preferred: "Master’s Degree" Pay Information: Salary range $96623 - $164259. Benefits: description of benefits. Schedule: Not explicitly mentioned; maybe full-time implied but not given. The posting says "Full-Time Salary Range". So schedule could be Full-Time. But we should only include Schedule if posting actually states it. It does mention "Full-Time Salary Range". That implies schedule is full-time. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states Full-Time Salary Range, which indicates schedule is full-time. So we could include Schedule with content "Full-Time". But is that explicit? It says "Full-Time Salary Range". That is about pay, not schedule explicitly but implies full-time. Might be acceptable to include Schedule with "Full-Time". However we need to be careful: The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Full-Time Salary Range". That's about pay, not schedule. It does not explicitly state schedule like "Full-Time" separate. But we could infer schedule is full-time. Safer to not include Schedule section unless explicit. There's no explicit schedule like "Work schedule: Monday-Friday, 9-5". So we omit Schedule. Now Benefits: we have description. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include duplicated lines. Ensure we preserve all substantive info. Let's craft sections:

  About the role

  The Data Analytics group is seeking an experienced and motivated Integration developer who will work as part of a larger Data Management team to implement a Master Data Management capability, develop and implement data quality rules, evolve our organizational understanding and approach, and accomplish key objectives to our Data Strategy. The Integration Developer will liaise with stakeholders across the business, gain an understanding of different domains, and create a pathway to mastering their data.

  Responsibilities

  • Execute DG-Data related projects and initiatives
  • Execute processes and maintenance of various Master and Reference Data Management elements to ensure accurate data creation, transformation, and retention
  • Inform DG Data policy, standards and procedures
  • Work with stakeholders across the enterprise to construct processes and define rules for ensuring data validity and consistency across systems of record
  • Collaborate/Coordinate with Data Governance Working Groups to apply governance specifications to the Master Data
  • Support Data Owners/Stewards with strategic prioritization of MDM initiatives that support Business Objectives
  • Implement, Maintain, and Evolve Data Governance and Stewardship Processes associated with the MDM ecosystem
  • Audit and Validate Master Data definitions
  • Leads/participates in defining business requirements to support system configuration changes
  • Integration design/build/create approach for new initiatives/existing
  Now Requirements: combine required education/experience and required skills. We need to list as
  • items. Let's extract required items clearly: - Bachelor’s Degree in Computer Science or related field or equivalent combination of education and experience - 6+ Years of career experience, at least 3 years of relevant integration experience - Familiar with Agile Methodology - Experience with Python, SQL/PLSQL, Redshift, AWS Step functions, Lambda, Integration using API, Dataiku - Experience with ETL / Master Data Management tools (e.g., Informatica, Profisee, Semarchy) - Leads/participates in defining business requirements to support system configuration changes - Strong analytics skill set and a high degree of proficiency in data profiling and modeling - Knowledge of various data integration methodologies - Understanding solution architecture / implementing integration design (Ingress/Egress) - Ability to develop and maintain strong internal and external relationships Also "Implement, Maintain, and Evolve Data Governance and Stewardship Processes associated with the MDM ecosystem" and "Audit and Validate Master Data definitions" appear in responsibilities already; but they also appear in required list. However we should not duplicate content. Since they are already in responsibilities, we might not repeat them under Requirements to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit them from Requirements, we might lose that detail if it's not elsewhere. But they are already in responsibilities list, so they are preserved. So we can omit duplicates. Now Qualifications: Preferred Education, Experience, & Skills: Master’s Degree. Also maybe other preferred? Only Master’s Degree mentioned. Thus Qualifications heading with

    Master’s Degree

    or
    • Master’s Degree
    . Since it's a single item, we can use

    . Skills: We could separate technical skills from responsibilities? But we already listed many skills under Requirements. The instruction says we can have Skills section. To avoid duplication, we could put specific technical skills under Skills, and keep education/experience under Requirements. Let's think. We have many skill items: Agile, Python, SQL/PLSQL, Redshift, AWS Step functions, Lambda, API integration, Dataiku, ETL/MDM tools, analytics, data profiling/modeling, data integration methodologies, solution architecture, relationship building. We could move those to Skills section, and keep Requirements for education/experience only. But we must preserve all info; duplication is okay? The instruction says do NOT repeat the job title as a heading and do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

    or drop it. It doesn't forbid duplication of content across sections, but better to avoid redundancy. However we need to decide. Given the headings list includes Skills, we should use it. Let's allocate: Requirements: Education and experience. - Bachelor’s Degree in Computer Science or related field or equivalent combination of education and experience - 6+ Years of career experience, at least 3 years of relevant integration experience Qualifications: Preferred education/experience/skills. - Master’s Degree Skills: Technical and soft skills. - Familiar with Agile Methodology - Experience with Python, SQL/PLSQL, Redshift, AWS Step functions, Lambda, Integration using API, Dataiku - Experience with ETL / Master Data Management tools (e.g., Informatica, Profisee, Semarchy) - Leads/participates in defining business requirements to support system configuration changes - Strong analytics skill set and a high degree of proficiency in data profiling and modeling - Knowledge of various data integration methodologies - Understanding solution architecture / implementing integration design (Ingress/Egress) - Ability to develop and maintain strong internal and external relationships Now Benefits: we have paragraph. Pay: we have salary range. Now we need to ensure we don't include Schedule. Now produce HTML. Check for any boilerplate: Remove lines like "Please note: This range is based on our market pay structures..." That's part of Pay info but it's explanatory; we should preserve substantive info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that note as part of Pay section? It's explanatory but still substantive. We'll include it as a

    under Pay. Similarly benefits description includes many details; we keep. Now ensure we don't include any navigation/legal/EEO etc. The text includes "This position will be posted for at least 5 calendar days..." that's boilerplate; we should remove. Also "At BAE Systems, we support our employees..." that's benefits, we keep. The "About BAE Systems, Inc." is company description; is that substantive? It's about the company, not the role. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About BAE Systems, Inc." is not explicitly listed but could be considered company overview, maybe not required. However it's substantive info about the employer. The instruction does