Technical Architect – AI & Agentic Solutions Delivery

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: - "Our Company" description: about Hitachi Digital Services. Could be "About the role"? Actually "Our Company" is about the company. Could be "About the role"? Not exactly. There's "Job Description" with bullet points (though not bullet list but paragraphs). There's "What You Will Be Doing" (responsibilities). There's "What You Bring To The Team" (requirements/qualifications/skills). There's "About Us" (company description again). There's "How we look after you" (benefits). There's also mention of flexible arrangements, life balance, etc. There's no explicit Pay or Schedule specifics. So we should not create Pay or Schedule sections. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, equal-opportunity, scam-warning, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's parse content: Sections: - "Our Company" (intro about Hitachi Digital Services). Could be "About the Company" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the role" maybe fits company overview? But maybe we can use "About the role" for the company description? However "About the role" is usually about the job role. The posting includes "Job Description" then "Meet Our Team:" etc. That could be considered role description. Could treat "Job Description" as "About the role". But we have also "What You Will Be Doing" (responsibilities). And "What You Bring To The Team" (requirements). And "How we look after you" (benefits). Also "About Us" maybe duplicate of company description; we could merge. We need to decide which headings to use. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings if appropriate. We should not invent headings not in that list. So we must only use those headings. So we need to map content to those headings. Thus we can have sections: - About the role: could contain the introductory description about the role/team: "Meet Our Team: Join a leadership team driving enterprise-scale AI, GenAI, Agentic AI, Physical AI, IoT, Cloud, and Digital Transformation initiatives for customers in asset-heavy industries such as Energy, Rail, and Manufacturing. Serve as a trusted advisor to business and technology stakeholders, leading architecture discussions, solution workshops, and executive-level engagements. Work with globally distributed architects and engineering teams to deliver innovative, scalable, secure, and business-critical solutions. Help shape technology strategy, governance, architecture standards, and adoption of emerging technologies across large transformation programs." That seems like role overview. - Responsibilities: "What You Will Be Doing" bullet points (though they are sentences). We'll put as

  • . - Requirements: maybe "What You Bring To The Team" includes experience, skills, etc. Could split into Requirements and Qualifications and Skills. But we have separate headings for Requirements, Qualifications, Skills. We need to decide if we should split. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine into one section like Requirements (or Qualifications). But we have to use headings from list; we can choose to use only Requirements and maybe Skills. However we have to include all substantive info. We could put all under Requirements (or Qualifications). But we also have Skills heading available; we could separate technical skills list under Skills. The "Must-have technical skills:" list is a list of skills. So we could have a Skills section for that. The "Required industry experience:" etc could be Requirements. The "15+ years of solution architecture..." could be Qualifications. But to avoid many thin sections, we could combine Qualifications and Requirements into one section called Requirements (or Qualifications). But we need to follow the allowed headings; we can choose either. Let's think: The posting includes: - 15+ years of solution architecture, technology leadership, and enterprise delivery experience, with proven success leading large-scale AI, cloud, platform, or digital transformation programs. (Experience/qualification) - Strong customer-facing experience with the ability to influence executive stakeholders, lead global teams, mentor talent, and drive strategic initiatives. (Skill/qualification) - Must-have technical skills: AI, Generative AI, Agentic AI, Physical AI, Machine Learning, Intelligent Automation, LLMs, RAG, Multi-Agent Architectures, AI Orchestration Frameworks, MLOps, IoT/IIoT, Edge Computing, Cloud Platforms (AWS/Azure/GCP), Microservices, APIs, Distributed Systems, Kubernetes, Containers, DevOps, Security, Integration, and Enterprise Architecture. (Skills) - Required industry experience: Delivery experience within asset-heavy industries such as Energy, Rail, or Manufacturing. Experience with HPC (CUDA, ROCm, Weka, GPFS), NVIDIA technologies, and Computer Vision models (CNNs, YOLO, ViTs, VLMs) is highly preferred. (Industry experience/requirement) Thus we could have: - Qualifications: the 15+ years experience and strong customer-facing experience. - Skills: the technical skills list. - Requirements: maybe industry experience? But we could also put industry experience under Qualifications. However we have separate headings; we could use Requirements for industry experience and maybe also include the 15+ years? But that would split. Given "Prefer a few substantive sections over many thin ones", maybe we combine Qualifications and Requirements into one section called Requirements (or Qualifications). But we still have Skills separate. That yields two sections: Requirements and Skills. Plus About the role, Responsibilities, Benefits. That's four sections. We also have Benefits: "How we look after you" includes industry-leading benefits, support, services, flexible arrangements, life balance, sense of belonging, autonomy, freedom, ownership, etc. Also mention of equal opportunity employer etc which we should remove as boilerplate. So we keep the benefits description. Thus sections:

    About the role

    with paragraph(s) from "Our Company" and maybe "Job Description" intro? Actually "Our Company" is about the company, not role. But we can treat as about the role because it's describing the company and the role's context. The "Job Description" includes "Meet Our Team:" etc which is also role overview. We'll combine.

    Responsibilities

    with
    • items from "What You Will Be Doing".

      Requirements

      with paragraph(s) covering 15+ years experience, strong customer-facing experience, required industry experience (including HPC, NVIDIA, Computer Vision). Could be

      for prose and maybe

      • for list? The industry experience could be list.

        Skills

        with
        • for technical skills list.

          Benefits

          with paragraph(s) from "How we look after you" (excluding EEO boilerplate). Also maybe mention flexible arrangements, life balance, sense of belonging, autonomy, freedom, ownership. We must not include Pay or Schedule sections. We must not include duplicated lines. Ensure we preserve all substantive info. Let's extract exact text. From posting: "Our Company We're Hitachi Digital Services, a global digital solutions and transformation business with a bold vision of our world's potential. We're people-centric and here to power good. Every day, we future-proof urban spaces, conserve natural resources, protect rainforests, and save lives. This is a world where innovation, technology, and deep expertise come together to take our company and customers from what's now to what's next. We make it happen through the power of acceleration. Imagine the sheer breadth of talent it takes to bring a better tomorrow closer to today. We don't expect you to 'fit' every requirement – your life experience, character, perspective, and passion for achieving great things in the world are equally as important to us." That's the company intro. Then "Job Description Meet Our Team: Join a leadership team driving enterprise-scale AI, GenAI, Agentic AI, Physical AI, IoT, Cloud, and Digital Transformation initiatives for customers in asset-heavy industries such as Energy, Rail, and Manufacturing.Serve as a trusted advisor to business and technology stakeholders, leading architecture discussions, solution workshops, and executive-level engagements.Work with globally distributed architects and engineering teams to deliver innovative, scalable, secure, and business-critical solutions.Help shape technology strategy, governance, architecture standards, and adoption of emerging technologies across large transformation programs." Note there are no spaces after periods; but we can add spaces for readability but must preserve info. We'll keep as is but maybe add spaces for readability; not altering meaning. Then "What You Will Be Doing Define end-to-end architecture for AI, GenAI, Agentic AI, Physical AI, IoT, Cloud, and Digital Transformation solutions.Lead technical delivery from strategy through implementation, ensuring quality, scalability, security, governance, and successful business outcomes.Drive architecture reviews, technology standards, best practices, and enterprise-wide adoption of emerging technologies.Mentor architects and engineering teams while leading customer workshops, executive discussions, and cross-functional delivery efforts." Then "What You Bring To The Team 15+ years of solution architecture, technology leadership, and enterprise delivery experience, with proven success leading large-scale AI, cloud, platform, or digital transformation programs.Strong customer-facing experience with the ability to influence executive stakeholders, lead global teams, mentor talent, and drive strategic initiatives.Must-have technical skills: AI, Generative AI, Agentic AI, Physical AI, Machine Learning, Intelligent Automation, LLMs, RAG, Multi-Agent Architectures, AI Orchestration Frameworks, MLOps, IoT/IIoT, Edge Computing, Cloud Platforms (AWS/Azure/GCP), Microservices, APIs, Distributed Systems, Kubernetes, Containers, DevOps, Security, Integration, and Enterprise Architecture.Required industry experience: Delivery experience within asset-heavy industries such as Energy, Rail, or Manufacturing. Experience with HPC (CUDA, ROCm, Weka, GPFS), NVIDIA technologies, and Computer Vision models (CNNs, YOLO, ViTs, VLMs) is highly preferred." Then "About Us We're a global, team of innovators. Together, we harness engineering excellence and passion to co-create meaningful solutions to complex challenges. We turn organizations into data-driven leaders that can make a positive impact on their industries and society. If you believe that innovation can bring a better tomorrow closer to today, this is the place for you." Then "Fostering innovation through diverse perspectives Hitachi is a global company operating across a wide range of industries and regions. One of the things that sets Hitachi apart is the diversity of our business and people, which drives our innovation and growth. We are committed to building an inclusive culture based on mutual respect and merit-based systems. We believe that when people feel valued, heard, and safe to express themselves, they do their best work." Then "How we look after you We help take care of your today and tomorrow with industry-leading benefits, support, and services that look after your holistic health and wellbeing. We're also champions of life balance and offer flexible arrangements that work for you (role and location dependent). We're always looking for new ways of working that bring out our best, which leads to unexpected ideas. So here, you'll experience a sense of belonging, and discover autonomy, freedom, and ownership as you work alongside talented people you enjoy sharing knowledge with." Then EEO boilerplate etc