Principal Enterprise Data Architect
Johnson Health Tech North America · Cottage Grove, WI · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections for headings where content exists. Use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: "Who We Are" maybe corresponds to About the role? Actually "Who We Are" is company overview; could be About the role? The instruction: use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: "Who We Are" maybe corresponds to About the role? Actually "Who We Are" is company overview; could be About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map sections accordingly.
We have:
- Description: includes "Who We Are" and "Mission Statement" and "Position Overview". That could be "About the role" or maybe "About the company". We'll treat as About the role (or maybe "About the role" includes position overview). We'll put that content under About the role
with paragraphs.
- Responsibilities: we have a list of responsibilities with subheadings (Enterprise Data Architecture, Data Engineering and Integration, etc). We need to output a - for any list of duties/requirements/benefits. So we can create a
with each responsibility as - . Should we keep subheadings inside li? Probably just plain text.
- Requirements: includes Education, Experience, Other Requirements. Also Bonus Qualifications. Those are requirements/qualifications. We can split into Requirements and Qualifications sections. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need separate sections for Requirements and Qualifications. We'll put Education, Experience, Other Requirements under Requirements. Bonus Qualifications under Qualifications.
- Skills: maybe we can extract skills from Other Requirements: Expert-level SQL, advanced Python, Databricks, Spark, etc. Could be a Skills section. But we already have those in Requirements/Other Requirements. Could create a Skills section listing those. However instruction: prefer a few substantive sections over many thin ones. Might combine skills into Requirements or Qualifications. But we have a separate Qualifications for bonus qualifications. Could make Skills section for technical skills (SQL, Python, Databricks, Spark, etc). Let's see: The posting includes "Other Requirements Expert-level SQL skills and advanced proficiency in Python for data engineering, automation, integration, platform development, and ETL/ELT pipelines for large and complex enterprise data sets. Deep experience with Databricks, Apache Spark, Delta Lake, lakehouse architecture, data modeling, data warehousing, dimensional design, data lakes, and analytical data structures. Experience integrating ERP, CRM, e-commerce, manufacturing, financial, logistics, or other enterprise applications, including SAP, Microsoft Dynamics CRM, APIs, file-transfer methods, database connectivity, message-based integration, and cloud data-integration patterns. Experience with source control, automated deployment, testing, monitoring, modern software development practices, documentation, and repeatable technical standards."
That's a list of skills/experience. Could be placed under Requirements or Skills. Since we have a Skills heading allowed, we could put those bullet points under Skills. Then Requirements could be Education and Experience. Qualifications could be Bonus Qualifications.
We also have Benefits & Perks: list of benefits. So Benefits section.
Pay and Schedule: not mentioned, so omit.
We must not include boilerplate like EEO, etc. Remove "Equal Opportunity Employer..." line.
Also remove "Physical Requirements/Work Environment" maybe? That's not a heading we have; but it's substantive? It's about physical requirements. Not in allowed headings; but we could drop it as not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical Requirements is not boilerplate but not in allowed headings; we could either drop or include as a paragraph under maybe a generic section? Since only allowed headings are specified, we should not create other headings. Could we include it as a paragraph under Responsibilities? No. Better to drop it as not required. The instruction: "Prefer a few substantive sections over many thin ones." So we can drop physical requirements.
Thus sections:
- About the role (h3) containing paragraphs: Who We Are, Mission Statement, Position Overview.
- Responsibilities (h3) containing ul li list of each responsibility bullet (maybe combine subpoints).
- Requirements (h3) containing ul li for Education, Experience, Other Requirements? Actually Other Requirements is more skills; we moved to Skills. So Requirements: Education, Experience.
- Skills (h3) containing ul li for technical skills list.
- Qualifications (h3) containing ul li for Bonus Qualifications.
- Benefits (h3) containing ul li for benefits list.
Make sure to preserve all substantive information. Let's extract details.
Who We Are: "Johnson Health Tech is one of the world’s largest and fastest-growing fitness equipment manufacturers, delivering innovative solutions that help people live healthier lives. Through our award-winning portfolio of commercial and residential brands, we serve customers in more than 60 countries worldwide."
Mission Statement: "To delight and excite our customers through truly innovative products, unsurpassed quality, and best-in-class customer experience provided by a world-class organization."
Position Overview: "The Principal Enterprise Data Architect is the senior technical leader responsible for the architecture, design, implementation, and continued evolution of Johnson Health Tech’s global enterprise data environment. This role leads the technical design of the company’s Databricks-based data platform, including integration, transformation, governance, and delivery of data from SAP, Microsoft Dynamics CRM, e-commerce, operational, third-party, and other enterprise data sources. This senior individual contributor role establishes the patterns and technical standards through which data moves across the organization, translating complex business and technology requirements into scalable, maintainable solutions while partnering with global IT, data engineering, analytics, infrastructure, security, application, and business teams."
Now Responsibilities list: We have headings with descriptions. Let's capture each bullet:
- Enterprise Data Architecture: "Define and maintain the technical architecture for Johnson Health Tech’s global enterprise data environment, including the Databricks lakehouse platform and supporting cloud, integration, and data-processing components. Establish scalable architectural patterns and ensure architecture decisions support performance, scalability, reliability, security, maintainability, cost effectiveness, and appropriate emerging technology improvements."
- Data Engineering and Integration: "Lead the technical design and implementation of ETL and ELT pipelines connecting SAP, Microsoft Dynamics CRM, e-commerce systems, operational applications, external platforms, and other enterprise data sources. Establish reusable integration frameworks, ingestion patterns, and data-processing standards using SQL, Python, Databricks, Spark, APIs, and other integration technologies, and resolve data-platform performance, scalability, and reliability issues."
- Data Modeling and Platform Design: "Define enterprise data-modeling standards across raw, curated, analytical, and consumption-ready data layers. Design data structures that support reporting, analytics, data science, artificial intelligence, operational applications, and business planning, while promoting modular, reusable, testable, and consistent data-engineering practices."
- Technical Leadership and Standards: "Serve as the senior technical authority for enterprise data architecture and data engineering. Establish and document architecture principles, development standards, naming conventions, integration patterns, and technical guardrails while providing guidance for complex data initiatives and critical platform components."
- Global Enablement and Knowledge Transfer: "Develop technical frameworks, documentation, reference architectures, and training materials required for global adoption of the data platform. Train and mentor regional technology teams to implement, operate, and extend the enterprise data environment within established architectural standards and local requirements."
- Data Quality, Governance, Security, and Reliability: "Incorporate data quality, lineage, observability, reconciliation, error handling, monitoring, and platform-performance requirements into platform and pipeline designs. Partner with data governance, cybersecurity, infrastructure, and application teams to ensure appropriate access controls, protection of sensitive data, and compliance with applicable privacy, security, retention, deployment, testing, release-management, disaster recovery, and business continuity requirements."
- Collaboration and Enterprise Influence: "Collaborate with enterprise application teams responsible for SAP, Dynamics CRM, e-commerce, manufacturing, logistics, finance, product, customer, and other operational systems, translating business requirements into actionable technical designs. Communicate complex technical decisions clearly, identify architectural risks and dependencies, influence technical decisions across teams, and partner with external vendors while maintaining ownership of the company’s architecture and technical standards."
- Marginal Job Functions: "Other projects as needed."
We'll include all as li.
Now Requirements:
Education: "Bachelor’s degree in computer science, information systems, engineering, data management, or related field, or equivalent professional experience. Master’s degree is preferred."
Experience: "At least 15 years of progressive experience in data architecture, data engineering, enterprise integration, software engineering, or related technical disciplines. Extensive experience designing and implementing enterprise-scale data platforms. Demonstrated experience serving as a senior architect, principal engineer, technical lead, or equivalent enterprise technical authority."
We could also include "Other Requirements" but we moved to Skills.
Now Skills: list from Other Requirements:
- Expert-level SQL skills
- Advanced proficiency in Python for data engineering, automation, integration, platform development, and ETL/ELT pipelines for large and complex enterprise data sets.
- Deep experience with Databricks, Apache Spark, Delta Lake, lakehouse architecture, data modeling, data warehousing, dimensional design, data lakes, and analytical data structures.
- Experience integrating ERP, CRM, e-commerce, manufacturing, financial, logistics, or other enterprise applications, including SAP, Microsoft Dynamics CRM, APIs, file-transfer methods, database connectivity, message-based integration, and cloud data-integration patterns.
- Experience with source control, automated deployment, testing, monitoring, modern software development practices, documentation, and repeatable technical standards.
We could break each into separate li.
Now Qualifications (Bonus Qualifications):
- Experience with Microsoft Azure, Amazon Web Services, hybrid cloud environments, Databricks Unity Catalog, governance, security, lineage, orchestration, and platform administration.
- Experience with Power BI, Tableau, data-product, data-mesh, domain-oriented, or federated data-architecture concepts.
- Experience with change data capture, event streaming, message queues, real-time data processing, DevOps, DataOps practices, and global enterprise environments with multinational deployment requirements.
Now Benefits:
- Medical, dental, and vision insurance
- Company-paid life insurance and AD&D coverage
- 401(k) retirement savings plan
- Paid time off (PTO)
- FSA and HSA options
- Employee product discounts, wellness resources, and employee assistance programs
Now output HTML fragment: use
headings,
for prose,
- for lists.
We need to ensure we don't repeat job title as heading. Not using.
We'll output:
About the role
Who We Are: Johnson Health Tech is one of the world’s largest and fastest-growing fitness equipment manufacturers, delivering innovative solutions that help people live healthier lives. Through our award-winning portfolio of commercial and residential brands, we serve customers in more than 60 countries worldwide.
Mission Statement: To delight and excite our customers through truly innovative products, unsurpassed quality, and best-in-class customer experience provided by a world-class organization.
Position Overview: The Principal Enterprise Data Architect is the senior technical leader responsible for the architecture, design, implementation, and continued evolution of Johnson Health Tech’s global enterprise data environment. This role leads the technical design of the company’s Databricks-based data platform, including integration, transformation, governance, and delivery of data from SAP, Microsoft Dynamics CRM, e-commerce, operational, third-party, and other enterprise data sources. This senior individual contributor role establishes the patterns and technical standards through which data moves across the organization, translating complex business and technology requirements into scalable, maintainable solutions while partnering with global IT, data engineering, analytics, infrastructure, security, application, and business teams.
Responsibilities
- Enterprise Data Architecture: Define and maintain the technical architecture for Johnson Health Tech’s global enterprise data environment, including the Databricks lakehouse platform and supporting cloud, integration, and data-processing components. Establish scalable architectural patterns and ensure architecture decisions support performance, scalability, reliability, security, maintainability, cost effectiveness,
About the role
with paragraphs. - Responsibilities: we have a list of responsibilities with subheadings (Enterprise Data Architecture, Data Engineering and Integration, etc). We need to output a- for any list of duties/requirements/benefits. So we can create a
- with each responsibility as
- . Should we keep subheadings inside li? Probably just plain text.
- Requirements: includes Education, Experience, Other Requirements. Also Bonus Qualifications. Those are requirements/qualifications. We can split into Requirements and Qualifications sections. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need separate sections for Requirements and Qualifications. We'll put Education, Experience, Other Requirements under Requirements. Bonus Qualifications under Qualifications.
- Skills: maybe we can extract skills from Other Requirements: Expert-level SQL, advanced Python, Databricks, Spark, etc. Could be a Skills section. But we already have those in Requirements/Other Requirements. Could create a Skills section listing those. However instruction: prefer a few substantive sections over many thin ones. Might combine skills into Requirements or Qualifications. But we have a separate Qualifications for bonus qualifications. Could make Skills section for technical skills (SQL, Python, Databricks, Spark, etc). Let's see: The posting includes "Other Requirements Expert-level SQL skills and advanced proficiency in Python for data engineering, automation, integration, platform development, and ETL/ELT pipelines for large and complex enterprise data sets. Deep experience with Databricks, Apache Spark, Delta Lake, lakehouse architecture, data modeling, data warehousing, dimensional design, data lakes, and analytical data structures. Experience integrating ERP, CRM, e-commerce, manufacturing, financial, logistics, or other enterprise applications, including SAP, Microsoft Dynamics CRM, APIs, file-transfer methods, database connectivity, message-based integration, and cloud data-integration patterns. Experience with source control, automated deployment, testing, monitoring, modern software development practices, documentation, and repeatable technical standards."
That's a list of skills/experience. Could be placed under Requirements or Skills. Since we have a Skills heading allowed, we could put those bullet points under Skills. Then Requirements could be Education and Experience. Qualifications could be Bonus Qualifications.
We also have Benefits & Perks: list of benefits. So Benefits section.
Pay and Schedule: not mentioned, so omit.
We must not include boilerplate like EEO, etc. Remove "Equal Opportunity Employer..." line.
Also remove "Physical Requirements/Work Environment" maybe? That's not a heading we have; but it's substantive? It's about physical requirements. Not in allowed headings; but we could drop it as not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical Requirements is not boilerplate but not in allowed headings; we could either drop or include as a paragraph under maybe a generic section? Since only allowed headings are specified, we should not create other headings. Could we include it as a paragraph under Responsibilities? No. Better to drop it as not required. The instruction: "Prefer a few substantive sections over many thin ones." So we can drop physical requirements.
Thus sections:
- About the role (h3) containing paragraphs: Who We Are, Mission Statement, Position Overview.
- Responsibilities (h3) containing ul li list of each responsibility bullet (maybe combine subpoints).
- Requirements (h3) containing ul li for Education, Experience, Other Requirements? Actually Other Requirements is more skills; we moved to Skills. So Requirements: Education, Experience.
- Skills (h3) containing ul li for technical skills list.
- Qualifications (h3) containing ul li for Bonus Qualifications.
- Benefits (h3) containing ul li for benefits list.
Make sure to preserve all substantive information. Let's extract details.
Who We Are: "Johnson Health Tech is one of the world’s largest and fastest-growing fitness equipment manufacturers, delivering innovative solutions that help people live healthier lives. Through our award-winning portfolio of commercial and residential brands, we serve customers in more than 60 countries worldwide."
Mission Statement: "To delight and excite our customers through truly innovative products, unsurpassed quality, and best-in-class customer experience provided by a world-class organization."
Position Overview: "The Principal Enterprise Data Architect is the senior technical leader responsible for the architecture, design, implementation, and continued evolution of Johnson Health Tech’s global enterprise data environment. This role leads the technical design of the company’s Databricks-based data platform, including integration, transformation, governance, and delivery of data from SAP, Microsoft Dynamics CRM, e-commerce, operational, third-party, and other enterprise data sources. This senior individual contributor role establishes the patterns and technical standards through which data moves across the organization, translating complex business and technology requirements into scalable, maintainable solutions while partnering with global IT, data engineering, analytics, infrastructure, security, application, and business teams."
Now Responsibilities list: We have headings with descriptions. Let's capture each bullet:
- Enterprise Data Architecture: "Define and maintain the technical architecture for Johnson Health Tech’s global enterprise data environment, including the Databricks lakehouse platform and supporting cloud, integration, and data-processing components. Establish scalable architectural patterns and ensure architecture decisions support performance, scalability, reliability, security, maintainability, cost effectiveness, and appropriate emerging technology improvements."
- Data Engineering and Integration: "Lead the technical design and implementation of ETL and ELT pipelines connecting SAP, Microsoft Dynamics CRM, e-commerce systems, operational applications, external platforms, and other enterprise data sources. Establish reusable integration frameworks, ingestion patterns, and data-processing standards using SQL, Python, Databricks, Spark, APIs, and other integration technologies, and resolve data-platform performance, scalability, and reliability issues."
- Data Modeling and Platform Design: "Define enterprise data-modeling standards across raw, curated, analytical, and consumption-ready data layers. Design data structures that support reporting, analytics, data science, artificial intelligence, operational applications, and business planning, while promoting modular, reusable, testable, and consistent data-engineering practices."
- Technical Leadership and Standards: "Serve as the senior technical authority for enterprise data architecture and data engineering. Establish and document architecture principles, development standards, naming conventions, integration patterns, and technical guardrails while providing guidance for complex data initiatives and critical platform components."
- Global Enablement and Knowledge Transfer: "Develop technical frameworks, documentation, reference architectures, and training materials required for global adoption of the data platform. Train and mentor regional technology teams to implement, operate, and extend the enterprise data environment within established architectural standards and local requirements."
- Data Quality, Governance, Security, and Reliability: "Incorporate data quality, lineage, observability, reconciliation, error handling, monitoring, and platform-performance requirements into platform and pipeline designs. Partner with data governance, cybersecurity, infrastructure, and application teams to ensure appropriate access controls, protection of sensitive data, and compliance with applicable privacy, security, retention, deployment, testing, release-management, disaster recovery, and business continuity requirements."
- Collaboration and Enterprise Influence: "Collaborate with enterprise application teams responsible for SAP, Dynamics CRM, e-commerce, manufacturing, logistics, finance, product, customer, and other operational systems, translating business requirements into actionable technical designs. Communicate complex technical decisions clearly, identify architectural risks and dependencies, influence technical decisions across teams, and partner with external vendors while maintaining ownership of the company’s architecture and technical standards."
- Marginal Job Functions: "Other projects as needed."
We'll include all as li.
Now Requirements:
Education: "Bachelor’s degree in computer science, information systems, engineering, data management, or related field, or equivalent professional experience. Master’s degree is preferred."
Experience: "At least 15 years of progressive experience in data architecture, data engineering, enterprise integration, software engineering, or related technical disciplines. Extensive experience designing and implementing enterprise-scale data platforms. Demonstrated experience serving as a senior architect, principal engineer, technical lead, or equivalent enterprise technical authority."
We could also include "Other Requirements" but we moved to Skills.
Now Skills: list from Other Requirements:
- Expert-level SQL skills
- Advanced proficiency in Python for data engineering, automation, integration, platform development, and ETL/ELT pipelines for large and complex enterprise data sets.
- Deep experience with Databricks, Apache Spark, Delta Lake, lakehouse architecture, data modeling, data warehousing, dimensional design, data lakes, and analytical data structures.
- Experience integrating ERP, CRM, e-commerce, manufacturing, financial, logistics, or other enterprise applications, including SAP, Microsoft Dynamics CRM, APIs, file-transfer methods, database connectivity, message-based integration, and cloud data-integration patterns.
- Experience with source control, automated deployment, testing, monitoring, modern software development practices, documentation, and repeatable technical standards.
We could break each into separate li.
Now Qualifications (Bonus Qualifications):
- Experience with Microsoft Azure, Amazon Web Services, hybrid cloud environments, Databricks Unity Catalog, governance, security, lineage, orchestration, and platform administration.
- Experience with Power BI, Tableau, data-product, data-mesh, domain-oriented, or federated data-architecture concepts.
- Experience with change data capture, event streaming, message queues, real-time data processing, DevOps, DataOps practices, and global enterprise environments with multinational deployment requirements.
Now Benefits:
- Medical, dental, and vision insurance
- Company-paid life insurance and AD&D coverage
- 401(k) retirement savings plan
- Paid time off (PTO)
- FSA and HSA options
- Employee product discounts, wellness resources, and employee assistance programs
Now output HTML fragment: use
headings,
for prose,
- for lists.
We need to ensure we don't repeat job title as heading. Not using.
We'll output:
About the role
Who We Are: Johnson Health Tech is one of the world’s largest and fastest-growing fitness equipment manufacturers, delivering innovative solutions that help people live healthier lives. Through our award-winning portfolio of commercial and residential brands, we serve customers in more than 60 countries worldwide.
Mission Statement: To delight and excite our customers through truly innovative products, unsurpassed quality, and best-in-class customer experience provided by a world-class organization.
Position Overview: The Principal Enterprise Data Architect is the senior technical leader responsible for the architecture, design, implementation, and continued evolution of Johnson Health Tech’s global enterprise data environment. This role leads the technical design of the company’s Databricks-based data platform, including integration, transformation, governance, and delivery of data from SAP, Microsoft Dynamics CRM, e-commerce, operational, third-party, and other enterprise data sources. This senior individual contributor role establishes the patterns and technical standards through which data moves across the organization, translating complex business and technology requirements into scalable, maintainable solutions while partnering with global IT, data engineering, analytics, infrastructure, security, application, and business teams.
Responsibilities
- Enterprise Data Architecture: Define and maintain the technical architecture for Johnson Health Tech’s global enterprise data environment, including the Databricks lakehouse platform and supporting cloud, integration, and data-processing components. Establish scalable architectural patterns and ensure architecture decisions support performance, scalability, reliability, security, maintainability, cost effectiveness,
- for lists.
We need to ensure we don't repeat job title as heading. Not using.
We'll output:
- . Should we keep subheadings inside li? Probably just plain text.
- Requirements: includes Education, Experience, Other Requirements. Also Bonus Qualifications. Those are requirements/qualifications. We can split into Requirements and Qualifications sections. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need separate sections for Requirements and Qualifications. We'll put Education, Experience, Other Requirements under Requirements. Bonus Qualifications under Qualifications.
- Skills: maybe we can extract skills from Other Requirements: Expert-level SQL, advanced Python, Databricks, Spark, etc. Could be a Skills section. But we already have those in Requirements/Other Requirements. Could create a Skills section listing those. However instruction: prefer a few substantive sections over many thin ones. Might combine skills into Requirements or Qualifications. But we have a separate Qualifications for bonus qualifications. Could make Skills section for technical skills (SQL, Python, Databricks, Spark, etc). Let's see: The posting includes "Other Requirements Expert-level SQL skills and advanced proficiency in Python for data engineering, automation, integration, platform development, and ETL/ELT pipelines for large and complex enterprise data sets. Deep experience with Databricks, Apache Spark, Delta Lake, lakehouse architecture, data modeling, data warehousing, dimensional design, data lakes, and analytical data structures. Experience integrating ERP, CRM, e-commerce, manufacturing, financial, logistics, or other enterprise applications, including SAP, Microsoft Dynamics CRM, APIs, file-transfer methods, database connectivity, message-based integration, and cloud data-integration patterns. Experience with source control, automated deployment, testing, monitoring, modern software development practices, documentation, and repeatable technical standards."
That's a list of skills/experience. Could be placed under Requirements or Skills. Since we have a Skills heading allowed, we could put those bullet points under Skills. Then Requirements could be Education and Experience. Qualifications could be Bonus Qualifications.
We also have Benefits & Perks: list of benefits. So Benefits section.
Pay and Schedule: not mentioned, so omit.
We must not include boilerplate like EEO, etc. Remove "Equal Opportunity Employer..." line.
Also remove "Physical Requirements/Work Environment" maybe? That's not a heading we have; but it's substantive? It's about physical requirements. Not in allowed headings; but we could drop it as not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical Requirements is not boilerplate but not in allowed headings; we could either drop or include as a paragraph under maybe a generic section? Since only allowed headings are specified, we should not create other headings. Could we include it as a paragraph under Responsibilities? No. Better to drop it as not required. The instruction: "Prefer a few substantive sections over many thin ones." So we can drop physical requirements.
Thus sections:
- About the role (h3) containing paragraphs: Who We Are, Mission Statement, Position Overview.
- Responsibilities (h3) containing ul li list of each responsibility bullet (maybe combine subpoints).
- Requirements (h3) containing ul li for Education, Experience, Other Requirements? Actually Other Requirements is more skills; we moved to Skills. So Requirements: Education, Experience.
- Skills (h3) containing ul li for technical skills list.
- Qualifications (h3) containing ul li for Bonus Qualifications.
- Benefits (h3) containing ul li for benefits list.
Make sure to preserve all substantive information. Let's extract details.
Who We Are: "Johnson Health Tech is one of the world’s largest and fastest-growing fitness equipment manufacturers, delivering innovative solutions that help people live healthier lives. Through our award-winning portfolio of commercial and residential brands, we serve customers in more than 60 countries worldwide."
Mission Statement: "To delight and excite our customers through truly innovative products, unsurpassed quality, and best-in-class customer experience provided by a world-class organization."
Position Overview: "The Principal Enterprise Data Architect is the senior technical leader responsible for the architecture, design, implementation, and continued evolution of Johnson Health Tech’s global enterprise data environment. This role leads the technical design of the company’s Databricks-based data platform, including integration, transformation, governance, and delivery of data from SAP, Microsoft Dynamics CRM, e-commerce, operational, third-party, and other enterprise data sources. This senior individual contributor role establishes the patterns and technical standards through which data moves across the organization, translating complex business and technology requirements into scalable, maintainable solutions while partnering with global IT, data engineering, analytics, infrastructure, security, application, and business teams."
Now Responsibilities list: We have headings with descriptions. Let's capture each bullet:
- Enterprise Data Architecture: "Define and maintain the technical architecture for Johnson Health Tech’s global enterprise data environment, including the Databricks lakehouse platform and supporting cloud, integration, and data-processing components. Establish scalable architectural patterns and ensure architecture decisions support performance, scalability, reliability, security, maintainability, cost effectiveness, and appropriate emerging technology improvements."
- Data Engineering and Integration: "Lead the technical design and implementation of ETL and ELT pipelines connecting SAP, Microsoft Dynamics CRM, e-commerce systems, operational applications, external platforms, and other enterprise data sources. Establish reusable integration frameworks, ingestion patterns, and data-processing standards using SQL, Python, Databricks, Spark, APIs, and other integration technologies, and resolve data-platform performance, scalability, and reliability issues."
- Data Modeling and Platform Design: "Define enterprise data-modeling standards across raw, curated, analytical, and consumption-ready data layers. Design data structures that support reporting, analytics, data science, artificial intelligence, operational applications, and business planning, while promoting modular, reusable, testable, and consistent data-engineering practices."
- Technical Leadership and Standards: "Serve as the senior technical authority for enterprise data architecture and data engineering. Establish and document architecture principles, development standards, naming conventions, integration patterns, and technical guardrails while providing guidance for complex data initiatives and critical platform components."
- Global Enablement and Knowledge Transfer: "Develop technical frameworks, documentation, reference architectures, and training materials required for global adoption of the data platform. Train and mentor regional technology teams to implement, operate, and extend the enterprise data environment within established architectural standards and local requirements."
- Data Quality, Governance, Security, and Reliability: "Incorporate data quality, lineage, observability, reconciliation, error handling, monitoring, and platform-performance requirements into platform and pipeline designs. Partner with data governance, cybersecurity, infrastructure, and application teams to ensure appropriate access controls, protection of sensitive data, and compliance with applicable privacy, security, retention, deployment, testing, release-management, disaster recovery, and business continuity requirements."
- Collaboration and Enterprise Influence: "Collaborate with enterprise application teams responsible for SAP, Dynamics CRM, e-commerce, manufacturing, logistics, finance, product, customer, and other operational systems, translating business requirements into actionable technical designs. Communicate complex technical decisions clearly, identify architectural risks and dependencies, influence technical decisions across teams, and partner with external vendors while maintaining ownership of the company’s architecture and technical standards."
- Marginal Job Functions: "Other projects as needed."
We'll include all as li.
Now Requirements:
Education: "Bachelor’s degree in computer science, information systems, engineering, data management, or related field, or equivalent professional experience. Master’s degree is preferred."
Experience: "At least 15 years of progressive experience in data architecture, data engineering, enterprise integration, software engineering, or related technical disciplines. Extensive experience designing and implementing enterprise-scale data platforms. Demonstrated experience serving as a senior architect, principal engineer, technical lead, or equivalent enterprise technical authority."
We could also include "Other Requirements" but we moved to Skills.
Now Skills: list from Other Requirements:
- Expert-level SQL skills
- Advanced proficiency in Python for data engineering, automation, integration, platform development, and ETL/ELT pipelines for large and complex enterprise data sets.
- Deep experience with Databricks, Apache Spark, Delta Lake, lakehouse architecture, data modeling, data warehousing, dimensional design, data lakes, and analytical data structures.
- Experience integrating ERP, CRM, e-commerce, manufacturing, financial, logistics, or other enterprise applications, including SAP, Microsoft Dynamics CRM, APIs, file-transfer methods, database connectivity, message-based integration, and cloud data-integration patterns.
- Experience with source control, automated deployment, testing, monitoring, modern software development practices, documentation, and repeatable technical standards.
We could break each into separate li.
Now Qualifications (Bonus Qualifications):
- Experience with Microsoft Azure, Amazon Web Services, hybrid cloud environments, Databricks Unity Catalog, governance, security, lineage, orchestration, and platform administration.
- Experience with Power BI, Tableau, data-product, data-mesh, domain-oriented, or federated data-architecture concepts.
- Experience with change data capture, event streaming, message queues, real-time data processing, DevOps, DataOps practices, and global enterprise environments with multinational deployment requirements.
Now Benefits:
- Medical, dental, and vision insurance
- Company-paid life insurance and AD&D coverage
- 401(k) retirement savings plan
- Paid time off (PTO)
- FSA and HSA options
- Employee product discounts, wellness resources, and employee assistance programs
Now output HTML fragment: use