Director, Digital Consulting | Enterprise Architecture

We need to output HTML fragment with sections: About the role, Responsibilities (WHAT YOU'LL DO), Requirements/Qualifications (QUALIFICATIONS & INTERESTS), Benefits (The Perks), Pay (Estimated Pay Range). Possibly Schedule not present, so omit. Also include maybe a short paragraph for metadata like location? The posting includes location info in the intro: "Trace3 is headquartered in Irvine, California. We employ more than 1,200 people all over the United States. Our major field office locations include Denver, Indianapolis, Grand Rapids, Lexington, Los Angeles, Louisville, Texas, San Francisco." This is not a heading but could be part of About the role? Actually it's company description. The instruction: "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." So we can include a short paragraph about location maybe under About the role? But they said include a section ONLY when posting has real, specific content for it. About the role section exists: "ABOUT THE ROLE:" heading present. So we output

About the role

then content after that heading until next heading "WHAT YOU'LL DO:" etc. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO etc. Also remove navigation/cookie etc. The provided text includes a lot of company culture description before ABOUT THE ROLE. That is not part of the role but maybe we can include as part of About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should map sections accordingly. The posting has "ABOUT THE ROLE:" then description. Then "WHAT YOU'LL DO:" then list. Then "QUALIFICATIONS & INTERESTS:" then list. Then "The Perks" then list. Then "Estimated Pay Range:" then line. Also there is "Actual salary will be based on a variety of factors..." which is part of Pay discussion. We'll include that in Pay section. We need to output only HTML fragment, no /, no markdown fences. We'll produce:

About the role

Trace3 is expanding its team of Enterprise Architecture leaders across complementary specialties; successful candidates may be very deep in one primary domain, such as Security, Cloud, Data, AI, Platform Engineering, Resilience, or Enterprise Applications, while demonstrating the judgment and curiosity to stretch across adjacent domains. In addition to driving account growth, executive relationships, and delivery quality, this Director serves as a technical-continuity owner across the account and as part of a broader architecture bench that collectively covers Trace3’s key domains.The role connects architecture and technology decisions to business strategy and funded outcomes, ensures solution coherence across Cloud, Data, AI, Security, and related domains, and gives Trace3 credibility with CIOs, CTOs, CISOs, architects, and engineering teams. This is a hands-on leadership role: the Director remains close enough to the work to review infrastructure-as-code, platform configurations, and engineering designs directly, stabilize accounts under pressure, and lead through influence, technical judgment, and commercial awareness.

Then Responsibilities:

Responsibilities

• Provide the account's architecture point of view: reference architectures, target-state design, and technology decisions tied to business cases.
• Ensure multi-domain solution coherence and non-functional integrity across engagements.
• Originate and shape technically credible pursuits and multi-domain programs.
• Elevate Trace3's standing with technical executives and engineering stakeholders.
• Operate as part of a complementary Enterprise Architecture team, bringing a distinctive domain spike while collaborating with other architect sub-types to provide full-stack coverage across Trace3’s priority domains.
• Serve as the named Digital Account Lead for assigned flagship and enterprise accounts when designated, or as the senior architecture lead within another Director's account strategy and governance model when a different Digital Account Lead owns the overall client outcome.
• Build and maintain the account strategy, executive relationship plan, stakeholder and initiative maps, engagement history, account roadmap, opportunity priorities, and cross-domain expansion thesis.
• Originate, qualify, shape, and advance pursuits that align to client priorities, Trace3's right-to-win, and available delivery capabilities.
• Orchestrate account, sales, domain, practice, business-unit, partner, and delivery leaders around one integrated account strategy and client experience.
• Maintain sufficient proximity to every active engagement to independently understand delivery health, client sentiment, scope, financial position, major dependencies, risks, solution integrity, and progress toward the business case.
• Bring in peer Directors and specialists when another domain is required. On accounts led by another Director, operate as the domain lead within the named Digital Account Lead's account strategy and governance model.
• Enterprise Architecture and Technical LeadershipOwn account-level architecture continuity: current-state assessment, target-state and reference architectures, technology selection, and non-functional requirements across the Director's primary domain and adjacent Trace3 domains, including Cloud, Data, AI, Security, Platform Engineering, Resilience, Enterprise Applications, and Integration where relevant.
• Review and provide substantive feedback on key technical and architectural areas (or work with SMEs to do so)
• Ensure solutions across engagements to integrate coherently and align to Trace3 well-architected and resilience standards.
• Serve as the senior technical authority in client and internal forums; guide engineers, architects, and practice teams without owning line management of them.
• Connect architecture decisions to business strategy, cost, risk, and measurable outcomes.
• Collaborate with peer Enterprise Architecture Directors to assemble the right architecture team for each account, balancing deep domain expertise with cross-domain integration and commercial relevance.
• Author architecture decision records, reference patterns, and standards as a normal part of the work—capturing the decision, constraints, alternatives, and rationale so the reasoning survives beyond the engagement and the individual.
• Delivery Excellence and Value RealizationChampion delivery quality, governance, risk management, and benefits realization on complex, multi-workstream programs.
• Guide solution quality across transformation initiatives; ensure adoption and value tracking.
• Own escalations and account recovery. Step into engagements that are blocked, degraded, or off-plan—including access and environment failures, platform and integration blockers, delivery or reporting gaps, and disputes over scope, hours, or commercial terms—and drive them to resolution with the client and internal teams.
• People Leadership and Practice MaturityMentor and develop technical consultants and architects; build architecture leverage across the account team.
• Productize the account’s success model. Where an approach or methodology demonstrably works, drive into a documented, transferable playbook that other account teams can adopt without the original author present.
• Contribute reference architectures, accelerators, and frameworks to the relevant product lines and Guilds.

But note some lines are concatenated without punctuation; we should keep as is but maybe split into separate li for each bullet. The original text had headings like "Enterprise Architecture and Technical Leadership" etc. Those are subheadings within responsibilities. We could keep them as li items but maybe better to keep as li with the heading text. However the instruction: Use

• for any list of duties/requirements/benefits. So we should treat each bullet as li. The original had paragraphs with headings inside; we can keep them as li items. We need to ensure we don't lose any content. Let's extract the responsibilities section exactly as posted after "WHAT YOU'LL DO:" until before "QUALIFICATIONS & INTERESTS:". The text: WHAT YOU'LL DO: Provide the account's architecture point of view: reference architectures, target-state design, and technology decisions tied to business cases.Ensure multi-domain solution coherence and non-functional integrity across engagements.Originate and shape technically credible pursuits and multi-domain programs.Elevate Trace3's standing with technical executives and engineering stakeholders.Operate as part of a complementary Enterprise Architecture team, bringing a distinctive domain spike while collaborating with other architect sub-types to provide full-stack coverage across Trace3’s priority domains.Serve as the named Digital Account Lead for assigned flagship and enterprise accounts when designated, or as the senior architecture lead within another Director's account strategy and governance model when a different Digital Account Lead owns the overall client outcome.Build and maintain the account strategy, executive relationship plan, stakeholder and initiative maps, engagement history, account roadmap, opportunity priorities, and cross-domain expansion thesis.Originate, qualify, shape, and advance pursuits that align to client priorities, Trace3's right-to-win, and available delivery capabilities.Orchestrate account, sales, domain, practice, business-unit, partner, and delivery leaders around one integrated account strategy and client experience.Maintain sufficient proximity to every active engagement to independently understand delivery health, client sentiment, scope, financial position, major dependencies, risks, solution integrity, and progress toward the business case.Bring in peer Directors and specialists when another domain is required. On accounts led by another Director, operate as the domain lead within the named Digital Account Lead's account strategy and governance model. Enterprise Architecture and Technical LeadershipOwn account-level architecture continuity: current-state assessment, target-state and reference architectures, technology selection, and non-functional requirements across the Director's primary domain and adjacent Trace3 domains, including Cloud, Data, AI, Security, Platform Engineering, Resilience, Enterprise Applications, and Integration where relevant.Review and provide substantive feedback on key technical and architectural areas (or work with SMEs to do so)Ensure solutions across engagements to integrate coherently and align to Trace3 well-architected and resilience standards.Serve as the senior technical authority in client and internal forums; guide engineers, architects, and practice teams without owning line management of them.Connect architecture decisions to business strategy, cost, risk, and measurable outcomes.Collaborate with peer Enterprise Architecture Directors to assemble the right architecture team for each account, balancing deep domain expertise with cross-domain integration and commercial relevance.Author architecture decision records, reference patterns, and standards as a normal part of the work—capturing the decision, constraints, alternatives, and rationale so the reasoning survives beyond the engagement and the individual. Delivery Excellence and Value RealizationChampion delivery quality, governance, risk management, and benefits realization on complex, multi-workstream programs.Guide solution quality across transformation initiatives; ensure adoption and value tracking.Own escalations and account recovery. Step into engagements that are blocked, degraded, or off-plan—including access and environment failures, platform and integration blockers, delivery or reporting gaps, and disputes over scope, hours, or commercial terms—and drive them to resolution with the client and internal teams.People Leadership and Practice MaturityMentor and develop technical consultants and architects; build architecture leverage across the account team.Productize the account’s success model. Where an approach or methodology demonstrably works, drive into a documented, transferable playbook that other account teams can adopt without the original author present.Contribute reference architectures, accelerators, and frameworks to the relevant product lines and Guilds. We need to split into sensible li items. Could split at each period that starts a new capitalized phrase? But we can just make one big li? That would lose structure. Better to split at each sentence that starts with a capital letter after a period. However there are some run-ons like "Enterprise Architecture and Technical LeadershipOwn account-level..." missing space. We'll just keep as is but maybe add a space. Given the instruction to preserve ALL substantive information, we can keep the exact text as a single

  under Responsibilities? But they said use

  • for any list of duties/requirements/benefits. The responsibilities are a list of duties, so we should use
    • . We can break at each distinct duty indicated by a capital letter after a period. Let's attempt to manually split: 1. Provide the account's architecture point of