Senior Data Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes description of company, 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). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. 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. IMPORTANT: 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Company description (Ekimetrics is a global leader...). Could be "About the role"? Actually "About the role" maybe not; but we could have "About Ekimetrics" but not in list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings if content matches. The posting includes responsibilities, profile (which includes qualifications, skills), what we offer (benefits, pay, etc.), why join us (culture). We need to map. We must not repeat job title as heading. So we can have sections: Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, maybe About the role? The company description could be considered "About the role"? Not exactly. But we could include a short paragraph about the company under a heading like "About the role"? Might be okay. However instructions: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings if appropriate. We could also use other headings? Probably better to stick to those. We need to include sections only when posting has real specific content. So we need to see if we have content for each. Responsibilities: Yes, detailed list. Requirements/Qualifications: The posting has "Your Profile" with degree, years experience, proficiencies. That could be split into Requirements (education, experience) and Qualifications (skills). Or we could combine into Requirements. Skills: Could be separate. Benefits: The posting has "What We Offer" includes base salary estimate, comprehensive benefits package, generous bonus package, dynamic promotions and salary structure, Eki.Academy training catalog, dynamic environment, close-knit team, client exposure, modern office, work-life balance, 20 days PTO, 11 holidays, flexible hybrid, opportunities for international mobility. Also mentions "Why join us?" includes mission-driven, Great Place to Work, etc. So we have benefits content. Pay: The posting gives salary estimate: "A reasonable estimate of the base salary for our NYC office is between $125,000 and $140,000." Also mentions final base salary determined by factors. So we have pay info. Schedule: Not explicitly mentioned; only flexible hybrid work environment, but not specific schedule. Could be considered schedule? Might be too vague. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not explicitly stated; we have flexible hybrid but not specific hours. Probably we should not include Schedule section. Thus sections: Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. Possibly also About the role (company description). But we could incorporate company description into a brief paragraph under Responsibilities? Better to have an "About the role" section describing the role and company. The posting includes a paragraph at start about Ekimetrics. That could be under "About the role". Let's do that. Thus sections:

  About the role

  Ekimetrics is a global leader in Marketing & Commercial effectiveness and AI-powered solutions...

  Responsibilities

  • ...

  Requirements

  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

  • 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.

  Benefits

  • Comprehensive benefits package
  • Generous bonus package
  • Dynamic promotions and salary structure
  • Eki.Academy training catalog with programs to enhance skills, learning paths, and programs dedicated to 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
  • 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

  Pay

  A reasonable estimate of the base salary for our NYC office is between $125,000 and $140,000. Final base salary is determined by a multitude of factors including professional background, years of experience, and skillset.

  We need to ensure we preserve all substantive information. Did we miss any? The responsibilities list includes many bullet points; we need to capture them all. Let's extract responsibilities from text: "Your ResponsibilitiesAs a Senior Data Engineer, you will lead and contribute to high-impact projects with top-tier international clients across industries, designing, implementing, and optimizing ETL solutions that support Marketing Mix Modeling and Optimization and broader Marketing Effectiveness initiatives. You’ll work closely with data engineers, data scientists, and tech leads across 1-2 concurrent projects, build robust, scalable data architectures that enable marketing analytics and support data driven decision making. In addition to technical ownership, you will play a key role in project and stakeholder management, partnering with cross-functional teams and client stakeholders to ensure successful project delivery and business impact. You will also benefit from our technology partnerships, training programs, and mentorship from Ekimetrics partners, further developing your expertise in data engineering, project management, and stakeholder engagement. Your responsibilities will include: Data EngineeringDesign, 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 ManagementPartner 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 ExcellenceTake 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." We need to break into list items. Could group into categories but we can just list each sentence as
• . Ensure we preserve all. Let's create list: - Lead and contribute to high-impact projects with top-tier international clients across industries, designing, implementing, and optimizing ETL solutions that support Marketing Mix Modeling and Optimization and broader Marketing Effectiveness initiatives. - Work closely with data engineers, data scientists, and tech leads across 1-2 concurrent projects, build robust, scalable data architectures that enable marketing analytics and support data-driven decision making. - Play a key role in project and stakeholder management, partnering with cross-functional teams and client stakeholders to ensure successful project delivery and business impact. - Benefit from technology partnerships, training programs, and mentorship from Ekimetrics partners, further developing expertise in data engineering, project management, and stakeholder engagement. - 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. That seems comprehensive. Now Requirements: The profile includes degree and experience. Also maybe "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." That's it. Skills: we listed. Benefits: we listed many items. Need to ensure we captured all from "What We Offer" and "Why join us?" The "Why join us?" includes mission-driven company status, purpose, Great Place to Work certifications, French Tech 120, equal employment opportunity statement (but