Senior Data Engineer

We need to output HTML fragment with sections: About the role? The posting includes intro about company, then responsibilities, profile, what we offer, why join us? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include: About the role (maybe the intro about Ekimetrics and role?), Responsibilities (the bullet list), Requirements/Qualifications/Skills (the profile), Benefits (what we offer includes benefits, salary range, PTO, etc.), Pay (salary range), Schedule (maybe hybrid work environment). The posting includes salary range: "A reasonable estimate of the base salary for our NYC office is between $125,000 and $140,000." That's pay info. Benefits: "comprehensive benefits package, generous bonus package, dynamic promotions and salary structure. The Eki.Academy training catalog... Dynamic environment... Close-knit team... Client exposure... Modern office... Emphasis on work-life-balance and 20 days of PTO with 11 annual holidays in a flexible hybrid work environment Opportunities for international mobility..." So we can include Benefits and Pay sections. Schedule: "flexible hybrid work environment" maybe schedule info. Could include Schedule section. We must not create sections with filler. So we need to ensure each heading has substantive content. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to avoid repeating job title as heading. The job title is Senior Data Engineer; we should not put that as heading. We need to strip boilerplate: EEO statements, visa sponsorship note, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's extract content. Intro paragraph: "Ekimetrics is a global leader in Marketing & Commercial effectiveness and AI-powered solutions. Since 2006, we’ve been helping businesses optimize marketing and operations by combining AI with business and tech expertise across 4 domains: Marketing & commercial effectiveness, Customer analytics, Operational excellence, ESG & sustainability. With a full in-house team and offices in Paris, London, New York, Hong Kong, and Shanghai, we deliver tailor-made solutions that turn data into real positive impact, leveraging our unique combination of technology and services. We excel at delivering AI impact at scale. Our mission is to harness this power to tackle the world’s most urgent issues. We commit to responsibility and frugality in AI, systematic AI impact at scale, and loyalty to our values and DNA." That's about the company; could be "About the role" or maybe "About Ekimetrics". The instruction says use headings like About the role, Responsibilities, etc. We could use About the role for this intro plus maybe role description. But we also have a separate responsibilities section. We could have sections: About the role (company overview + role summary), Responsibilities (detailed bullet list), Requirements (profile), Benefits (what we offer), Pay (salary range), Schedule (flexible hybrid work environment). Ensure each has content. We must not repeat job title as heading; fine. We need to avoid duplication: The responsibilities section includes bullet list under "Your responsibilities will include:" and then subheadings Data Engineering, Stakeholder Management, Project Management & Delivery Excellence. We should capture all bullet points. We need to format as

  • for any list. For subheadings maybe we can keep as

    ? But instruction only mentions using

    for section headings. It didn't forbid other headings, but we should likely keep within

    sections and use

    or

    inside. Could treat subheadings as or just part of
    • . Simpler: produce a flat list of responsibilities. But we need to preserve all substantive information; we can keep subheadings as part of list items. Let's extract responsibilities bullet points: Data Engineering: - Design, develop, and deploy scalable data pipelines and ETL workflows in Databricks. - Transform and harmonize data from diverse sources and formats (i.e. APIs, CSV files, JSON, databases, cloud platforms, file transfers, etc.) - Build and industrialize cloud-based data solutions and frameworks that support efficient data ingestion, integration, processing, and delivery, enabling reliable and analytics-ready datasets for accounts. - Define and implement robust data architectures, QA, validation, and monitoring processes to ensure accuracy, consistency, reliability, and scalability. Stakeholder Management: - Partner with internal and external stakeholders to understand client data ecosystems, business objectives, account needs, and long-term goals, ensuring alignment between solutions and business priorities. - Translate client requirements into scalable data engineering designs, collaborating cross-functional teams to develop effective ETL frameworks. - Serve as a trusted point of contact through project delivery, communicating technical recommendations and project progress while promoting best practices in data management. Project Management & Delivery Excellence: - Take ownership of project deliverables from planning through execution, managing priorities, timelines, and risks to ensure high-quality outcomes delivered on time aligned with client objectives. - Proactively identify and mitigate potential project, technical, and data-related risks, communicating issues, recommendations, and status updates clearly. - Collaborate cross-functionally to coordinate activities, align expectations, and drive project execution. Now Profile (Your Profile): - Bachelor’s or Master’s degree in Data Science, Computer Science, Engineering, or a related quantitative field, with 4-6 years of experience in data engineering, analytics, or statistical modeling. - Proficient with Databricks (Delta Lake, Spark, Asset Bundles, Unity Catalog, Cluster Management) - Proficiency in Python and working knowledge of SQL, Spark, and Bash scripting. - Experience with templating languages is a plus. - Skilled in building and deploying production-grade data pipelines and architectures complete with CI/CD plus experience with ELT/ETL processes. - Experience with Azure required, familiarity with GCP or AWS a plus. - Experience with PowerBI or Tableau for dashboarding and data visualizations. - Exposure to ML or advanced analytics techniques is a plus. - Strong communication, stakeholder management, and project delivery skills, with the ability to explain technical concepts to non-technical audiences. What We Offer: - At Ekimetrics, final base salary is determined by a multitude of factors and vary from candidate to candidate. Determining factors for base compensation include, but are not limited to, professional background, years of experience, and skillset. A reasonable estimate of the base salary for our NYC office is between $125,000 and $140,000. In addition to this base salary, we have a comprehensive benefits package, generous bonus package, and a dynamic promotions and salary structure. - The Eki.Academy training catalog, which contains programs that will enhance your skills on our solutions and jobs, learning paths on our digital platform, as well as programs dedicated to our priority challenges, including awareness of environmental issues with the Climate School - Dynamic environment with a strong culture and great offices - Close-knit team with bi-monthly team events and more - Client exposure up to the executive level - Modern office just off Wall Street with best-in-class amenities - An emphasis on work-life-balance and 20 days of PTO with 11 annual holidays in a flexible hybrid work environment - Opportunities for international mobility across our four other offices in Paris, London, Hong Kong, and Shanghai Why join us? (maybe we can incorporate into About the role or Benefits? It's more about culture. Could be a separate section "Why join us?" but not in the list of allowed headings. The instruction gave examples but not limited to those; we could still use other headings but better to stick to given ones. However we can incorporate that content into Benefits or About the role. The "Why join us?" section includes: ideas matter, entrepreneurial spirit, collaboration, learning, enjoying work, mission-driven company status, CSR, Great Place to Work certifications, French Tech 120, equal employment opportunities, inclusive environment, note about visa sponsorship not offered. Some of that is boilerplate (EEO, visa sponsorship). We should remove EEO and visa sponsorship note as boilerplate. Keep the rest: ideas matter, entrepreneurial spirit, collaboration, learning, enjoying work, mission-driven company status, CSR, Great Place to Work certifications, French Tech 120. That's substantive. We could add a section "About the role" that includes company overview and why join us? Or we could add a section "Why join us?" but not in the list; maybe better to incorporate into Benefits or About the role. Given 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 but we can use others if needed? It says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. So we should stick to those. Thus we need to map content to those headings. - About the role: company overview + maybe role summary (the introductory paragraph about Ekimetrics and the role's purpose). Could also include "Why join us?" content as part of About the role. - Responsibilities: the bullet list. - Requirements: maybe combine Profile (education, experience) and Skills (technical proficiencies). Could split into Requirements and Skills but we can combine into Requirements or have both. - Qualifications: maybe same as Requirements? Could use Requirements for education/experience, Qualifications for technical skills, Skills for soft skills. But we have many items. Better to have sections: About the role, Responsibilities, Requirements (education/experience), Skills (technical proficiencies), Benefits, Pay, Schedule. We must avoid thin sections; but we have enough content. Let's extract: About the role: company overview paragraph (first big paragraph) plus maybe the sentence "Your ResponsibilitiesAs a Senior Data Engineer, you will lead and contribute to high-impact projects..." but that's basically responsibilities intro. We'll keep responsibilities separate. Thus About the role: the Ekimetrics description. Responsibilities: the bullet list. Requirements: education/experience: "Bachelor’s or Master’s degree in Data Science, Computer Science, Engineering, or a related quantitative field, with 4-6 years of experience in data engineering, analytics, or statistical modeling." Skills: technical proficiencies: Databricks, Python, SQL, Spark, Bash, templating languages, CI/CD, ELT/ETL, Azure, GCP/AWS, PowerBI/Tableau, ML/advanced analytics, communication/stakeholder/project delivery skills. But we also have "Strong communication, stakeholder management, and project delivery skills, with the ability to explain technical concepts to non-technical audiences." That's a skill. We could also include "Experience with templating languages is a plus." etc. Benefits: the What We Offer list excluding salary details (which go to Pay). Benefits: comprehensive benefits package, generous bonus package, dynamic promotions and salary structure, Eki.Academy training catalog, dynamic environment, strong culture, great offices, close-knit team with bi-monthly team events, client exposure up to executive level, modern office off Wall Street with best-in-class amenities, emphasis on work-life-balance and 20 days P