Jobs · Management · Texas

Data Engineering Technical Lead

Expedia Group · Austin, TX · 3 wk ago
On-siteManagement$185k–$258k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes description of role, responsibilities, qualifications, benefits, pay, schedule? No schedule mentioned. Benefits present. Pay present (multiple locations). We need to include sections only when real specific content. So we will have sections: About the role (maybe description), Responsibilities (list of duties), Requirements (experience and qualifications), Benefits (benefits and perks), Pay (pay ranges). Possibly also Qualifications separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can combine Requirements and Qualifications? Better to have Requirements (experience and qualifications) and maybe Skills separate? But we have a lot of skill details; could put under Requirements. We'll avoid duplicate. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. Remove accommodation requests? That's maybe legal but could be considered boilerplate; but it's about accommodation request; might be considered EEO? Probably remove. Also remove "About Expedia Group" maybe not needed? It's about company; could be considered boilerplate but maybe relevant? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Expedia Group" is not exactly those but could be considered company overview; might be okay to keep? Might be considered not substantive for role? It's generic. Safer to omit. Also remove "Important notice", "Equal Opportunity". Also remove "Learn more about life at Expedia Group at ..." maybe not needed. Keep benefits and perks. We need to preserve all substantive information: responsibilities list, qualifications list, benefits list, pay ranges. We'll structure:

About the role

... description of role (first paragraphs).

Responsibilities

  • ... each bullet from "In This Role, You Will" list.

Requirements

  • ... each bullet from Experience And Qualifications and Preferred Qualifications? Might combine required and preferred? Could separate Required and Preferred but headings limited. Could just list all as requirements; but we should differentiate? Not required. We'll list required qualifications (the ones before "Preferred Qualifications") as required, and then maybe a separate section "Preferred Qualifications". But we have heading for Qualifications and Skills. Could do Requirements (required) and Preferred Qualifications (preferred). Let's do:

    Requirements

      for required experience/qualifications.

      Preferred Qualifications

        for preferred. But instruction says use headings like Requirements, Qualifications, Skills. We can use Requirements and Preferred Qualifications as separate headings (though not in list but acceptable). Probably okay.

        Benefits and Perks

          list benefits.

          Pay

          include pay ranges for Austin, Chicago, Seattle and note potential increase and starting pay variability. No Schedule. Make sure not to include filler like "commensurate with experience". Not present. Now craft HTML. We need to extract responsibilities bullets from the long list. Let's list them: - Lead the design and delivery of complex, end-to-end SFMC initiatives for partner marketing, such as journey and automation builds and NBA integration, with minimal day-to-day guidance. - Own and architect the end-to-end data model for Salesforce Marketing Cloud and Salesforce Data Cloud (Data 360), including Data Extensions, Contact Builder/Data Designer relationships, Data Model Objects (DMOs), Data Lake Objects (DLOs), and Identity Resolution rulesets. - Design and build a knowledge graph connecting partner, property, contact, and campaign entities across SFMC, Data Cloud, and upstream systems to enable unified partner profiles, relationship discovery, and Next Best Action (NBA) recommendations. - Define the ontology, entity-relationship structure, and identity resolution/deduplication logic underpinning the knowledge graph and Data Cloud unified profiles. - Design, develop, and optimize data capture, processing, storage, and distribution solutions that power marketing campaigns, reporting, and partner integrations. - Build and maintain batch and streaming pipelines that are reliable, observable, and cost-efficient at scale. - Model and curate datasets that marketing, analytics, and partner teams can trust and self-serve from. - Expose data through well-designed APIs and services that integrate with internal platforms and third-party marketing tools. - Use AI-assisted development tools in your day-to-day workflow, and help the team establish where they help and where they do not. - Partner with the business to integrate AI and LLM capabilities into marketing data workflows enrichment, classification, content generation, and agentic automation—with appropriate evaluation and guardrails. - Design and develop ETL/ELT pipelines end-to-end, from source system extraction (for example, PMDS, Salesforce Core CRM) through transformation and orchestration, into SFMC Data Extensions, Data Cloud DMOs/DLOs, and the knowledge graph, including evaluating SFMC/Data Cloud-native data management versus custom pipelines. - Architect Zero Copy integration between Salesforce Data Cloud and EG's external data lake (for example, AWS, EGDL), so data used for marketing can be queried in place without duplicating it, keeping it available outside SFMC for analytics and other downstream consumers. - Establish data pipeline orchestration, scheduling, and monitoring (for example, Airflow, dbt, or similar), with clear SLAs for data freshness, identity resolution accuracy, and pipeline reliability, as the team scales from pilot to production volumes. - Drive platform health and reliability practices (for example, change/release management, CI/CD for Salesforce metadata, monitoring and alerting) across SFMC and Data Cloud. - Serve as a go-to technical resource for engineers and partner marketing stakeholders building on SFMC and Data Cloud, unblocking complex technical issues and reviewing designs and pull requests for platform-wide standards. - Mentor other engineers on the team and share platform and data architecture knowledge through documentation to raise the team's overall technical standards. - Partner with partner marketing stakeholders, data science partners, and Salesforce (vendor) contacts to translate platform capabilities and constraints into practical implementation plans. Now required qualifications bullets (from Experience And Qualifications): - Bachelor's degree in Computer Science or a related technical field; or equivalent related professional experience. - 10+ years of experience building and operating enterprise software platforms, with hands-on experience in Salesforce Data Cloud (Data 360, Automation Studio, Journey Builder, Content Builder, SSJS/AMPscript, SOAP/REST APIs) or comparable enterprise MarTech platforms. - Demonstrated experience leading complex technical projects end-to-end within a team or domain, with minimal supervision. - Experience with data integration patterns (for example, SFTP, SOAP/REST, Data Extensions, CDP/Data Cloud) connecting marketing platforms to upstream and downstream systems. - Experience architecting data models for CRM or marketing platforms, such as Salesforce Marketing Cloud (Contact Builder/Data Designer, Data Extensions) and/or Salesforce Data Cloud (Data Model Objects, Data Lake Objects, Identity Resolution). - Data engineering experience, including designing and building ETL/ELT pipelines end-to-end, data modeling for large-scale audience and contact datasets, and working with SQL and cloud data warehouses (for example, AWS, Snowflake, or similar) to move and transform partner data into marketing platforms. - Strong proficiency in SQL and at least one programming language commonly used for data engineering (for example, Python, Scala, or Java), along with experience using data processing frameworks and orchestration tools (for example, Spark, Airflow, dbt, or similar). - 5+ years of hands-on programming experience with Python, Java, or Scala. - Strong SQL skills and a solid understanding of database design, data ingestion, modeling, and performance optimization. - Demonstrable experience leveraging AWS services, including S3, Redshift, Lambda, Glue, DynamoDB, EC2, and AppFlow. - Experience with batch and/or stream processing using Spark, Kafka, or SQS. - Experience building with LLMs and GenAI services (for example Amazon Bedrock)—prompt design, retrieval/RAG patterns, vector stores, and evaluating output quality, cost, and latency. - Experience using agentic AI for development and task orchestration – configuring, constraining, and reviewing agent-produced code and building custom skills/workflows to accelerate delivery. Preferred qualifications bullets: - Experience migrating marketing communications off legacy platforms (for example, Marketo, Message Gears, or similar ESPs) onto Salesforce Marketing Cloud. - Experience with Salesforce Data Cloud (Data 360), including Identity Resolution, Calculated Insights, DMO/DLO modeling, or evaluating native platform data management as an alternative to custom data pipelines. - Experience with Zero Copy data architecture (for example, Salesforce Data Cloud Zero Copy Partner Network/BYOL, or comparable federated query patterns) that lets data be queried in place across an external data lake and a CRM/marketing platform without duplicating it. - Experience designing or building knowledge graphs, including ontology and schema design, entity resolution, and graph databases (for example, Neo4j, Amazon Neptune, or similar) and query languages (for example, Cypher, SPARQL, Gremlin). - Familiarity with CI/CD for Salesforce metadata (Git-based deployment, change/release management for Marketing Cloud components). - Experience in B2B or partner-facing marketing and communications platforms. - Experience designing data pipelines that feed audience segmentation or Next Best Action (NBA) style recommendation systems. - Experience with streaming and batch data processing, including schema evolution, backfill, and data freshness service level objectives (SLOs). - Experience with data governance practices such as data contracts, lineage tracking, and PII/privacy compliance in marketing data platforms. - Salesforce Marketing Cloud certifications (for example, Email Specialist, Developer). Now benefits list: - medical, dental, and vision coverage - paid time off - Employee Assistance Program - wellness and travel reimbursement - travel discounts - International Airlines Travel Agent Network (IATAN) membership Now pay: - The total cash range for this position in Austin is $184,500.00 to $258,000.00. Employees in this role have the potential to increase their pay up to $295,000.00, which is the top of the range, based on ongoing, demonstrated, and sustained performance in the role. - The total cash range for this position in Chicago is $171,500.00 to $240,000.00. Employees in this role have the potential to increase their pay up to $274,500.00, which is the top of the range, based on ongoing, demonstrated, and sustained performance in the role. - The total cash range for this position in Seattle is $184,500.00 to $258,000.00. Employees in this role have the potential to increase their pay up to $295,000.00, which is the top of the range, based on ongoing, demonstrated, and sustained performance in the role. - Starting pay for this role will vary based on multiple factors, including location, available budget, and an individual’s knowledge, skills, and experience. Pay ranges may be modified in the future. We'll put that in a

          maybe multiple sentences. Now About the role paragraph: combine initial paragraphs up to "We're looking for a Senior Technology Lead to help drive that build-out." plus maybe the sentence "In this role, you'll be a senior technical voice..." Actually that is part of responsibilities. We'll keep About the role as the introductory description before responsibilities. Let's craft:

          At Expedia Group, we help travelers explore the world, one journey at a time. As a global travel company powered by passionate people, trusted partnerships, and leading technology, we connect travelers, partners, and advertisers through our consumer brands, B2B network, and travel advertising business. Here, you

Similar jobs

Data Engineering Tech Lead

Tata Consultancy ServicesJersey City, NJ· 1 mo ago
Management$180k–$210k/yrapply on ibegin.tcsapps.com