Enterprise Architect
- list of values. That's specific content. So we keep.
We must not repeat job title as heading. The page already shows it, so we don't add heading for job title.
We must not put Job ID/requisition numbers as headings; none present.
We need to include sections only when posting has real specific content. So we will have sections: About the role (maybe combine Who We Are and Position Summary?), Responsibilities (Key Responsibilities + Essential Responsibilities?), Requirements (Minimum Qualifications + Preferred Experience?), Skills (Capabilities?), Benefits? There's salary range, so we can have Pay section. Benefits? Not mentioned besides salary. So we may not include Benefits unless there is info. There's no explicit benefits besides salary. So we omit Benefits.
Schedule? Not mentioned. So omit.
We need to use
for section headings. We need to use
- for any list of duties/requirements/benefits, and
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We need to avoid duplication: there are overlapping responsibilities (Key Responsibilities and Essential Responsibilities). We should combine them without losing detail. But we must preserve all substantive information; we can merge but must not lose any detail. We'll need to include all bullet points from both sections. Similarly for qualifications: Minimum Qualifications and Preferred Experience. We also have "Capabilities" list under Minimum Qualifications? Actually after Minimum Qualifications there is a list of capabilities (Collaboration & Communication etc). Those are likely part of qualifications/skills. We'll treat them as Skills section. We also have "Physical & Mental Requirements" which we should include maybe as a section "Requirements"? But we already have Requirements for qualifications. Could make a separate section "Physical & Mental Requirements". That's specific content. We also have "OUR VALUES" list. We also have salary range. We need to avoid headings with filler like "commensurate with experience". Not present. Now craft HTML. Structure:
About the role
Who We Are ODW Logistics is a people-focused and customer-driven third-party logistics (3PL) provider committed to delivering seamless end-to-end supply chain solutions. Our extensive range of services include supply chain design and innovation, warehousing, efficient distribution and fulfillment, freight brokerage, transportation management, and specialized e-commerce fulfillment solutions.
Position Summary ODW Logistics is seeking a hands-on enterprise level senior application, data, and AI architect to support IT leadership in advancing the company's enterprise architecture, analytics strategy, and AI adoption initiatives. The architect will lead architecture reviews, evaluating emerging technologies, supply chain enterprise applications, data platforms and AI-enabled solutions. They will also help establish architecture standards, governance, and technology roadmaps. This role is ideal for a highly skilled architect who combines enterprise architecture, solution architecture, data architecture, and hands-on AI engineering capabilities. The successful candidate will help guide ODW's evolution toward a modern, AI-enabled enterprise powered by enterprise data governance, intelligent automation, and advanced analytics, while supporting the modernization of core operational platforms including WMS, TMS, HR, Finance, and customer-facing systems. The role will serve as a key technical advisor for new projects, technology evaluations, architecture reviews, strategic system, data and AI initiatives.
Then maybeIdeal Candidate Profile
with list. But we could combine Ideal Candidate Profile into Requirements/Skills. However it's specific content; we can keep as a section. We need to use- for any list. So for Ideal Candidate Profile we have bullet points: Strategic Thinker, Effective Communicator, Collaborative Partner, Pragmatic Innovator, Continuous Learner. We'll list each.
Then
Key Responsibilities
combine Key Responsibilities and Essential Responsibilities. We need to list each bullet. Key Responsibilities bullet list: - Drive Strategy & Execution: Support the overarching enterprise architecture strategy while remaining actively hands-on. - Lead Innovation: Conduct Proof of Concepts (PoCs) for technology evaluations and oversee rigorous architecture reviews. - Design Advanced Solutions: Architect modern application ecosystems, data platforms, and AI-enabled solutions. - Foster Collaboration: Partner effectively with business leadership and technical teams to bridge the gap between vision and execution. - Standardize & Modernize: Champion technical simplification, modernization, and standardization across the entire IT landscape. - Shape the Future: Actively build and refine ODW's future-state application, data, analytics, and AI capabilities. Essential Responsibilities bullet list (longer): - Architect and govern ODW's future-state technology, data, and AI platforms while leading delivery of scalable enterprise solutions that drive business transformation, modernization, and operational excellence supporting operations, warehouse management, transportation, HR, finance, and customer systems. - Evaluate emerging technologies and vendors for strategic alignment. - Drive application modernization, platform rationalization, technical debt reduction, and architecture simplification. - Develop architecture guidance, design patterns, and best practices across the organization. - Translate business requirements into scalable, supportable technology solutions. - Create solution architectures, integration designs, technical roadmaps, and implementation plans. - Build scalable lakehouse, data warehouse, semantic model, and real-time data platforms that support analytics and AI workloads. - Develop business ontologies, semantic models, knowledge graphs, and AI-ready data architectures. - Establish security, compliance, metadata, lineage, and information governance standards. - Lead the design and implementation of AI solutions utilizing leading tools like Copilot, Azure OpenAI, RAG, Semantic Search, Data Agents, AI Agents, and intelligent automation. - Evaluate emerging data technologies and recommend architecture, reliability, performance, and cost improvements that support ODW's analytics strategy and business growth. We'll combine them, preserving all. ThenMinimum Qualifications
list. Minimum Qualifications bullet list: - Bachelor's degree in Computer Science, Information Systems, AI/ML, Data Engineering, Business Analytics, or a related field, or an equivalent combination of education and relevant experience. A graduate degree in relevant field will be preferred. - 7+ years of experience in enterprise solution development and application architecture, specializing in integrating AI capabilities into large-scale systems and navigating the critical success factors of enterprise AI adoption. - Experience evaluating and implementing modern cloud, enterprise applications, data, analytics, and AI technologies. - Experience supporting cross-functional business and technology transformation programs. - Experience designing scalable, secure, maintainable application, data and AI solutions that balance current delivery needs with long-term architecture and reuse. Then maybeCapabilities
list (these are under Minimum Qualifications but could be Skills). We'll treat as Skills. Capabilities bullet list: - Collaboration & Communication: Ability to translate business and system requirements into technical designs and communicate effectively with Systems Analysts, BI developers, application teams, infrastructure teams, vendors, and non-technical stakeholders. - Systems Thinking & Problem-Solving: Connects source-system behavior, integration patterns, data architecture design, semantic models, and business processes to solve complex business problems. - Business Acumen: Learns operational processes and translates business priorities into pragmatic technical solutions that improve decision-making and customer outcomes. - Communication & Collaboration: Builds productive partnerships across technical and non-technical teams, explains tradeoffs clearly, and documents decisions and support procedures effectively. - Execution & Continuous Improvement: Manages competing priorities, delivers dependable solutions, standardizes repeatable practices, and continuously improves performance, quality, and cost. Note there is duplication of Communication & Collaboration appears twice? Actually first is Collaboration & Communication, later Communication & Collaboration. They are similar but we keep both as they appear. ThenPreferred Experience
list: - Experience in hybrid cloud environment and MS-Azure/Fabric technologies. - Experience in third-party logistics, warehousing, transportation, supply chain, or another high-volume operational environment. - Familiarity with Agile delivery and work-management platforms such as Jira, ServiceNow, or GitHub. - Successful track record of deploying agentic AI capabilities in business enterprises. ThenPhysical & Mental Requirements
list: - Hear, read and comprehend, write, and communicate - Continuously sit, type, and perform repetitive wrist motion - Occasionally stand, walk, bend, squat/kneel, twist/turn or reach - Focus (with or without corrective lenses) to see close and distant, along with depth perception capabilities ThenOur Values
list: - Respect | Give and it will be given. We treat others as we want to be treated. We cannot control events, but we can control our response. We build respect through honesty, fairness, and integrity. - Trust | Earned over time. We do what we say we will do. We are clear, direct, and honest. We seek to understand and be understood. - Team | Accomplish more together. We work hard toward a common goal. We desire to make everyone successful. We achieve the best results as a team. - Opportunity | Realize your potential. We believe all people have significance and potential. We understand work and life are integrated and we value both. We strive to make an impact in the world around us. ThenPay
with salary range. We need to usefor prose,
- for lists. We must not include any extra text outside HTML fragment. Let's craft final HTML. Check for any duplicated lines: we have combined. Make sure we didn't include boilerplate like "EQUAL OPPORTUNITY EMPLOYER". We omitted. Also omitted "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That appears twice; it's boilerplate? It's about accommodations; could be considered legal boilerplate. The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. This is about reasonable accommodations, which is part of EEO? Might be considered legal. Safer to remove. We'll omit those sentences. Also we omitted "Physical & Mental Requirements While performing the duties of this job, the employee requires the ability to:" we kept the bullet list but removed the introductory sentence. That's okay. We also omitted "The physical demands herein are representative of those that must be met by an employee to successfully perform the essential functions of this job." That's boilerplate; remove. We also omitted "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." (duplicate). Remove. Now ensure we kept all substantive info: The values list we kept. The salary range we kept. Check if any other substantive info
- for any list. So for Ideal Candidate Profile we have bullet points: Strategic Thinker, Effective Communicator, Collaborative Partner, Pragmatic Innovator, Continuous Learner. We'll list each.
Then
- for any list of duties/requirements/benefits, and