Senior Data Architect

We need to output HTML fragment with sections only where there is real specific content. Must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - "Opportunity As a Senior Customer Experience Orchestration Data Architect at Adobe, you will lead the development of advanced, secure data solutions for our innovative digital marketing platforms. We craft data strategy, architecture, SQL and governance for customer solutions, including end-to-end profiles, segmentation, journeys, and campaigns!" This is about the role. So we can have

About the role

with paragraph(s) containing that description. - Responsibilities: The "What You’ll Do" section lists many bullet points. So we need a Responsibilities section with

• items. - Requirements: There's a "Requirements" heading in the posting: "Degree in Computer Science, Information Systems, Data Science, or a related field or equivalent experience. 10+ years of data architecture, modeling, SQL, and working with customers!Expert proficiency..." That's requirements. Also there is "Special Consideration given for Hands-on use or administration of Adobe Experience Platform (AEP)Deep domain expertise in one or more industries..." and "Experience with programming languages (e.g., Python or Bash scripting)". Those are also requirements/qualifications. We can combine into Requirements section. - Qualifications: Might be overlapping. The posting also has "About Adobe" which is company description, not a section we need. Could be "About the role" already covered. There's no separate Benefits, Pay, Schedule except Pay is mentioned: "Expected Pay Range: ..." So we need a Pay section with that info. Benefits: not mentioned specifically besides generic benefits but not detailed; we should not create Benefits unless specific. Schedule: not mentioned. Thus sections: About the role, Responsibilities, Requirements, Pay. We must not include headings with filler. Ensure we preserve all substantive info. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we strip the Adobe EEO paragraphs, AI Use Guidelines, State-Specific Notices, etc. Also remove "About Adobe" description? It's not a required section but could be considered "About the role"? Actually "About Adobe" is company overview, not required. We can omit it as it's not a specific section heading we need to include; but we must preserve ALL substantive information. Does that mean we must keep the Adobe description? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." However we are allowed to omit sections if not specific? The instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't say we must include all info; we must preserve substantive information, but we can embed it within appropriate sections. The Adobe description is substantive but not fitting under any of the allowed headings? Could be placed under "About the role"? Actually "About the role" is about the job, not company. But we could add a separate section like "About Adobe" but not in allowed headings list. The allowed headings list is given as examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely we should stick to those. The Adobe description could be considered "About the role"? Not exactly. However we could incorporate it into About the role paragraph as context: "At Adobe, you will...". The posting already says "Opportunity As a Senior Customer Experience Orchestration Data Architect at Adobe, you will lead...". That includes Adobe. So we can keep that. Thus we will output:

  About the role

  Opportunity As a Senior Customer Experience Orchestration Data Architect at Adobe, you will lead the development of advanced, secure data solutions for our innovative digital marketing platforms. We craft data strategy, architecture, SQL and governance for customer solutions, including end-to-end profiles, segmentation, journeys, and campaigns!

  Responsibilities

  • Provide deep experience to build data solutions across multiple Adobe products and cloud platforms aligned with enterprise data strategy.
  • Engage closely with customers and Adobe team to facilitate data discovery by evaluating systems and business processes.
  • Analyze customer sources, data movement, data granularity, relationships, data format, etc.
  • Unify disparate data (e.g., sales, CRM, analytics data, etc.) to meet customers’ digital marketing use cases.
  • Lead and develop conceptual, logical, and physical data models for multi-solution delivery.
  • Establish frameworks for data quality, define standards, master data management, data services, data governance, data modeling, tools, data security, privacy, and compliance with industry regulations (PII, PCI, HIPAA, GDPR, etc.).
  • Develop and champion data architecture guidelines via detailed documentation. These encompass architectural blueprints, ERDs, data flow diagrams, source-to-target mappings, data dictionaries, metadata catalogs, governance frameworks, guardrails, and security and compliance protocols.
  • Engage with cross-disciplinary groups and Adobe professionals to identify customer demands.
  • Provide data layout and strategic blueprints, advocating for scalable, secure resolutions.
  • Assume the role of a liaison to promptly tackle technical obstacles.
  • Develop strategies for growing data volumes, tools, and integrations, while aligning with customers’ objectives.
  • Deliver mentorship on data architecture to customers and consultants to align work with targets.
  • Deliver Adobe platform data lake and real-time customer profile to get ready for data ingestion and activation.
  • Employ REST APIs, Postman, and basic scripting to automate and streamline the implementation and setup.
  • Develop and construct data ingestion solutions for streaming and batch processing, online and offline data within AEP.
  • Collaborate with data engineers to develop and implement ETL/ELT pipelines for data collection and extraction.
  • Improve data query performance across platforms by tuning models and adhering to guidelines and ensure product guardrails are followed and deployed in solutions.

  Requirements

  • Degree in Computer Science, Information Systems, Data Science, or a related field or equivalent experience.
  • 10+ years of data architecture, modeling, SQL, and working with customers.
  • Expert proficiency in crafting customer-centric database models, datasets (e.g., CRM, Call Center, Marketing, Offline, Point of Sale, etc.) with relational, hierarchical (e.g., RDBMS, Columnar, Data Warehouse, BI, Document, Semantic layer modeling, Data Lakes, OLTP & OLAP, etc.).
  • Advanced skills in SQL development (e.g., functions, data transformations, arrays, joins details, stored procedures, data analysis).
  • Deep experience in translating business requirements into scalable data architecture by conducting structured analysis of data workflows and processes.
  • Demonstrate outstanding organizational skills and ability to balance customer projects concurrently with strong verbal, written communication skills and previous experience with customer-facing engagements.
  • Special consideration given for hands-on use or administration of Adobe Experience Platform (AEP).
  • Deep domain expertise in one or more industries (Retail, Telecom, Healthcare, Automotive, Cloud and Streaming platforms, etc.).
  • Experience with programming languages (e.g., Python or Bash scripting).

  Pay

  Expected Pay Range: Our compensation reflects the cost of labor across several U.S. geographic markets, and we pay differently based on those defined markets. The U.S. pay range for this position is $146,800 - $263,900 annually. Pay within this range varies by work location and may also depend on job-related knowledge, skills, and experience. Your recruiter can share more about the specific salary range for the job location during the hiring process. In California, the pay range for this position is $182,300 - $263,900. In New York, the pay range for this position is $182,300 - $263,900. In Washington, the pay range for this position is $171,600 - $248,600.

  We should not include any other sections like Benefits, Schedule. Ensure no extra whitespace? It's fine. Check for any duplicated lines: we removed EEO etc. Also removed "About Adobe" paragraphs, AI Use Guidelines, State-Specific Notices. We kept all substantive info from the posting: the opportunity paragraph, responsibilities list, requirements list, pay details. Make sure we didn't miss any responsibility bullet: we captured all bullet points from "What You’ll Do". Let's verify original text: "What You’ll Do Provide deep experience to build data solutions across multiple Adobe products and cloud platforms aligned with enterprise data strategy. Engage closely with customers and Adobe team to facilitate data discovery by evaluating systems and business processes. Analyze customer sources, data movement, data granularity, relationships, data format, etc. Unify disparate data (e.g., sales, CRM, analytics data, etc.) to meet customers’ digital marketing use cases. Lead and develop conceptual, logical, and physical data models for multi-solution delivery. Establish frameworks for data quality, define standards, master data management, data services, data governance, data modeling, tools, data security, privacy, and compliance with industry regulations (PII, PCI, HIPAA, GDPR, etc.). We develop and champion data architecture guidelines via detailed documentation. These encompass architectural blueprints, ERDs, data flow diagrams, source-to-target mappings, data dictionaries, metadata catalogs, governance frameworks, guardrails, and security and compliance protocols. We engage with cross-disciplinary groups and Adobe professionals to identify customer demands. We provide data layout and strategic blueprints, advocating for scalable, secure resolutions. Assume the role of a liaison to promptly tackle technical obstacles. We develop strategies for growing data volumes, tools, and integrations, while aligning with customers’ objectives. We deliver mentorship on data architecture to customers and consultants to align work with targets. We deliver Adobe platform data lake and real-time customer profile to get ready for data ingestion and activation. Employ REST APIs, Postman, and basic scripting to automate and streamline the implementation and setup. Develop and construct data ingestion solutions for streaming and batch processing, online and offline data within AEP. Collaborate with data engineers to develop and implement ETL/ELT pipelines for data collection and extraction. We improve data query performance across platforms by tuning models and adhering to guidelines and ensure product guardrails are followed and deployed in solutions" We turned each sentence into a bullet. Good. Requirements: original text after "Requirements": "Degree in Computer Science, Information Systems, Data Science, or a related field or equivalent experience. 10+ years of data architecture, modeling, SQL, and working with customers!Expert proficiency in crafting customer-centric database models, datasets (e.g., CRM, Call Center, Marketing, Offline, Point of Sale, etc.) with relational, hierarchical (e.g., RDBMS, Columnar, Data Warehouse, BI, Document, Semantic layer modeling, Data Lakes, OLTP & OLAP, etc.). Advanced skills in SQL development (e.g., functions, data transformations, arrays, joins details, stored procedures, data analysis). Deep experience in translating business requirements into scalable data architecture by conducting structured analysis of data workflows and processesDemonstrate outstanding organizational skills and ability to balance customer projects concurrently with strong verbal, written communication skills and previous experience with customer-facing engagements Special Consideration given for