Jobs · Virginia

Identity Graph Architect, Senior Consultant

Deloitte · Richmond, VA · Yesterday
Hybrid$111k–$218k/yrFull-time
The user has provided a job posting that appears to contain two distinct roles merged together: an Identity Graph Architect role and an Adobe Journey Optimizer (AJO) Senior Consultant role. I need to parse this carefully and create a clean HTML fragment that represents the content appropriately. Looking at the content, there are clearly two separate job postings concatenated: 1. First role: Identity Graph Architect (with recruiting end date Jan 22, 2027) 2. Second role: Senior Consultant supporting Adobe Journey Optimizer (AJO) (with recruiting end date Dec 18, 2026) The user wants me to reformat into clean semantic HTML. Since this appears to be two separate roles in one posting, I should probably structure it to reflect both roles clearly. However, the instructions say "reformat a job posting" (singular). But the content clearly has two distinct roles. I think the best approach is to create sections for each role, perhaps with a clear separation. Since the page already shows the job title (per instructions: "Do NOT repeat the job title as a heading (the page already shows it)"), but there are two titles here. I'll need to handle this carefully. Let me analyze each role's content: **Role 1: Identity Graph Architect** - About the role: Description of Deloitte Customer team and the role - Work you'll do: List of responsibilities (Identity Graph Management, Data Collection Architecture, Use Case Development, Traceability, Quality Monitoring, Privacy and Compliance, Collaboration, Documentation and Specifications, Stakeholder Engagement, Innovation) - Skills: List of soft skills - The Team: Description of Advertising, Marketing and Commerce team - Qualifications Required: List of required qualifications - Qualifications Preferred: List of preferred qualifications **Role 2: Senior Consultant - Adobe Journey Optimizer (AJO)** - About the role: Description of role - Work you'll do: List of responsibilities - Skills: List of soft skills (same as first role) - The team: Description of team (similar to first role) - Qualifications Required: List of required qualifications - Qualifications Preferred: List of preferred qualifications - Pay: Partial sentence about wage range (cut off) The pay section for the second role is incomplete: "The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training;" Since it's incomplete and doesn't give actual pay info, I should not include a Pay section per instructions: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Also need to remove: "Recruiting for this role ends on January 22, 2027" and "Recruiting for this role ends on December 18, 2026" - these are metadata dates, fold into a short

or drop. I'll include as a brief note. Also need to remove duplicate "A successful candidate would possess these skills:" sections (they appear identical for both roles). Now, structure: Since there are two distinct roles, I'll create a structure that separates them clearly. Perhaps use for each role? But instructions say use

for section headings. I could use

for each role's major sections. But the instructions say: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings. Given two roles, I might need to label each role's sections. Perhaps:

Identity Graph Architect

- but instructions say "Do NOT repeat the job title as a heading (the page already shows it)". However, there are two titles. The page might show one title? The user didn't specify. I think I should not include the job titles as headings. Alternative: Since it's one posting with two roles, maybe the page shows both titles? I'll assume the page shows the titles, so I won't repeat them. I'll structure as: For each role, have sections: About the role, Responsibilities, Skills, Team, Qualifications (Required), Qualifications (Preferred). But "Qualifications" is a heading, and "Required" and "Preferred" could be sub-lists under it. Better: Use

for "Qualifications" and then have two
    with labels? Or use

    ? Instructions only mention

    for section headings. I'll use

    for "Qualifications" and then within that, have paragraphs or lists for required and preferred. But the example headings include "Requirements" and "Qualifications" as separate. I'll use "Qualifications" as heading and then list required and preferred. Also "Skills" appears as a heading for soft skills. Let me draft. First, I'll create a wrapper? No, output only HTML fragment, no /. So just a series of elements. I'll start with a brief intro paragraph for the posting metadata (recruiting end dates) maybe. Then for each role, I'll group sections. But the instructions: "Prefer a few substantive sections over many thin ones." So maybe combine some. Let's outline:

    Recruiting for the Identity Graph Architect role ends January 22, 2027. Recruiting for the Senior Consultant (Adobe Journey Optimizer) role ends December 18, 2026.

    Then for Identity Graph Architect:

    About the role

    Our Deloitte Customer team empowers organizations to build deeper relationships with customers through innovative strategies, advanced analytics, Generative AI, transformative technologies, and creative design. We enhance customer experiences and drive sustained growth and customer value creation and capture through customer and commercial strategies, digital products and innovation, marketing, commerce, sales, and service. We are a team of strategists, data scientists, operators, creatives, designers, engineers, and architects. Our team balances business strategy, technology, creativity, and ongoing managed services to solve the biggest problems that affect customers, partners, constituents, and the workforce.

    An Identity Graph Architect is responsible for designing, implementing, and optimizing enterprise-level identity resolution solutions that enable a unified view of the customer across all data touchpoints. Key responsibilities include maintaining and evolving the identity graph, designing identity resolution inputs and data collection, collaborating with identity partners, and supporting traceability and data quality for identity outputs. The role requires deep expertise in identity resolution, data architecture, and cross-functional stakeholder engagement.

    Responsibilities

    • Identity Graph Management: Help maintain and evolve the identity graph in collaboration with identity partners to optimize identity matching logic and resolution accuracy
    • Data Collection Architecture: Design data collection strategies using tagging solutions to feed high-quality data into the identity graph
    • Use Case Development: Gather and translate business use cases for the identity graph into scalable technical architectures and solutions
    • Traceability: Support linking identity resolution outputs back to source data so identities and attributes can be traced to their origin
    • Quality Monitoring: Help build reporting and monitoring into the identity graph to flag data anomalies, match mismatches, and oversized clusters
    • Privacy and Compliance: Partner with legal and compliance teams to ensure identity data handling meets applicable U.S. privacy requirements
    • Collaboration: Work closely with stakeholders across product, marketing, analytics, and engineering teams to align on data strategy, solution design, and implementation priorities
    • Documentation and Specifications: Create technical specifications to drive development of solutions and deliver documentation for stakeholder review
    • Stakeholder Engagement: Interface with clients and internal teams to gather requirements, map solutions, and make recommendations
    • Innovation: Continuously identify opportunities to improve customer data capabilities and innovate on solutions to address evolving business needs

    Skills

    • Ability to work independently and collaborate as part of a team
    • Effective written and verbal communication skills
    • Meticulous attention to detail and quality of work product
    • Ability to build and sustain professional relationships
    • Ability to lead projects or workstreams
    • Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment
    • Strong interpersonal skills and professional demeanor
    • Ability to meet deadlines
    • Ability to provide clear guidance to others

    Team

    Deloitte's Advertising, Marketing and Commerce team creates content and experiences that inspire action. We design and implement technology platforms for personalized marketing across all digital touchpoints, specializing in customer-centric B2B and B2C solutions. Our in-house agency engages customers throughout their journey, working on projects like AdTech, MarTech, campaign automation, CRM, and lead-to-loyalty orchestration. Join us to drive impactful customer interactions and business growth.

    Qualifications

    Required

    • 5+ years of experience in data architecture, customer data platforms, or identity resolution solutions
    • 3+ years of experience working with identity graph technologies or identity resolution platforms (e.g., Acxiom, LiveRamp, or similar)
    • 5+ years of in-depth understanding of database platforms including relational and non-relational data engines (MS SQL, MySQL, PostgreSQL, MongoDB, Snowflake, BigQuery, Redshift, and similar)
    • 5+ years of experience with data processing (ETL) tools and methodologies
    • 3+ years of experience designing customer-centric datasets (i.e., CRM, Call Center, Marketing, Offline, Point of Sale, etc.)
    • 3+ years of data modeling experience
    • Limited immigration sponsorship may be available
    • Ability to travel up to 50% on average based on the work you do and the clients and industries/sectors you serve

    Preferred

    • Experience and knowledge with digital marketing analytics and media operations
    • Experience with marketing cloud solutions and customer data platforms
    • Experience with data observability or anomaly detection tooling
    • Familiarity with U.S. privacy and data protection requirements as they apply to identity data, including federal requirements for government data
    • Experience in programming languages (Python, Java, or Bash scripting)
    • Experience with Big Data technologies (i.e., Hadoop, Spark, Redshift, Snowflake, Hive, etc.)
    • Experience with Martech/Adtech tools and how to integrate technologies into the data management solution (Adobe, Salesforce, Oracle, Google, and similar)
    • Experience in advanced analytics, machine learning concepts, and use cases applied to customer experience and marketing solutions
    • Excellent interpersonal skills and the ability to articulate complex technology concepts with technical and non-technical individuals
    • Ability to approach technical solutions to challenges from a business perspective
    • Understanding of the full SDLC process
    • Understanding of data integration methodologies and tools (Mulesoft, Dell Boomi, Custom API, Segment, Tealium, and similar)
    • Understanding of public cloud offerings and how to design solutions built around these technologies (AWS, Azure, Google Cloud Platform, and similar)
    • Degree in Computer Science, Information Systems, Data Science, or related field
    • Experience working with public cloud offerings (AWS, Azure, Google Cloud Platform, and similar)
    • GCP (Cloud Functions, Composer, SQL, Storage, Dataproc, Datastore, Kubernetes, BigQuery, Stackdriver, Pub/Sub)
    • AWS (Lambda, Glue, Data Pipeline, Redshift, Aurora, Athena/Spectrum, S3/Glacier

Similar jobs