Strategic Data & Analytics Engineer (Cloud Data & Agentic Infrastructure)

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to parse the posting. We have sections: - About SH/FT Shift Paradigm (company description) – could be "About the role"? Actually "About SH/FT Shift Paradigm" is company overview. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly. We need to avoid repeating job title as heading (the page already shows it). So we don't put a heading for job title. We need to include sections only when posting has real specific content. Let's extract: Company description: "About SH/FT Shift Paradigm is an execution-led strategic consultancy..." This is about the company, not role. Could map to "About the role"? Actually "About the role" is about the role description. The posting includes "The Role" section describing responsibilities. So we can put that under

About the role

maybe? But they said "About the role" as example heading. We'll use that for the role description. Responsibilities: The bullet list under "What You'll Accomplish" includes many items. Those are responsibilities. Requirements: Could be "What You Bring Experience & Expertise" etc. That's qualifications/requirements. Qualifications: Might overlap with Requirements. We could combine? But we need separate headings only if content exists. Could have "Requirements" for experience, and "Qualifications" for certifications? Or "Skills" for technical skills. Benefits: The posting includes "What We Offer" with compensation, remote flexibility, collaborative culture, etc. Also "Comp & Benefits" includes salary range and benefits. So we have Benefits and Pay sections. Pay: Salary range $120,000 to $140,000 USD. Schedule: Not mentioned (no schedule info). So we should not include Schedule section. We must not include placeholder text like "commensurate with experience". Not present. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the details. We need to use

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

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is some legal text about accommodations, work authorization, E-Verify, etc. That's boilerplate; we should remove it. Also "No relocation assistance can be offered at this time." etc. Remove. We need to keep substantive info: company description, role description, responsibilities list, experience/expertise list, certifications, mindset, remote flexibility, collaborative culture, work that makes difference, compensation and benefits. We need to avoid duplication: The "Comp & Benefits" repeats salary range and benefits; also earlier "What We Offer" includes competitive compensation, remote flexibility, collaborative culture, work that makes a measurable difference. We'll combine. We must not repeat job title as heading. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  ... company description? Actually "About the role" should contain role description: The Role paragraph and maybe the "We are seeking..." paragraph. Let's include that. Then

  Responsibilities

  with
  of each accomplishment bullet. Then

  Requirements

  with
  of experience/expertise items. Then

  Skills

  maybe for technical skills list? Could include "Advanced Data Engineering Skills", "Domain & Integration Knowledge", "Data Modeling Fundamentals". But those are part of requirements. Might be better to have a single Requirements section covering all. But instruction says prefer few substantive sections over many thin ones. So we could combine experience, skills, qualifications into one Requirements section. However they gave examples of separate headings; but we can decide to combine if it avoids thin sections. We have also "Preferred Certifications" and "Mindset" etc. Those could be part of Requirements or Qualifications. We have "What We Offer" and "Comp & Benefits" for Benefits and Pay. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We'll not include Qualifications or Skills separately. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Let's extract precise text. Company description paragraph: "About SH/FT Shift Paradigm is an execution-led strategic consultancy that bridges the gap between enterprise strategy and technical reality. We partner with Fortune 500 brands and emerging leaders to solve the inherent complexity of modern digital marketing. As partners to the world’s leading MarTech platforms, including Adobe, Salesforce, Optimizely, and Braze, we deploy integrated experts across data analytics, marketing strategy, technology development, engineering, and revenue operations to ensure our clients’ tech stacks don't just exist, but perform." That's substantive. The Role paragraph: "We are seeking a forward-thinking, consultative Data & Analytics Engineer to design, build, and maintain enterprise marketing data models, ontologies, and semantic context layers. In this role, you will act as a strategic bridge between business leaders and technical execution—partnering directly with clients to understand their strategic goals and translating those business requirements into scalable, warehouse-native data infrastructure. Beyond core data engineering, you will spearhead how our clients' data ecosystems adapt to an evolving agentic future. You will architect the semantic models and data integration patterns required to power autonomous AI agents, both native to modern cloud data platforms (such as Databricks and Snowflake) and across connected MarTech platforms (such as Salesforce, Hightouch)." We'll combine these two paragraphs under About the role. Now Responsibilities: bullet list under "What You'll Accomplish". Each bullet starts with a bold heading? Actually they are like: Consultative Requirements & Architecture: Partner with key business stakeholders to uncover core business goals, mapping complex business domain needs into unified data engineering solutions, semantic layers, and robust warehouse architectures. Agentic & AI Data Readiness: Architect forward-looking context layers and semantic models designed specifically for AI/LLM-driven engines and autonomous agents—ensuring data ecosystems (from modern cloud warehouses to activation platforms like Hightouch and Salesforce) are structured for reliable execution. Taxonomy & Metadata Engineering: Design scalable data models (e.g. Medallion/Multi-layer architectures) to house controlled classification hierarchies, unified asset tags, and standardized business glossaries across marketing channels. Identity & Semantic Modeling: Build and maintain deterministic and probabilistic identity resolution models and graph-like bridge tables to resolve customer identities across CRM IDs, device tokens, and digital touchpoints. Cross-System Pipeline Integration: Lead the technical integration of complex cross-system datasets, developing high-performance ingestion and transformation pipelines to unify marketing metadata, CDP activation models, DAM content, and real-time telemetry. Data Governance & Quality: Implement enterprise governance, business glossaries, access controls, and data cataloging (e.g., Unity Catalog, Snowflake Horizon) to enable secure self-service analytics and reliable AI execution. We'll put each as
  • with the full sentence. Now Requirements: "What You Bring Experience & Expertise" list: - 5+ years of hands-on experience in data engineering, analytics engineering, or data architecture building production-grade data pipelines and semantic models. - 2+ years in a client-facing, consultative, or strategic lead role—demonstrated ability to run discovery, map business goals to technical architectures, and present solutions to cross-functional stakeholders. - Willing to travel 25% a year and up to twice a quarter minimum. - Consultative Mindset: Strong ability to navigate ambiguity, translate non-technical business strategies into clear technical specifications, and articulate technical trade-offs to executives and cross-functional teams. - Strategic Vision for AI/Agents: A keen interest in the shift toward agentic AI, with an understanding of how data modeling, semantics, and context layers must adapt to support autonomous workflows across data platforms and marketing engines. - Cloud Data Platform Expertise: Hands-on experience designing production pipelines and semantic data models across modern cloud data platforms, with deep expertise in Databricks, Snowflake, or equivalent architectures. - Advanced Data Engineering Skills: Proficiency in SQL, Python/PySpark, data pipeline orchestration, and modern data stack tooling (e.g., dbt). - Domain & Integration Knowledge: Experience with marketing technology (MarTech), Customer Data Platforms (CDPs), reverse ETL tools (e.g., Hightouch, Census), and enterprise platforms (e.g., Salesforce Marketing Cloud, CRMs). - Data Modeling Fundamentals: Proven track record in multi-dimensional schema design, identity resolution modeling, graph/hierarchical structures, and API payload parsing (nested JSON/REST). - Relevant Certifications (Preferred): Professional Data Engineer / Analytics Engineer certifications in Databricks or Snowflake. Then "Preferred Certifications" list: - Databricks: Certified Data Engineer Professional or Certified Analytics Engineer. - Snowflake: SnowPro Core or SnowPro Advanced Architect. - dbt: dbt Cloud Developer Certification. Then "Mindset" section: - Forward-Thinking AI Perspective: Active interest and practical awareness of agentic AI concepts (e.g., tool use, LLM context retrieval, autonomous agent workflows) and how data modeling must evolve to serve them. - Remote & Autonomous: Ability to manage complex deliverables independently in a distributed, fast-paced environment. We can include all these under Requirements. Now Benefits: "What We Offer" paragraph: - Competitive compensation aligned with your experience and impact - Remote flexibility - Collaborative culture that values diverse perspectives and innovative thinking - Work that makes a measurable difference for your clients Also "Comp & Benefits" paragraph: - The US salary range for this role is $120,000 to $140,000 USD. Salary is based on several factors including but not limited to skillset, relevant education, level of experience, certifications, and scope of responsibilities. - In addition to base salary, SH/FT offers benefits such as medical, dental, vision, STD/LTD, Life/AD&D, Flexible Paid Time Off, and various other ancillary benefits and perks. We should combine these into Benefits and Pay sections. Pay: Salary range. Benefits: list of benefits and other offerings. We must not include boilerplate like "We welcome and encourage applications from people with disabilities under the Accessibility for Ontarians with Disabilities Act. Accommodations are available on request for candidates taking part in all aspects of the selection process. Candidates must have current US or Canada work authorization. For US candidates, this employer participates in E-Verify and will provide the federal government with your Form I-9 information to confirm that you are authorized to work in the US. No relocation assistance can be offered at this time. All inquiries are held in strict confidence." Remove. Also "The Pay Range For This Role Is 120,000 - 140,000 USD per year (Remote (United States))" duplicate; we already have salary range. Now produce HTML. We need to use

    for each section heading. Inside each section, use

    for prose,

    • for lists. We must not include any extra text outside HTML. Let's craft. First section: About the role. We'll put two paragraphs: company description and role description. Could combine into one

      but better separate

      for each. Second: Responsibilities:

      with each bullet. Third: Requirements:
      with each bullet (including mindsets, certifications). Might be long but okay. Fourth: Benefits:
      with items: Competitive compensation aligned with your experience and impact, Remote flexibility, Collaborative culture that values diverse perspectives and innovative thinking, Work