Principal Systems Architect - Marketing Technology
Caterpillar Inc. · Chicago, IL · 1 mo ago
Information Technology$159k–$259k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Job Summary" and "What You Will Do", "What You Will Have", "Considerations For Top Candidates", "Summary Pay Range", "Benefits". Also "Career Area Technology, Digital and Data" maybe not needed. We must not repeat job title. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Remove boilerplate: EEO, etc. Also remove "Any offer of employment is conditioned upon the successful completion of a drug screen." That's boilerplate? Might be considered legal; remove. Also remove "Visa Sponsorship is not available for this position." Might be considered requirement? It's a condition; but maybe keep? It's not a benefit/duty; it's a note. Probably remove as boilerplate. Also remove "Posting Dates". Remove "Please note that salary is only one component of total compensation". Might be considered boilerplate; but we need to preserve substantive info: Pay Range. Keep that line. Also "Compensation and benefits offered may vary depending on multiple individualized factors..." Might be considered boilerplate; but we can keep as part of Pay section? Might be considered filler. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states Pay Range and Benefits list. So we can include Pay and Benefits sections. The line "Compensation and benefits offered may vary depending on multiple individualized factors..." is somewhat generic but not placeholder; we could keep as part of Pay section prose. But we need to avoid filler. Might be okay.
We need to preserve all substantive information. So include:
- About the role? Not explicitly a heading but we have "Job Summary". Could treat as 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 content to those headings where appropriate. "Job Summary" could be About the role. "What You Will Do" -> Responsibilities. "What You Will Have" -> Skills/Qualifications? Actually "What You Will Have" lists competencies like Analytical Thinking, Effective Communications, etc. Those are skills/qualifications. Could be Requirements or Qualifications. "Considerations For Top Candidates" -> Qualifications (maybe more detailed). Could combine.
We need to avoid duplicate sections. Let's decide:
- About the role: Job Summary paragraph.
- Responsibilities: "What You Will Do" list (bullet points).
- Qualifications/Skills: combine "What You Will Have" and "Considerations For Top Candidates". Could have two sub-sections: Skills and Qualifications. But we should prefer few substantive sections over many thin ones. Maybe combine into one "Qualifications" section with bullet points for each competency and experience.
But we need to use - for any list of duties/requirements/benefits. So for responsibilities we need a list. For qualifications we also need a list.
Pay:
Pay
with containing the pay range and maybe note about variation.
Benefits:
Benefits
with - list.
We must not include schedule as not present.
We must not repeat job title.
We must not include metadata like Job ID.
We must remove boilerplate: EEO, drug screen, visa sponsorship, posting dates, talent community, etc.
Let's extract substantive paragraphs.
Job Summary: "The Principal Systems Architect is the architecture leader for digital marketing technology. The role establishes the target-state vision and executable roadmap for an integrated, secure, scalable and measurable MarTech ecosystem spanning content creation, asset management, product information, web experience delivery, analytics, social and omnichannel activation. The role designs scalable MarTech architectures, leads content management and personalization initiatives, defines integration and data-governance strategies, and partners with business and marketing teams to deliver digital transformation and measurable business value."
That's prose.
What You Will Do: list of bullet points (each sentence starting with a verb). Let's capture them:
- Own the current-state, transition and target-state architecture and multiyear roadmap across digital marketing technology ecosystem.
- Develop detailed architecture deliverables to solve business problems, translating functional and non-functional requirements into application, platform, integration and data designs.
- Design technical infrastructure including databases, programming languages, utilities and testing approaches and lead evaluation and deployment of technologies that add or enhance digital capabilities.
- Partner with business, product, marketing, data, security and engineering teams to address requirements and deliver digital solutions that meet business results.
- Assess the marketing technology ecosystem, identify capability and performance gaps, document architecture decisions, and recommend solution patterns and best practices aligned with business objectives.
- Define platform strategy from MVP through implementation, maintenance, consolidation and deprecation.
- Architect end-to-end content supply chains for image, video and product/specification content from Adobe Creative Cloud, agencies and source systems through Assets, Sites, PIM, commerce and external channels, reducing manual handoffs and duplicate stores.
- Design data-layer contracts, tagging standards, consent gating, identity and audience flows, API/event integrations, metadata and data-quality controls that enable reliable measurement and personalized omnichannel experiences.
- Lead architecture reviews, technical discovery and requirements walkthroughs; quantify cost, benefit, risk and likelihood of success; resolve complex design issues and maintain traceability to business outcomes.
- Provide technical direction to delivery teams and partners, coach architects and engineers, and communicate recommendations effectively to executives, practitioners
What You Will Have: list of competencies each with description. Let's capture each bullet:
- Analytical Thinking: Knowledge of techniques and tools that promote effective analysis; ability to determine the root cause of organizational problems and create alternative solutions that resolve these problems.
- Effective Communications: Understanding of effective communication concepts, tools and techniques; ability to effectively transmit, receive, and accurately interpret ideas, information, and needs through the application of appropriate communication behaviors.
- Application Design, Architecture: Knowledge of basic activities and deliverables of application design; ability to utilize application design methodologies, tools and techniques to convert business requirements and logical models into a technical application design.
- Data Architecture: Knowledge of processes, techniques and factors that affect data architecture; ability to design blueprints on how to integrate data resources for business processes and functional support.
- Platform Architecture: Knowledge of technologies and methods to design processing mechanisms and roadmaps to execute business application systems; ability to design these roadmaps and deploy supportive interfaces for end-users to access related systems, in accordance with standards and processes.
- Requirements Analysis: Knowledge of tools, methods, and techniques of requirement analysis; ability to elicit, analyze and record required business functionality and non-functionality requirements to ensure the success of a system or software development project.
- Target Architecture: Knowledge of target architecture; ability to develop the IT blueprint and roadmap while aligning the architecture and processes with business strategies and objectives roadmap while aligning the architecture and processes with business strategies and objectives (duplicate phrase). We'll keep as is.
Considerations For Top Candidates: list of items (each sentence). Let's capture:
- Extensive IT and MarTech experience, including senior architecture leadership and full-lifecycle delivery of complex, global digital transformation programs.
- A degree in computer science, information systems or a related field, or equivalent experience; architecture and platform certifications are advantageous.
- Deep enterprise DXP experience with AEM, Contentful, Uniform or similar platforms, including headless and composable delivery models.
- Production experience with React/Next.js or comparable web stacks, server rendering, edge platforms/CDNs, caching, redirects, accessibility, SEO and web performance.
- Strong working knowledge of Adobe Experience Cloud and adjacent content tools, especially Adobe Experience Manager Sites and Assets, Creative Cloud workflows and Adobe Workfront; familiarity with Google Analytics, Adobe Analytics, Target, Experience Platform/Real-Time CDP and Journey Optimizer is highly valuable.
- Architecture experience across enterprise PIM (such as Informatica and Akeneo PIM) and commerce platforms, DAM/CDN and media platforms (such as Adobe Dynamic Media/Scene7 and CatDV), social platforms, analytics/BI and customer-facing web ecosystems.
- Expertise in marketing, advertising, personalization, experimentation, customer data platforms, data orchestration, content strategy and omnichannel activation.
- Demonstrated success simplifying fragmented content and data flows, integrating legacy and modern platforms, and moving organizations from manual handoffs toward governed, AI-enabled automation.
- Experience with structured content and DITA, and with B2B manufacturing, industrial, dealer/distributor or similarly complex global ecosystems.
- Strong integration fundamentals, including REST APIs, webhooks, OAuth/OIDC, SAML, event-driven and durable asynchronous processing, idempotency, reconciliation and data-contract design.
- Cloud fluency (AWS, Azure or equivalent), including serverless compute, secrets management, observability, resilience, security, privacy and cost control.
- Modern delivery practices: Agile and full SDLC, architecture-as-code/documentation, automated testing, CI/CD, environment strategy, release governance and vendor/platform lifecycle management.
- Practical knowledge of privacy-by-design, consent management, identity resolution, data governance and responsible AI-enabled personalization.
- A record of mentoring technical talent, directing partners and vendors, and converting architecture strategy into prioritized investment decisions and measurable outcomes.
Pay Range: "$159,120.00 - $258,570.00". Also note: "Compensation and benefits offered may vary depending on multiple individualized factors, job level, market location, job-related knowledge, skills, individual performance and experience. Please note that salary is only one component of total compensation at Caterpillar." We could keep first sentence as prose, second maybe boilerplate? It's somewhat generic but not placeholder. Might keep as part of Pay section.
Benefits list: bullet points:
- Medical, dental, and vision benefits*
- Paid time off plan (Vacation, Holidays, Volunteer, etc.)*
- 401(k) savings plans*
- Health Savings Account (HSA)*
- Flexible Spending Accounts (FSAs)*
- Health Lifestyle Programs*
- Employee Assistance Program*
- Voluntary Benefits and Employee Discounts*
- Career Development*
- Incentive bonus*
- Disability benefits
- Life Insurance
- Parental leave
- Adoption benefits
- Tuition Reimbursement
- These benefits also apply to part-time employees
Also note: "Visa Sponsorship is not available for this position." Might be considered a condition; but it's not a benefit/duty. Could be considered boilerplate; but it's specific info. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those categories; it's a sponsorship note. Might be considered relevant. However, it's a negative condition; maybe keep? I'd lean to keep as a short note under Benefits or as a separate paragraph. But the instruction says "Prefer a few substantive sections over many thin ones." Could add a note under Benefits as a paragraph.
We'll not include "Posting Dates", "Any offer of employment is conditioned upon the successful completion of a drug screen.", "Caterpillar is an Equal Opportunity Employer..." etc.
Now construct HTML.
We'll have:
About the role
Job Summary paragraph.
Responsibilities
- ...
...
Qualifications
Maybe combine What You Will Have and Considerations For Top Candidates as a list.
- ...
...
Pay
$159,120.00 - $258,570.00. Compensation and benefits offered may vary depending on multiple individualized factors, job level, market location, job-related knowledge, skills, individual performance and experience.
Benefits
for prose. Remove boilerplate: EEO, etc. Also remove "Any offer of employment is conditioned upon the successful completion of a drug screen." That's boilerplate? Might be considered legal; remove. Also remove "Visa Sponsorship is not available for this position." Might be considered requirement? It's a condition; but maybe keep? It's not a benefit/duty; it's a note. Probably remove as boilerplate. Also remove "Posting Dates". Remove "Please note that salary is only one component of total compensation". Might be considered boilerplate; but we need to preserve substantive info: Pay Range. Keep that line. Also "Compensation and benefits offered may vary depending on multiple individualized factors..." Might be considered boilerplate; but we can keep as part of Pay section? Might be considered filler. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states Pay Range and Benefits list. So we can include Pay and Benefits sections. The line "Compensation and benefits offered may vary depending on multiple individualized factors..." is somewhat generic but not placeholder; we could keep as part of Pay section prose. But we need to avoid filler. Might be okay. We need to preserve all substantive information. So include: - About the role? Not explicitly a heading but we have "Job Summary". Could treat as 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 content to those headings where appropriate. "Job Summary" could be About the role. "What You Will Do" -> Responsibilities. "What You Will Have" -> Skills/Qualifications? Actually "What You Will Have" lists competencies like Analytical Thinking, Effective Communications, etc. Those are skills/qualifications. Could be Requirements or Qualifications. "Considerations For Top Candidates" -> Qualifications (maybe more detailed). Could combine.
We need to avoid duplicate sections. Let's decide:
- About the role: Job Summary paragraph.
- Responsibilities: "What You Will Do" list (bullet points).
- Qualifications/Skills: combine "What You Will Have" and "Considerations For Top Candidates". Could have two sub-sections: Skills and Qualifications. But we should prefer few substantive sections over many thin ones. Maybe combine into one "Qualifications" section with bullet points for each competency and experience.
But we need to use - for any list of duties/requirements/benefits. So for responsibilities we need a list. For qualifications we also need a list.
Pay:
Pay
with containing the pay range and maybe note about variation.
Benefits:
Benefits
with - list.
We must not include schedule as not present.
We must not repeat job title.
We must not include metadata like Job ID.
We must remove boilerplate: EEO, drug screen, visa sponsorship, posting dates, talent community, etc.
Let's extract substantive paragraphs.
Job Summary: "The Principal Systems Architect is the architecture leader for digital marketing technology. The role establishes the target-state vision and executable roadmap for an integrated, secure, scalable and measurable MarTech ecosystem spanning content creation, asset management, product information, web experience delivery, analytics, social and omnichannel activation. The role designs scalable MarTech architectures, leads content management and personalization initiatives, defines integration and data-governance strategies, and partners with business and marketing teams to deliver digital transformation and measurable business value."
That's prose.
What You Will Do: list of bullet points (each sentence starting with a verb). Let's capture them:
- Own the current-state, transition and target-state architecture and multiyear roadmap across digital marketing technology ecosystem.
- Develop detailed architecture deliverables to solve business problems, translating functional and non-functional requirements into application, platform, integration and data designs.
- Design technical infrastructure including databases, programming languages, utilities and testing approaches and lead evaluation and deployment of technologies that add or enhance digital capabilities.
- Partner with business, product, marketing, data, security and engineering teams to address requirements and deliver digital solutions that meet business results.
- Assess the marketing technology ecosystem, identify capability and performance gaps, document architecture decisions, and recommend solution patterns and best practices aligned with business objectives.
- Define platform strategy from MVP through implementation, maintenance, consolidation and deprecation.
- Architect end-to-end content supply chains for image, video and product/specification content from Adobe Creative Cloud, agencies and source systems through Assets, Sites, PIM, commerce and external channels, reducing manual handoffs and duplicate stores.
- Design data-layer contracts, tagging standards, consent gating, identity and audience flows, API/event integrations, metadata and data-quality controls that enable reliable measurement and personalized omnichannel experiences.
- Lead architecture reviews, technical discovery and requirements walkthroughs; quantify cost, benefit, risk and likelihood of success; resolve complex design issues and maintain traceability to business outcomes.
- Provide technical direction to delivery teams and partners, coach architects and engineers, and communicate recommendations effectively to executives, practitioners
What You Will Have: list of competencies each with description. Let's capture each bullet:
- Analytical Thinking: Knowledge of techniques and tools that promote effective analysis; ability to determine the root cause of organizational problems and create alternative solutions that resolve these problems.
- Effective Communications: Understanding of effective communication concepts, tools and techniques; ability to effectively transmit, receive, and accurately interpret ideas, information, and needs through the application of appropriate communication behaviors.
- Application Design, Architecture: Knowledge of basic activities and deliverables of application design; ability to utilize application design methodologies, tools and techniques to convert business requirements and logical models into a technical application design.
- Data Architecture: Knowledge of processes, techniques and factors that affect data architecture; ability to design blueprints on how to integrate data resources for business processes and functional support.
- Platform Architecture: Knowledge of technologies and methods to design processing mechanisms and roadmaps to execute business application systems; ability to design these roadmaps and deploy supportive interfaces for end-users to access related systems, in accordance with standards and processes.
- Requirements Analysis: Knowledge of tools, methods, and techniques of requirement analysis; ability to elicit, analyze and record required business functionality and non-functionality requirements to ensure the success of a system or software development project.
- Target Architecture: Knowledge of target architecture; ability to develop the IT blueprint and roadmap while aligning the architecture and processes with business strategies and objectives roadmap while aligning the architecture and processes with business strategies and objectives (duplicate phrase). We'll keep as is.
Considerations For Top Candidates: list of items (each sentence). Let's capture:
- Extensive IT and MarTech experience, including senior architecture leadership and full-lifecycle delivery of complex, global digital transformation programs.
- A degree in computer science, information systems or a related field, or equivalent experience; architecture and platform certifications are advantageous.
- Deep enterprise DXP experience with AEM, Contentful, Uniform or similar platforms, including headless and composable delivery models.
- Production experience with React/Next.js or comparable web stacks, server rendering, edge platforms/CDNs, caching, redirects, accessibility, SEO and web performance.
- Strong working knowledge of Adobe Experience Cloud and adjacent content tools, especially Adobe Experience Manager Sites and Assets, Creative Cloud workflows and Adobe Workfront; familiarity with Google Analytics, Adobe Analytics, Target, Experience Platform/Real-Time CDP and Journey Optimizer is highly valuable.
- Architecture experience across enterprise PIM (such as Informatica and Akeneo PIM) and commerce platforms, DAM/CDN and media platforms (such as Adobe Dynamic Media/Scene7 and CatDV), social platforms, analytics/BI and customer-facing web ecosystems.
- Expertise in marketing, advertising, personalization, experimentation, customer data platforms, data orchestration, content strategy and omnichannel activation.
- Demonstrated success simplifying fragmented content and data flows, integrating legacy and modern platforms, and moving organizations from manual handoffs toward governed, AI-enabled automation.
- Experience with structured content and DITA, and with B2B manufacturing, industrial, dealer/distributor or similarly complex global ecosystems.
- Strong integration fundamentals, including REST APIs, webhooks, OAuth/OIDC, SAML, event-driven and durable asynchronous processing, idempotency, reconciliation and data-contract design.
- Cloud fluency (AWS, Azure or equivalent), including serverless compute, secrets management, observability, resilience, security, privacy and cost control.
- Modern delivery practices: Agile and full SDLC, architecture-as-code/documentation, automated testing, CI/CD, environment strategy, release governance and vendor/platform lifecycle management.
- Practical knowledge of privacy-by-design, consent management, identity resolution, data governance and responsible AI-enabled personalization.
- A record of mentoring technical talent, directing partners and vendors, and converting architecture strategy into prioritized investment decisions and measurable outcomes.
Pay Range: "$159,120.00 - $258,570.00". Also note: "Compensation and benefits offered may vary depending on multiple individualized factors, job level, market location, job-related knowledge, skills, individual performance and experience. Please note that salary is only one component of total compensation at Caterpillar." We could keep first sentence as prose, second maybe boilerplate? It's somewhat generic but not placeholder. Might keep as part of Pay section.
Benefits list: bullet points:
- Medical, dental, and vision benefits*
- Paid time off plan (Vacation, Holidays, Volunteer, etc.)*
- 401(k) savings plans*
- Health Savings Account (HSA)*
- Flexible Spending Accounts (FSAs)*
- Health Lifestyle Programs*
- Employee Assistance Program*
- Voluntary Benefits and Employee Discounts*
- Career Development*
- Incentive bonus*
- Disability benefits
- Life Insurance
- Parental leave
- Adoption benefits
- Tuition Reimbursement
- These benefits also apply to part-time employees
Also note: "Visa Sponsorship is not available for this position." Might be considered a condition; but it's not a benefit/duty. Could be considered boilerplate; but it's specific info. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those categories; it's a sponsorship note. Might be considered relevant. However, it's a negative condition; maybe keep? I'd lean to keep as a short note under Benefits or as a separate paragraph. But the instruction says "Prefer a few substantive sections over many thin ones." Could add a note under Benefits as a paragraph.
We'll not include "Posting Dates", "Any offer of employment is conditioned upon the successful completion of a drug screen.", "Caterpillar is an Equal Opportunity Employer..." etc.
Now construct HTML.
We'll have:
About the role
Job Summary paragraph.
Responsibilities
- ...
...
Qualifications
Maybe combine What You Will Have and Considerations For Top Candidates as a list.
- ...
...
Pay
$159,120.00 - $258,570.00. Compensation and benefits offered may vary depending on multiple individualized factors, job level, market location, job-related knowledge, skills, individual performance and experience.
Benefits
Pay
withcontaining the pay range and maybe note about variation. Benefits:
Benefits
with- list.
We must not include schedule as not present.
We must not repeat job title.
We must not include metadata like Job ID.
We must remove boilerplate: EEO, drug screen, visa sponsorship, posting dates, talent community, etc.
Let's extract substantive paragraphs.
Job Summary: "The Principal Systems Architect is the architecture leader for digital marketing technology. The role establishes the target-state vision and executable roadmap for an integrated, secure, scalable and measurable MarTech ecosystem spanning content creation, asset management, product information, web experience delivery, analytics, social and omnichannel activation. The role designs scalable MarTech architectures, leads content management and personalization initiatives, defines integration and data-governance strategies, and partners with business and marketing teams to deliver digital transformation and measurable business value."
That's prose.
What You Will Do: list of bullet points (each sentence starting with a verb). Let's capture them:
- Own the current-state, transition and target-state architecture and multiyear roadmap across digital marketing technology ecosystem.
- Develop detailed architecture deliverables to solve business problems, translating functional and non-functional requirements into application, platform, integration and data designs.
- Design technical infrastructure including databases, programming languages, utilities and testing approaches and lead evaluation and deployment of technologies that add or enhance digital capabilities.
- Partner with business, product, marketing, data, security and engineering teams to address requirements and deliver digital solutions that meet business results.
- Assess the marketing technology ecosystem, identify capability and performance gaps, document architecture decisions, and recommend solution patterns and best practices aligned with business objectives.
- Define platform strategy from MVP through implementation, maintenance, consolidation and deprecation.
- Architect end-to-end content supply chains for image, video and product/specification content from Adobe Creative Cloud, agencies and source systems through Assets, Sites, PIM, commerce and external channels, reducing manual handoffs and duplicate stores.
- Design data-layer contracts, tagging standards, consent gating, identity and audience flows, API/event integrations, metadata and data-quality controls that enable reliable measurement and personalized omnichannel experiences.
- Lead architecture reviews, technical discovery and requirements walkthroughs; quantify cost, benefit, risk and likelihood of success; resolve complex design issues and maintain traceability to business outcomes.
- Provide technical direction to delivery teams and partners, coach architects and engineers, and communicate recommendations effectively to executives, practitioners
What You Will Have: list of competencies each with description. Let's capture each bullet:
- Analytical Thinking: Knowledge of techniques and tools that promote effective analysis; ability to determine the root cause of organizational problems and create alternative solutions that resolve these problems.
- Effective Communications: Understanding of effective communication concepts, tools and techniques; ability to effectively transmit, receive, and accurately interpret ideas, information, and needs through the application of appropriate communication behaviors.
- Application Design, Architecture: Knowledge of basic activities and deliverables of application design; ability to utilize application design methodologies, tools and techniques to convert business requirements and logical models into a technical application design.
- Data Architecture: Knowledge of processes, techniques and factors that affect data architecture; ability to design blueprints on how to integrate data resources for business processes and functional support.
- Platform Architecture: Knowledge of technologies and methods to design processing mechanisms and roadmaps to execute business application systems; ability to design these roadmaps and deploy supportive interfaces for end-users to access related systems, in accordance with standards and processes.
- Requirements Analysis: Knowledge of tools, methods, and techniques of requirement analysis; ability to elicit, analyze and record required business functionality and non-functionality requirements to ensure the success of a system or software development project.
- Target Architecture: Knowledge of target architecture; ability to develop the IT blueprint and roadmap while aligning the architecture and processes with business strategies and objectives roadmap while aligning the architecture and processes with business strategies and objectives (duplicate phrase). We'll keep as is.
Considerations For Top Candidates: list of items (each sentence). Let's capture:
- Extensive IT and MarTech experience, including senior architecture leadership and full-lifecycle delivery of complex, global digital transformation programs.
- A degree in computer science, information systems or a related field, or equivalent experience; architecture and platform certifications are advantageous.
- Deep enterprise DXP experience with AEM, Contentful, Uniform or similar platforms, including headless and composable delivery models.
- Production experience with React/Next.js or comparable web stacks, server rendering, edge platforms/CDNs, caching, redirects, accessibility, SEO and web performance.
- Strong working knowledge of Adobe Experience Cloud and adjacent content tools, especially Adobe Experience Manager Sites and Assets, Creative Cloud workflows and Adobe Workfront; familiarity with Google Analytics, Adobe Analytics, Target, Experience Platform/Real-Time CDP and Journey Optimizer is highly valuable.
- Architecture experience across enterprise PIM (such as Informatica and Akeneo PIM) and commerce platforms, DAM/CDN and media platforms (such as Adobe Dynamic Media/Scene7 and CatDV), social platforms, analytics/BI and customer-facing web ecosystems.
- Expertise in marketing, advertising, personalization, experimentation, customer data platforms, data orchestration, content strategy and omnichannel activation.
- Demonstrated success simplifying fragmented content and data flows, integrating legacy and modern platforms, and moving organizations from manual handoffs toward governed, AI-enabled automation.
- Experience with structured content and DITA, and with B2B manufacturing, industrial, dealer/distributor or similarly complex global ecosystems.
- Strong integration fundamentals, including REST APIs, webhooks, OAuth/OIDC, SAML, event-driven and durable asynchronous processing, idempotency, reconciliation and data-contract design.
- Cloud fluency (AWS, Azure or equivalent), including serverless compute, secrets management, observability, resilience, security, privacy and cost control.
- Modern delivery practices: Agile and full SDLC, architecture-as-code/documentation, automated testing, CI/CD, environment strategy, release governance and vendor/platform lifecycle management.
- Practical knowledge of privacy-by-design, consent management, identity resolution, data governance and responsible AI-enabled personalization.
- A record of mentoring technical talent, directing partners and vendors, and converting architecture strategy into prioritized investment decisions and measurable outcomes.
Pay Range: "$159,120.00 - $258,570.00". Also note: "Compensation and benefits offered may vary depending on multiple individualized factors, job level, market location, job-related knowledge, skills, individual performance and experience. Please note that salary is only one component of total compensation at Caterpillar." We could keep first sentence as prose, second maybe boilerplate? It's somewhat generic but not placeholder. Might keep as part of Pay section.
Benefits list: bullet points:
- Medical, dental, and vision benefits*
- Paid time off plan (Vacation, Holidays, Volunteer, etc.)*
- 401(k) savings plans*
- Health Savings Account (HSA)*
- Flexible Spending Accounts (FSAs)*
- Health Lifestyle Programs*
- Employee Assistance Program*
- Voluntary Benefits and Employee Discounts*
- Career Development*
- Incentive bonus*
- Disability benefits
- Life Insurance
- Parental leave
- Adoption benefits
- Tuition Reimbursement
- These benefits also apply to part-time employees
Also note: "Visa Sponsorship is not available for this position." Might be considered a condition; but it's not a benefit/duty. Could be considered boilerplate; but it's specific info. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those categories; it's a sponsorship note. Might be considered relevant. However, it's a negative condition; maybe keep? I'd lean to keep as a short note under Benefits or as a separate paragraph. But the instruction says "Prefer a few substantive sections over many thin ones." Could add a note under Benefits as a paragraph.
We'll not include "Posting Dates", "Any offer of employment is conditioned upon the successful completion of a drug screen.", "Caterpillar is an Equal Opportunity Employer..." etc.
Now construct HTML.
We'll have:
About the role
Job Summary paragraph.
Responsibilities
- ... ...
Qualifications
Maybe combine What You Will Have and Considerations For Top Candidates as a list.
- ... ...
Pay
$159,120.00 - $258,570.00. Compensation and benefits offered may vary depending on multiple individualized factors, job level, market location, job-related knowledge, skills, individual performance and experience.
Benefits