Director, Architecture – Enterprise & Strategy
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate etc. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key content:
- Introduction to Role: description about role, responsibilities, etc. Could be "About the role" section.
- Accountabilities: list of responsibilities.
- Essential Skills/Experience: list of required skills/experience.
- Desirable Skills/Experience: list of desirable.
- Working at AstraZeneca: description about work environment, in-person days, etc. Could be "Benefits" or "Schedule"? Actually schedule: "minimum of three days per week from the office". That's schedule info. Benefits: "qualified retirement programs, paid time off (i.e., vacation, holiday, and leaves), as well as health, dental, and vision coverage". Also incentives: short-term incentive bonuses, equity-based awards, commissions for sales roles.
- Pay: "The annual base pay for this position ranges from $166,081.60 to $249,122.40."
- Date posted and closing date: maybe minor metadata, can be folded into short
or dropped. Probably we can include a short paragraph with posting date.
- Mission statement etc: maybe part of "About the role" or "Working at AstraZeneca".
We need to decide sections.
Potential sections:
- About the role (intro paragraph)
- Responsibilities (accountabilities list)
- Requirements (essential skills/experience list)
- Desirable Skills (maybe combine with Requirements? Could be separate "Qualifications" or "Skills". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content.
We have essential skills/experience (requirements). Desirable skills/experience (maybe "Qualifications" or "Skills").
We have benefits and pay and schedule.
Thus sections:
- About the role (intro paragraph)
- Responsibilities (list of accountabilities)
- Requirements (essential skills/experience)
- Qualifications (desirable skills/experience) maybe.
- Benefits (list of benefits)
- Pay (pay range)
- Schedule (in-person days)
We must not create sections with filler. All have content.
We must not repeat job title as heading.
We must not include Job ID etc.
We must not include boilerplate like EEO etc. Remove mission statement? The mission statement about inclusive environment is boilerplate EEO; we should remove. Also "Our mission is to build an inclusive environment..." is EEO boilerplate; remove. Also "If you have a disability..." remove.
Also "Date Posted" and "Closing Date" maybe minor metadata; we can fold into short
at end or drop. Probably include a short paragraph with posting date.
We must preserve all substantive information: so we need to keep the description about role, responsibilities list, essential skills list, desirable skills list, working at AstraZeneca description (including in-person days, flexibility, mission about architecting enterprise platforms, etc), benefits list, pay range.
We must not invent or summarize away detail: keep specifics.
We need to format lists as
- . For prose, use
.
We need to ensure we don't duplicate lines.
Let's extract content.
Introduction to Role paragraph:
"Are you ready to take on a pivotal role that builds the future of AstraZeneca's Martech architecture? As the Director, Architecture – Enterprise & Strategy, you'll have the outstanding opportunity to drive strategic architecture decisions that align with our business and IT strategies. Your expertise will ensure our architectures align with relevant standards, blueprints, and roadmaps. You'll partner with key business and IT leadership teams, integrating information from business strategies to develop the overall strategic direction for AstraZeneca’s Martech architecture portfolio. This role is not just about maintaining the status quo; it's about inspiring change, addressing industry trends, and educating partners across Martech. Are you up for the challenge?"
That's prose.
Accountabilities list: many bullet-like sentences separated by periods. We need to turn each into
- . Let's list them:
- Provide Enterprise Design thinking & support to AZ’s Martech Enterprise Architecture specifically:
- Marketing Automation - CDP, Campaign Management
- Commerce – Direct to Consumer and Direct to Patient
- Content Management Systems and Web Sites
- GENAI Content Creation
- Define the architecture strategy, direction, and standards pertinent for Martech.
- Analyse business priorities & strategies and translate these into architecture requirements for the enterprise.
- Act as an authority to the architecture community and the business regarding strategic architecture decisions for the relevant architecture segment.
- Refine Martech architecture strategies, mentorship, and criteria as the need arises.
- Lead the development of Martech Architecture Roadmaps and Blueprints (1-5 Year horizon).
- Ensure continuous alignment of capabilities with current business priorities and objectives.
- Be a contributing member of cross-functional decision-making bodies.
- Act as a sign-off authority for solution and segment architectures as well as architecture blueprints and roadmaps.
- Nurture EA initiatives across IS.
- Engage and build a network with external architecture subject matter experts to remain up-to-date with the latest trends and technologies.
- Act as a strategic architectural advisor for senior IT and Business management.
- Drive and oversee the development of Architecture Roadmaps and Blueprints.
- Ensure Martech Architectures are in alignment with Global strategies and solutions.
- Lead the development and implementation of Enterprise Architecture (EA) standards, processes, tools, and setup.
- Establish clear comprehensive strategies and agreed AZ approaches for management of key information.
- Analyse IT industry and market trends and determine potential impact upon enterprise.
- Establish partnerships with key technology suppliers.
- Provide thought leadership and sophisticated technical expertise for Martech enterprise architecture across IS.
- Drive the continuous development of the Architecture Capability within IS by encouraging standard process sharing.
We need to keep the sub-bullets under "Provide Enterprise Design thinking & support..." as separate items? The instruction: Use
- for any list of duties/requirements/benefits. So we can flatten: each bullet as
- . The sub-items could be separate
- as well. We'll keep them as separate items.
Essential Skills/Experience list: each line starts with bullet? It's a paragraph with many items separated by line breaks? Let's extract:
- Bachelor's Degree
- At least 5 years Enterprise Architecture experience
- Experience defining and aligning Martech architectural roadmaps and strategies to business strategy.
- Experience in Salesforce and Adobe products and platforms including Salesforce Marketing Cloud and Data Cloud, Adobe Experience Manager, Workfront, and Adobe Assets.
- Experience with rationalisation, consolidation, and integration across business domains using a formal framework.
- Experience with large Justification phase work – product evaluation, case formulation.
- Experience influencing key senior partners in business and IT to adopt change or innovative solutions.
- Experience defining and developing components of an Enterprise Architecture practice.
- Experience managing and negotiating with third-party suppliers.
- Experience managing, developing, and leading a team of people in different locations.
- Strong networking skills with good internal/external links.
- Strong communication, facilitation, and relationship-building skills at senior levels of corporate and technology sectors.
- Ability to interpret and communicate technical information into business language.
- Awareness of developments in the marketplace and understand the relevance and potential impact to AZ IS.
- Ability to work well in diverse, multinational teams and proven track record to influence others to achieve positive outcomes.
- Ability to recognize important aspects of business.
Desirable Skills/Experience list:
- Demonstrate initiative, strong customer orientation, and cross-cultural working.
- People Development experience.
- Budget Management experience.
- Masters and/or Professional Certification.
- Awareness of relevant legislation and data protection laws.
- Understanding of the pharmaceutical/healthcare industry and of competitor activity on a particular architecture and Information Management.
Working at AstraZeneca paragraph:
"When we put unexpected teams in the same room, we unleash ambitious thinking with the power to encourage life-changing medicines. In-person working gives us the platform we need to connect, work at pace, and challenge perceptions. That's why we work, on average, a minimum of three days per week from the office. But that doesn't mean we're not flexible. We balance the expectation of being in the office while respecting individual flexibility. Join us in our outstanding and ambitious world. At AstraZeneca, we architect enterprise platforms that align with our strategic direction, enabling us to scale rapidly while applying the right technology to meet business needs. Our approach simplifies our technology landscape, allowing us to flexibly respond to challenges. Here, you'll be part of a dynamic environment where your contributions can significantly impact our mission to deliver life-changing medicines. Ready to make a difference? Apply now to join AstraZeneca's journey towards innovation!"
We need to remove the "Apply now" call to action? That's application instruction; we should remove application instructions. So remove "Ready to make a difference? Apply now to join AstraZeneca's journey towards innovation!" Also maybe remove "Join us in our outstanding and ambitious world." That's okay? It's not application instruction; it's promotional. Keep.
We also need to remove boilerplate like EEO etc already removed.
Benefits paragraph:
"Benefits offered include qualified retirement programs, paid time off (i.e., vacation, holiday, and leaves), as well as health, dental, and vision coverage in accordance with the terms of the applicable plans."
Also incentives: "Our positions offer eligibility for various incentives—an opportunity to receive short-term incentive bonuses, equity-based awards for salaried roles, and commissions for sales roles."
We can combine benefits and incentives into a Benefits section list.
Pay: "The annual base pay for this position ranges from $166,081.60 to $249,122.40."
Schedule: "That's why we work, on average, a minimum of three days per week from the office." Also mention flexibility.
We can create Schedule section with that sentence.
Now we need to output HTML fragment only.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- qualified retirement programs
- paid time off (i.e., vacation, holiday, and leaves)
- health, dental, and vision coverage
- short-term incentive bonuses
- equity-based awards for salaried roles
- commissions for sales roles
But we need to preserve the phrase "in accordance with the terms of the applicable plans." Might be part of health coverage description. Could keep as part of - health, dental, and vision coverage in accordance with the terms of the applicable plans.
Also incentives description: "an opportunity to receive short-term incentive bonuses, equity-based awards for salaried roles, and commissions for sales roles." Could split.
We'll keep as separate items.
Pay
The annual base pay for this position ranges from $166,081.60 to $249,122.40.
Schedule
We work, on average, a minimum of three days per week from the office, with flexibility to balance office expectations and individual needs.
We need to ensure we didn't lose any substantive info: The working at AstraZeneca paragraph includes many sentences about unexpected teams, in-person working, platform, etc. We should include that
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate etc. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key content: - Introduction to Role: description about role, responsibilities, etc. Could be "About the role" section. - Accountabilities: list of responsibilities. - Essential Skills/Experience: list of required skills/experience. - Desirable Skills/Experience: list of desirable. - Working at AstraZeneca: description about work environment, in-person days, etc. Could be "Benefits" or "Schedule"? Actually schedule: "minimum of three days per week from the office". That's schedule info. Benefits: "qualified retirement programs, paid time off (i.e., vacation, holiday, and leaves), as well as health, dental, and vision coverage". Also incentives: short-term incentive bonuses, equity-based awards, commissions for sales roles. - Pay: "The annual base pay for this position ranges from $166,081.60 to $249,122.40." - Date posted and closing date: maybe minor metadata, can be folded into short
or dropped. Probably we can include a short paragraph with posting date. - Mission statement etc: maybe part of "About the role" or "Working at AstraZeneca". We need to decide sections. Potential sections: - About the role (intro paragraph) - Responsibilities (accountabilities list) - Requirements (essential skills/experience list) - Desirable Skills (maybe combine with Requirements? Could be separate "Qualifications" or "Skills". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have essential skills/experience (requirements). Desirable skills/experience (maybe "Qualifications" or "Skills"). We have benefits and pay and schedule. Thus sections: - About the role (intro paragraph) - Responsibilities (list of accountabilities) - Requirements (essential skills/experience) - Qualifications (desirable skills/experience) maybe. - Benefits (list of benefits) - Pay (pay range) - Schedule (in-person days) We must not create sections with filler. All have content. We must not repeat job title as heading. We must not include Job ID etc. We must not include boilerplate like EEO etc. Remove mission statement? The mission statement about inclusive environment is boilerplate EEO; we should remove. Also "Our mission is to build an inclusive environment..." is EEO boilerplate; remove. Also "If you have a disability..." remove. Also "Date Posted" and "Closing Date" maybe minor metadata; we can fold into short
at end or drop. Probably include a short paragraph with posting date. We must preserve all substantive information: so we need to keep the description about role, responsibilities list, essential skills list, desirable skills list, working at AstraZeneca description (including in-person days, flexibility, mission about architecting enterprise platforms, etc), benefits list, pay range. We must not invent or summarize away detail: keep specifics. We need to format lists as
- . For prose, use
. We need to ensure we don't duplicate lines. Let's extract content. Introduction to Role paragraph: "Are you ready to take on a pivotal role that builds the future of AstraZeneca's Martech architecture? As the Director, Architecture – Enterprise & Strategy, you'll have the outstanding opportunity to drive strategic architecture decisions that align with our business and IT strategies. Your expertise will ensure our architectures align with relevant standards, blueprints, and roadmaps. You'll partner with key business and IT leadership teams, integrating information from business strategies to develop the overall strategic direction for AstraZeneca’s Martech architecture portfolio. This role is not just about maintaining the status quo; it's about inspiring change, addressing industry trends, and educating partners across Martech. Are you up for the challenge?" That's prose. Accountabilities list: many bullet-like sentences separated by periods. We need to turn each into
- . Let's list them:
- Provide Enterprise Design thinking & support to AZ’s Martech Enterprise Architecture specifically:
- Marketing Automation - CDP, Campaign Management
- Commerce – Direct to Consumer and Direct to Patient
- Content Management Systems and Web Sites
- GENAI Content Creation
- Define the architecture strategy, direction, and standards pertinent for Martech.
- Analyse business priorities & strategies and translate these into architecture requirements for the enterprise.
- Act as an authority to the architecture community and the business regarding strategic architecture decisions for the relevant architecture segment.
- Refine Martech architecture strategies, mentorship, and criteria as the need arises.
- Lead the development of Martech Architecture Roadmaps and Blueprints (1-5 Year horizon).
- Ensure continuous alignment of capabilities with current business priorities and objectives.
- Be a contributing member of cross-functional decision-making bodies.
- Act as a sign-off authority for solution and segment architectures as well as architecture blueprints and roadmaps.
- Nurture EA initiatives across IS.
- Engage and build a network with external architecture subject matter experts to remain up-to-date with the latest trends and technologies.
- Act as a strategic architectural advisor for senior IT and Business management.
- Drive and oversee the development of Architecture Roadmaps and Blueprints.
- Ensure Martech Architectures are in alignment with Global strategies and solutions.
- Lead the development and implementation of Enterprise Architecture (EA) standards, processes, tools, and setup.
- Establish clear comprehensive strategies and agreed AZ approaches for management of key information.
- Analyse IT industry and market trends and determine potential impact upon enterprise.
- Establish partnerships with key technology suppliers.
- Provide thought leadership and sophisticated technical expertise for Martech enterprise architecture across IS.
- Drive the continuous development of the Architecture Capability within IS by encouraging standard process sharing.
We need to keep the sub-bullets under "Provide Enterprise Design thinking & support..." as separate items? The instruction: Use
- for any list of duties/requirements/benefits. So we can flatten: each bullet as
- . The sub-items could be separate
- as well. We'll keep them as separate items.
Essential Skills/Experience list: each line starts with bullet? It's a paragraph with many items separated by line breaks? Let's extract:
- Bachelor's Degree
- At least 5 years Enterprise Architecture experience
- Experience defining and aligning Martech architectural roadmaps and strategies to business strategy.
- Experience in Salesforce and Adobe products and platforms including Salesforce Marketing Cloud and Data Cloud, Adobe Experience Manager, Workfront, and Adobe Assets.
- Experience with rationalisation, consolidation, and integration across business domains using a formal framework.
- Experience with large Justification phase work – product evaluation, case formulation.
- Experience influencing key senior partners in business and IT to adopt change or innovative solutions.
- Experience defining and developing components of an Enterprise Architecture practice.
- Experience managing and negotiating with third-party suppliers.
- Experience managing, developing, and leading a team of people in different locations.
- Strong networking skills with good internal/external links.
- Strong communication, facilitation, and relationship-building skills at senior levels of corporate and technology sectors.
- Ability to interpret and communicate technical information into business language.
- Awareness of developments in the marketplace and understand the relevance and potential impact to AZ IS.
- Ability to work well in diverse, multinational teams and proven track record to influence others to achieve positive outcomes.
- Ability to recognize important aspects of business.
Desirable Skills/Experience list:
- Demonstrate initiative, strong customer orientation, and cross-cultural working.
- People Development experience.
- Budget Management experience.
- Masters and/or Professional Certification.
- Awareness of relevant legislation and data protection laws.
- Understanding of the pharmaceutical/healthcare industry and of competitor activity on a particular architecture and Information Management.
Working at AstraZeneca paragraph:
"When we put unexpected teams in the same room, we unleash ambitious thinking with the power to encourage life-changing medicines. In-person working gives us the platform we need to connect, work at pace, and challenge perceptions. That's why we work, on average, a minimum of three days per week from the office. But that doesn't mean we're not flexible. We balance the expectation of being in the office while respecting individual flexibility. Join us in our outstanding and ambitious world. At AstraZeneca, we architect enterprise platforms that align with our strategic direction, enabling us to scale rapidly while applying the right technology to meet business needs. Our approach simplifies our technology landscape, allowing us to flexibly respond to challenges. Here, you'll be part of a dynamic environment where your contributions can significantly impact our mission to deliver life-changing medicines. Ready to make a difference? Apply now to join AstraZeneca's journey towards innovation!"
We need to remove the "Apply now" call to action? That's application instruction; we should remove application instructions. So remove "Ready to make a difference? Apply now to join AstraZeneca's journey towards innovation!" Also maybe remove "Join us in our outstanding and ambitious world." That's okay? It's not application instruction; it's promotional. Keep.
We also need to remove boilerplate like EEO etc already removed.
Benefits paragraph:
"Benefits offered include qualified retirement programs, paid time off (i.e., vacation, holiday, and leaves), as well as health, dental, and vision coverage in accordance with the terms of the applicable plans."
Also incentives: "Our positions offer eligibility for various incentives—an opportunity to receive short-term incentive bonuses, equity-based awards for salaried roles, and commissions for sales roles."
We can combine benefits and incentives into a Benefits section list.
Pay: "The annual base pay for this position ranges from $166,081.60 to $249,122.40."
Schedule: "That's why we work, on average, a minimum of three days per week from the office." Also mention flexibility.
We can create Schedule section with that sentence.
Now we need to output HTML fragment only.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- qualified retirement programs
- paid time off (i.e., vacation, holiday, and leaves)
- health, dental, and vision coverage
- short-term incentive bonuses
- equity-based awards for salaried roles
- commissions for sales roles
- health, dental, and vision coverage in accordance with the terms of the applicable plans.
Also incentives description: "an opportunity to receive short-term incentive bonuses, equity-based awards for salaried roles, and commissions for sales roles." Could split.
We'll keep as separate items.
Pay
The annual base pay for this position ranges from $166,081.60 to $249,122.40.
Schedule
We work, on average, a minimum of three days per week from the office, with flexibility to balance office expectations and individual needs.
We need to ensure we didn't lose any substantive info: The working at AstraZeneca paragraph includes many sentences about unexpected teams, in-person working, platform, etc. We should include that