Data Analytics Engineer / Architect

We need to output HTML fragment with sections: headings

for each section that has content. Use

• for lists. Use

  for prose. No job title heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Keep substantive info. We need to parse the posting. Let's extract sections: - About the role? The intro: "Infopro Digital, the B2B group specialising in information and technology, is currently looking for a Data Analytics Engineer / Architect on a permanent contract to strengthen the team at Business Unit Automotive in Nashville, TN. Infopro Digital Automotive develops digital tools and software dedicated to the performance of decision-makers in the various sectors of the automotive aftermarket industry. Services benefit various automotive stakeholders, such as car manufacturers, aftermarket parts producers, distributors, and workshops. Further brands include ETAI, Eucon, HaynesPro, OATS, Inovaxo, Autronica, ETAI Ibérica, IsiCondal, Carooline, Haynes, DriveRightData, GiPA and Aurelis. Join Infopro Digital and become a Key Player in our Team! With exciting job opportunities worldwide, Infopro Digital opens up a vast universe of professional challenges. Joining our group means plunging into the heart of stimulating collaborations within multidisciplinary teams." That's about the company and role. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "The challenge awaiting you: As a Data Analytics Engineer / Architect (m/f/d), you will play a key role in shaping scalable data models and transformation pipelines, enabling reliable business insights and advanced analytics through high-quality, well-structured data. You'll be contributing to a variety of projects, while developing your skills and reaching new levels of expertise." That could be part of About the role. Then "The tasks awaiting you: You will be responsible for :" then list bullet points. Thus Responsibilities section: list of duties. Then "Our data stack: Snowflake, Databricks, Microsoft Azure dbt, SQL, Python Dimensional modeling, Data Vault 2.0, Anchor Modeling Semantic layers, Power BI, product-facing APIs Git, Azure DevOps, YAML, code reviews Data testing frameworks, cataloging and lineage, Claude Code" That's maybe Skills or Requirements? Actually it's describing tech stack; could be under Skills or Requirements. Then "Requirements Hands-on expertise in Snowflake and its data modeling capabilities for defining business entities, KPIs, and building semantic layers for BI and advanced analytics use cases. Additional experience in Databricks is a plus Advanced SQL expertise with a strong focus on transformations and query performance, combined with hands-on experience in dbt (models, tests, macros, and project structure), and a deep understanding of data modeling concepts such as dimensional modeling as well as Data Vault 2.0 and Anchor Modeling (or a strong willingness to learn both) You collaborate effectively with business stakeholders and translate requirements into scalable data models, while maintaining high standards for data quality, harmonization, and single-source-of-truth principles within Git-based development workflows You communicate fluently in English with international colleagues and stakeholders in the US and Europe You would stand out with additional knowledge in Power BI (from a consumption perspective), experience with data testing frameworks (e.g., Great Expectations, DQX, Soda), familiarity with data cataloging and lineage tracking, as well as an understanding of feature engineering concepts for future ML use cases" That's Requirements (and maybe Qualifications). We'll treat as Requirements. Then Benefits section: list of benefits. Then "Our foundations and values: ..." maybe could be About the company or Culture. Not a required heading; we could include as About the company? But instruction says only include sections when posting has real specific content. Could include "About the company" but not in list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put the values under About the role? Might be better to include as a separate section like "About the company" but not in allowed list; maybe we should not create extra headings beyond those. However we could incorporate that content into About the role or maybe omit if not fitting. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not strict limited list. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create other headings if needed, but better to stick to those examples. The "Our foundations and values" is substantive; we could put under "About the role" or maybe "About the company". Since not in examples, maybe we can incorporate into About the role. Also there is "Who are we?" paragraph about Infopro Digital. That's also about company. Could be part of About the role. Thus we can have sections: About the role, Responsibilities, Requirements, Skills (maybe from data stack), Benefits. We need to avoid Pay and Schedule as not present. Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details like number of vacation days, etc. We need to format lists with

  • . For prose use

    . We need to drop boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some EEO lines: "Diversity is one of our core values... The Group is committed to a policy of equal opportunities and inclusion..." That's EEO boilerplate; we should remove it. Also "Who are we?" maybe not boilerplate but substantive; keep. Also "Infopro Digital is Proud to Announce its 2024 Great Place To Work Certification™" etc. That's substantive about certification; keep. Now let's craft HTML. We'll start with

    About the role

    then

    containing the intro paragraphs about the role, company, challenge, etc. Need to ensure we keep all details: mention permanent contract, Nashville, TN, Business Unit Automotive, description of Infopro Digital Automotive, brands list, join statement, exciting opportunities worldwide, multidisciplinary teams, challenge awaiting you (shaping scalable data models etc), contributing to variety of projects, developing skills. We need to be careful not to include duplicated lines. The intro includes some repeated phrases? We'll just include once. Now Responsibilities:

    Responsibilities

    then
    • each bullet. The bullet list after "The tasks awaiting you: You will be responsible for :" includes: - Design, build, and optimize scalable data transformation pipelines with a strong focus on SQL performance and efficiency, while maintaining robust dbt projects including models, tests, macros, and structured project setups - Develop and evolve data models using dimensional modeling principles (e.g., star schemas) as well as Data Vault 2.0 and Anchor Modeling approaches in a combined modeling environment - Define, standardize, and maintain business entities, KPIs, and metric logic as reusable assets, and provide semantic layers consumable by BI tools and machine learning use cases - Work closely with business stakeholders to translate requirements into scalable data models, ensuring alignment, data consistency, and a single-source-of-truth approach - Leverage modern data platforms such as Snowflake and/or Databricks and contribute to collaborative, Git-based development workflows including code reviews and best practices We'll keep exactly. Now Skills: maybe we can have a section "Skills" for the data stack and technical proficiencies. The "Our data stack:" list includes many items. We'll turn into
      • . Also we might include "Requirements" separate. But the posting also has a "Requirements" section with detailed requirements. We'll treat that as Requirements. Thus we need sections: About the role, Responsibilities, Requirements, Skills, Benefits. Now Requirements: we need to capture all bullet-like sentences. The text after "Requirements" is a paragraph with multiple sentences. We could break into
        • for each distinct requirement. Let's parse: - Hands-on expertise in Snowflake and its data modeling capabilities for defining business entities, KPIs, and building semantic layers for BI and advanced analytics use cases. - Additional experience in Databricks is a plus - Advanced SQL expertise with a strong focus on transformations and query performance, combined with hands-on experience in dbt (models, tests, macros, and project structure), and a deep understanding of data modeling concepts such as dimensional modeling as well as Data Vault 2.0 and Anchor Modeling (or a strong willingness to learn both) - You collaborate effectively with business stakeholders and translate requirements into scalable data models, while maintaining high standards for data quality, harmonization, and single-source-of-truth principles within Git-based development workflows - You communicate fluently in English with international colleagues and stakeholders in the US and Europe - You would stand out with additional knowledge in Power BI (from a consumption perspective), experience with data testing frameworks (e.g., Great Expectations, DQX, Soda), familiarity with data cataloging and lineage tracking, as well as an understanding of feature engineering concepts for future ML use cases We'll make each a
        • . Now Skills: The "Our data stack:" list includes: - Snowflake, Databricks, Microsoft Azure - dbt, SQL, Python - Dimensional modeling, Data Vault 2.0, Anchor Modeling - Semantic layers, Power BI, product-facing APIs - Git, Azure DevOps, YAML, code reviews - Data testing frameworks, cataloging and lineage, Claude Code We could group logically but just list each item as
        • . Might be long but okay. Now Benefits: list: - 20 vacation days (rising to 25 days) - 5 paid sick days - 11 paid company holidays - Medical, dental & vision insurance (including life insurance) - 401(k) plan plus match - Flexible Spending Account (FSA) - Short-term and long-term disability - Employee Assistance Program - Flexible working - Office gym membership - Employee referral scheme We'll list each as
        • . Now also include the "Our foundations and values" and "Who are we?" and Great Place To Work certification. We could incorporate into About the role after the initial paragraphs. Let's add a paragraph after the challenge description that includes: "Our foundations and values: At Infopro Digital, we are driven by core values such as entrepreneurial spirit, constant customer focus, promoting diversity, striving for significant impact, and a collaborative culture. By joining us, you become part of a dynamic community that embraces these values on a daily basis, shaping the future with passion and commitment. Diversity is one of our core values. We are convinced that our teams, drawn from all backgrounds and with different backgrounds and experiences, are one of the key drivers of our success. The Group is committed to a policy of equal opportunities and inclusion, from recruitment to career development, and we strive to provide an equitable working environment to promote the well-being of our teams." But we need to remove EEO boilerplate. The sentence about equal opportunities and inclusion is EEO; we should remove that. Also "Diversity is one of our core values" is okay but might be considered values. We'll keep the values part but remove the EEO commitment sentence. Also remove "Who are we?" paragraph? That is substantive about company; we can keep. Let's extract "Who are we?" paragraph: "Infopro Digital is a B2B group specializing in information and technology. The group is present in 26 countries and employs over 4,000 people. Its innovative solutions are aimed at professional communities in 5 key economic sectors: construction & public sector, automotive, risk & insurance, industry and retail. Thanks to the group's sectorial expertise, Infopro Digital covers all the