Presales- Sr. Enterprise Architect

We need to output HTML fragment with sections: About the team, About the role, Responsibilities, About You (maybe split into Basic Qualifications, Other Qualifications). Use

for headings. Use

• for lists. Use

  for prose. Remove boilerplate like EEO, etc. Also remove application instructions, referral, etc. Keep substantive info. We need to preserve all substantive info: The opening paragraph about culture, mission, etc. That is part of job description. Should we include that? It's not a heading but prose. We can put it in a

  before sections. We need sections only when there is real specific content. We have: - About The Team (content) - About The Role (content) - Responsibilities Include: (list) - About You (contains Basic Qualifications, Principal Enterprise Architect qualifications, Other Qualifications) - Workday Pay Transparency Statement (pay ranges) - Our Approach to Flexible Work (schedule/flexibility) - Possibly Benefits? Not explicit benefits listed; only mention of total compensation package includes bonus, stock grants. Could we create Benefits section? The instruction: only create Benefits if posting actually states them. It mentions "total compensation package, this role may be eligible for the Workday Bonus Plan or a role-specific commission/bonus, as well as annual refresh stock grants." That's compensation, not benefits like health. Might be considered part of Pay? But we have Pay section already. We could include that in Pay section. However we already have Pay Transparency Statement with ranges. Could add note about bonus/stock. But we must not invent. We can include that as part of Pay section prose. - Schedule: Flexible work description. So we can create a Schedule section with that content. - Benefits: Not explicit; we might skip. - Also there is "Workday Pay Transparency Statement" which we can treat as Pay section. - Also there is "Primary Location: USA.TX.Home Office" etc. That's location metadata; we can fold into a short

  maybe under About the Role or separate? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is minor metadata; we can include a short

  maybe after About the Role. We must not repeat job title as heading. We must not include boilerplate like EEO, accommodation, referral, scam warning, etc. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  Intro paragraph about culture.

  About The Team

  Content...

  About The Role

  Content about role (what will you do?) maybe combine with responsibilities? Actually "About The Role" includes "What will you do?" paragraph. Then responsibilities list separate. We'll put the "What will you do?" paragraph in

  under About The Role. Then responsibilities list as

  • ... each bullet. We have responsibilities bullet list: - Leading strategic, complex, platform opportunities. This involves architecting technology solution strategies that achieve customer objectives. - Identifying and analyzing key systems, dependencies, and integration points within the overall solution landscape, developing solution maps. - Providing expert guidance to sales and deal teams on how to differentiate with Workday technology. - Collaborating across functional groups (Value Management, Services, Customer Success Management) to create customer experiences that build long-term, sustainable relationships. - Ability to travel up to 50% of the time - Sponsorship is not available for this role. We need to keep all. Then

    About You

    maybe we split into Basic Qualifications and Other Qualifications as subheadings? But instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid using other headings like Basic Qualifications? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could use

    for Basic Qualifications and Other Qualifications as they are qualifications. Or we could combine under a single

    About You

    and then use
    for lists. Probably better to have

    About You

    then sublists. But we have two tiers: Basic Qualifications (with two levels: Sr. Enterprise Architect and Principal Enterprise Architect) and Other Qualifications (list). We could present as:

    About You

    The ideal candidate has strong sales consulting experience ...

    Basic Qualifications

    but we cannot use h4? Not prohibited but instruction only mentions h3 for section headings. Using h4 might be okay but safer to stick to h3 only. Could treat Basic Qualifications as a

    section and Other Qualifications as another

    . But then we would have multiple headings under About You? Might be okay. Alternatively, we can keep About You as

    and then use

    for Basic Qualifications and Other Qualifications with
    • items that contain the detailed text. That would preserve info. Let's extract Basic Qualifications text: "Sr. Enterprise Architect 5+ years Enterprise Software Solution Consulting experience or hands-on experience supporting enterprise software applications. 5+ years delivering compelling presentation both in person and virtual meetings, effectively communicating technical concepts and strategic initiatives 5+ years applied working knowledge of cloud architecture, security, reporting, and integration standards. 1+ years experience with AI technology solutions to design and deliver tailored demos, proofs of concept, and presentations that address prospective customers' business needs. Principal Enterprise Architect 7+ years Enterprise Software Solution Consulting experience or hands-on experience supporting enterprise software applications. 7+ years delivering compelling presentation both in person and virtual meetings, effectively communicating technical concepts and strategic initiatives 7+ years applied working knowledge of cloud architecture, security, reporting, and integration standards. 5+ years experience with Workday or partner deployment, architecture/integrations 2+ years experience with AI technology solutions to design and deliver tailored demos, proofs of concept, and presentations that address prospective customers' business needs." Other Qualifications list: - Bringing a point of view and influencing decision making. - Multi-pillar Solution and Product Knowledge. - Executive Presence and Relationship Building. - Collaborative and Team-Oriented. - Innovative and Adaptable. We'll put these as
      • . Now Pay section: We have Workday Pay Transparency Statement with ranges. We'll create

        Pay

        and include prose with ranges and mention bonus/stock. Schedule section:

        Schedule

        with flexible work description. We also have location info: "Primary Location: USA.TX.Home Office Primary Location Base Pay Range: $138,600 USD - $208,000 USD Additional US Location(s) Base Pay Range: $138,600 USD - $208,000 USD Additional Considerations: If performed in Colorado, the pay range for this job is $138,600 USD - $208,000 USD based on min and max pay range for that role if performed in CO. The application deadline for this role is the same as the posting end date stated as below: 10/09/2026" We can fold location and deadline into a short

        maybe under About The Role or separate. Since it's minor metadata, we can include a

        after About The Role before Responsibilities? Or we can include a

        under About The Role after the "What will you do?" paragraph. We must not include application deadline as heading; just include in prose. We must not include boilerplate like EEO, accommodation, referral, scam warning, etc. Remove those. Now produce HTML. Let's craft:

        Your work days are brighter here. We’re obsessed with making hard work pay off, for our people, our customers, and the world around us. As a Fortune 500 company and a leading AI platform for managing people, money, and agents, we’re shaping the future of work so teams can reach their potential and focus on what matters most. The minute you join, you’ll feel it. Not just in the products we build, but in how we show up for each other. Our culture is rooted in integrity, empathy, and shared enthusiasm. We’re in this together, tackling big challenges with bold ideas and genuine care. We look for curious minds and courageous collaborators who bring sun-drenched optimism and drive. Whether you're building smarter solutions, supporting customers, or creating a space where everyone belongs, you’ll do meaningful work with Workmates who’ve got your back. In return, we’ll give you the trust to take risks, the tools to grow, the skills to develop and the support of a company invested in you for the long haul. So, if you want to inspire a brighter work day for everyone, including yourself, you’ve found a match in Workday, and we hope to be a match for you too.

        About The Team

        As a member of our diverse and skilled North America Presales team, you will have the opportunity to communicate and demonstrate the power of Workday's applications to prospects and customers alike. It is this team's job to bring the value of Workday solutions to life and showcase how the world of work can be transformed. Along with working closely with our sales counterparts, this team also sits at the exciting intersection of our Product Management, Consulting Services, Marketing, and Value Management teams, providing exposure to various areas of the business.

        About The Role

        In this role, you will serve as a trusted advisor to Workday customers and prospects, crafting the overall solution strategy to achieve their business objectives. With Professional Services expertise and understanding of enterprise SaaS solutions, you will establish yourself as a leader with a valued point of view.

        Primary Location: USA.TX.Home Office. Additional US locations share the same base pay range. Application deadline: 10/09/2026.

        Responsibilities

        • Leading strategic, complex, platform opportunities. This involves architecting technology solution strategies that achieve customer objectives.
        • Identifying and analyzing key systems, dependencies, and integration points within the overall solution landscape, developing solution maps.
        • Providing expert guidance to sales and deal teams on how to differentiate with Workday technology.
        • Collaborating across functional groups (Value Management, Services, Customer Success Management) to create customer experiences that build long-term, sustainable relationships.
        • Ability to travel up to 50% of the time.
        • Sponsorship is not available for this role.

        About You

        The ideal candidate has strong sales consulting experience in business applications, enterprise data and AI, coupled with a deep understanding of the Professional Services industry. You are adept at translating business needs into technology solutions. Your exceptional communication and relationship-building skills enable you to engage effectively with C-level executives.

        Basic Qualifications

        • Sr. Enterprise Architect: 5+ years Enterprise Software Solution Consulting experience or hands-on experience supporting enterprise software applications.
        • 5+ years delivering compelling presentation both in person and virtual meetings, effectively communicating technical concepts and strategic initiatives.
        • 5+ years applied working knowledge of cloud architecture, security, reporting, and integration standards.
        • 1+ years experience with AI technology solutions to design and deliver tailored demos, proofs of concept, and presentations that address prospective customers' business needs.
        • Principal Enterprise Architect: 7+ years Enterprise Software Solution Consulting experience or hands-on experience supporting enterprise software applications.
        • 7+ years delivering compelling presentation both in person and virtual meetings, effectively communicating technical concepts and strategic initiatives.
        • 7+ years applied working knowledge of cloud