VP Enterprise Business Applications & Technology
for section headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide what to put in lists vs prose. For responsibilities, we have many items; could list them as
- . For qualifications, we have education & credentials, experience & expertise, etc. Could list as
. For skills, list professional & leadership capabilities as . For benefits, we have a sentence: "We provide best-in-class benefits and we foster an inclusive workplace where diversity is valued, and everyone is essential, heard and respected." Could be or list? It's prose; we can put in
. For About the role, we have description paragraphs: "Providence is seeking a transformational technology leader..." and "The Opportunity ..." Could be
.
We must not duplicate lines. Need to ensure we capture all substantive info.
Let's extract sections:
About the role: combine first paragraph and "The Opportunity" paragraph(s). The Opportunity paragraph: "The Vice President of Enterprise Business Applications & Technology (EBAT) is responsible for guiding the strategic vision and performance of Providence's enterprise business application and technology portfolio. This executive leads the development and execution of technology strategies that enable operational excellence, business transformation, innovation, and sustainable growth across Finance, Human Resources, Workforce Management, Supply Chain, Real Estate, Legal, Compliance, and other shared services functions. The Vice President oversees a diverse portfolio that includes custom software engineering, service engineering, data and analytics platforms, automation capabilities, and AI-enabled solutions. In partnership with business and technology leaders, this role establishes priorities, investment strategies, modernization roadmaps, and governance frameworks to ensure technology capabilities align with organizational objectives and deliver measurable business value. As a senior technology leader, the Vice President is thought leader; accountable for portfolio health, service performance, strategic planning, resource allocation, financial stewardship, talent development, risk management, cybersecurity and regulatory compliance, and the successful delivery of technology initiatives. The role fosters a culture of innovation, operational excellence, and continuous improvement while advancing Providence's digital transformation agenda and maximizing the impact of technology investments across EBAT."
We can put that as
.
Responsibilities: from "Accountabilities Include The Following Operational Categories" list: Support of functional business partners and executives; Identification and assessment of technical road maps and requirements; Sponsorship of implementation activities; Production support of assigned applications; Support of and maximization of application usefulness; Effective management of vendor relationships. Also "This position is responsible for leading, mentoring and developing leaders, managers as well as other staff." "This position will work in close collaboration with executives, directors, managers and other leaders and staff across the system." "This position will create and successfully execute strategic plans for highly complex issues involving business and information services operations and support." "It will also work to standardize complex and disparate processes and methodologies related to application management such as design, deployment, support and life cycle."
Then Essential Functions broken into Strategic, Management, Operational. Those are more detailed responsibilities. We could combine all into a responsibilities list.
But we must not invent or summarize away detail; we can list each bullet as
- . Ensure we capture all.
Let's list responsibilities bullets:
- Support of functional business partners and executives
- Identification and assessment of technical road maps and requirements
- Sponsorship of implementation activities
- Production support of assigned applications
- Support of and maximization of application usefulness
- Effective management of vendor relationships
- Leading, mentoring and developing leaders, managers and other staff
- Working in close collaboration with executives, directors, managers and other leaders and staff across the system
- Creating and successfully executing strategic plans for highly complex issues involving business and information services operations and support
- Standardizing complex and disparate processes and methodologies related to application management (design, deployment, support and life cycle)
Then Strategic responsibilities (list):
- Responsible for the development of enterprise business application digital transformation strategy and roadmap
- Develops long term strategy of AI, ML and RPA technologies (note duplicate line appears twice; we should include only once)
- Responsible for the pre M&A due diligence and post M&A integration strategy for new affiliations and maintenance of legacy systems
- Responsible for the post M&A technical conversion of new affiliations
- Creates and executes the long term enterprise application integration strategy program for EBAT operations and technology
- Maintains relationships with key business partners and other senior leaders in the IT industry in order to leverage best practices, evaluate and manage emerging application technologies
- Directs adoption process for introducing and implementing new services, technologies and/or applications into Information Services
- Implements appropriate service delivery models for core application functions in defining, delivering, and improving services for the enterprise and its customers
- Responsible for working with leaders of IS Strategy and Business Development in ensuring adherence to standards, and continuously evaluating the effectiveness of application systems
- Ensures that the Applications division supports IS services and systems effectively and meets the needs of the business
- Participates in the development of the overall IS strategic plan by identifying needed application management strategies and projects that support business needs
- Manages customer expectations regarding the success of each Information Services strategy and project; ensures measurable outcomes are defined and reported for each strategy or project
- Partners with key stakeholders and customers to implement application services for strategic initiatives that are effective, user-friendly and accurate
Management responsibilities:
- Manages overall technology program budget and the establishment of project financials and controls
- Develops and negotiates preferred information technology vendor contracts and manages key vendor relationships
- Manages strategic vendor relationships, ensuring financial, compliance, and service level goals are achieved
- Ensures the performance of applications within their domain and evaluates the performance of services on the basis of specific KPIs
- Oversees budgeting and expenditures for applications, staff and services within their span of control
- Assists in the development of and monitors compliance with policies and procedures for Application Services that impact all of Providence St. Joseph Health
- Attracts, hires, trains, motivates, retains, and develops a team of first-rate professionals to perform the responsibilities of applications management
- Designs, implements, maintains, and operates departmental Service Level Agreements, Operating Level Agreements, and associated KPIs
- Demonstrates the ability to build an organization and provide responsive leadership; to delegate, coordinate and motivate staff, and to evaluate performance
- Demonstrates ability to coordinate and facilitate teamwork with multidisciplinary groups, building and reaching consensus; agreeing upon a course of action where there are multiple perspectives
- Demonstrates outstanding organizational skills, as well as the ability to manage shifting priorities
Operational responsibilities:
- Plans for monthly and quarterly releases
- Provides leadership for all support activities
- Develops budgets and expenditures for information services related to applications in partnership with other leaders and the PMO
- Provides executive leadership on critical issues, problems or delays in production, projects or any other issues that have an impact on the customer
- Leads process optimization and initiatives to improve service delivery, increase value and promote customer service
- Maintains the delivery of secure, reliable, and scalable applications and processes that support the growth and financial objectives of Providence St. Joseph Health
- Teams with the business and other IS disciplines to develop and maintain appropriate disaster recovery architecture, projects, and policies and participates in disaster drills for applications
We could combine all into one responsibilities list, but that would be huge. Still acceptable.
Requirements: maybe we treat Qualifications as separate heading; Requirements maybe not needed. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes under Requirements vs Qualifications vs Skills. Typically Requirements could be education/experience; Qualifications could be credentials; Skills could be capabilities. But we have both Education & Credentials, Experience & Expertise, Professional & Leadership Capabilities. We could map:
- Requirements: Education & Credentials + Experience & Expertise (maybe combined)
- Qualifications: maybe not needed if we already used Requirements; but we could put Qualifications as Education & Credentials (or combine). However we must not create empty sections. We need to decide.
Better: Use Requirements for education and experience (the must-haves). Use Qualifications for preferred qualifications (Master's degree preferred). Use Skills for professional & leadership capabilities.
But the posting has "Education & Credentials" (Bachelor's required, Master's preferred). "Experience & Expertise" (various years). Then "Professional & Leadership Capabilities". So we can assign:
- Requirements: Education & Credentials (Bachelor's required) + Experience & Expertise (the years etc.)
- Qualifications: maybe Master's degree preferred (but that's part of Education & Credentials). Could also include "Healthcare knowledge and experience preferred." etc. But we might just put Qualifications as the preferred qualifications (Master's degree preferred, Healthcare knowledge preferred, etc.) but we risk duplication.
Simplify: Use Requirements for Education & Credentials + Experience & Expertise (all required). Use Skills for Professional & Leadership Capabilities. Omit Qualifications section (or combine into Requirements). But we need to follow instruction: include a section ONLY when posting has real, specific content for it. If we omit Qualifications, that's fine.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
Now we need to format.
For Requirements, we have list items: Education & Credentials (Bachelor's Degree in ...; Master's Degree ... preferred). Experience & Expertise (multiple bullet points). We'll create
- for each bullet.
We must preserve all substantive info; not invent or summarize away detail. So we need to include each bullet exactly as in text, but we can condense? The instruction says do NOT invent or summarize away detail. Summarizing away detail would be removing details. We should keep the details but can we rephrase? Safer to keep the exact phrasing but maybe we can keep as is. However we need to avoid duplication (like duplicate line "Develops long term strategy of AI, ML and RPA technologies." appears twice; we should include once.
Let's extract Education & Credentials bullet:
"Bachelor's Degree in Computer Science, Business Management, Information Services, Engineering, Finance, Supply Chain, HR; or equivalent education/experience.
Master's Degree in Information Services, Business Administration, Healthcare Administration, Public Administration, or a related IS or healthcare field; or equivalent education/experience (preferred)."
We can make two list items.
Experience & Expertise bullets (many). Let's list them as separate
- items, preserving the text.
We need to be careful not to include
for prose. We need to decide what to put in lists vs prose. For responsibilities, we have many items; could list them as
- . For qualifications, we have education & credentials, experience & expertise, etc. Could list as
- . For skills, list professional & leadership capabilities as
- . Ensure we capture all.
Let's list responsibilities bullets:
- Support of functional business partners and executives
- Identification and assessment of technical road maps and requirements
- Sponsorship of implementation activities
- Production support of assigned applications
- Support of and maximization of application usefulness
- Effective management of vendor relationships
- Leading, mentoring and developing leaders, managers and other staff
- Working in close collaboration with executives, directors, managers and other leaders and staff across the system
- Creating and successfully executing strategic plans for highly complex issues involving business and information services operations and support
- Standardizing complex and disparate processes and methodologies related to application management (design, deployment, support and life cycle)
Then Strategic responsibilities (list):
- Responsible for the development of enterprise business application digital transformation strategy and roadmap
- Develops long term strategy of AI, ML and RPA technologies (note duplicate line appears twice; we should include only once)
- Responsible for the pre M&A due diligence and post M&A integration strategy for new affiliations and maintenance of legacy systems
- Responsible for the post M&A technical conversion of new affiliations
- Creates and executes the long term enterprise application integration strategy program for EBAT operations and technology
- Maintains relationships with key business partners and other senior leaders in the IT industry in order to leverage best practices, evaluate and manage emerging application technologies
- Directs adoption process for introducing and implementing new services, technologies and/or applications into Information Services
- Implements appropriate service delivery models for core application functions in defining, delivering, and improving services for the enterprise and its customers
- Responsible for working with leaders of IS Strategy and Business Development in ensuring adherence to standards, and continuously evaluating the effectiveness of application systems
- Ensures that the Applications division supports IS services and systems effectively and meets the needs of the business
- Participates in the development of the overall IS strategic plan by identifying needed application management strategies and projects that support business needs
- Manages customer expectations regarding the success of each Information Services strategy and project; ensures measurable outcomes are defined and reported for each strategy or project
- Partners with key stakeholders and customers to implement application services for strategic initiatives that are effective, user-friendly and accurate
Management responsibilities:
- Manages overall technology program budget and the establishment of project financials and controls
- Develops and negotiates preferred information technology vendor contracts and manages key vendor relationships
- Manages strategic vendor relationships, ensuring financial, compliance, and service level goals are achieved
- Ensures the performance of applications within their domain and evaluates the performance of services on the basis of specific KPIs
- Oversees budgeting and expenditures for applications, staff and services within their span of control
- Assists in the development of and monitors compliance with policies and procedures for Application Services that impact all of Providence St. Joseph Health
- Attracts, hires, trains, motivates, retains, and develops a team of first-rate professionals to perform the responsibilities of applications management
- Designs, implements, maintains, and operates departmental Service Level Agreements, Operating Level Agreements, and associated KPIs
- Demonstrates the ability to build an organization and provide responsive leadership; to delegate, coordinate and motivate staff, and to evaluate performance
- Demonstrates ability to coordinate and facilitate teamwork with multidisciplinary groups, building and reaching consensus; agreeing upon a course of action where there are multiple perspectives
- Demonstrates outstanding organizational skills, as well as the ability to manage shifting priorities
Operational responsibilities:
- Plans for monthly and quarterly releases
- Provides leadership for all support activities
- Develops budgets and expenditures for information services related to applications in partnership with other leaders and the PMO
- Provides executive leadership on critical issues, problems or delays in production, projects or any other issues that have an impact on the customer
- Leads process optimization and initiatives to improve service delivery, increase value and promote customer service
- Maintains the delivery of secure, reliable, and scalable applications and processes that support the growth and financial objectives of Providence St. Joseph Health
- Teams with the business and other IS disciplines to develop and maintain appropriate disaster recovery architecture, projects, and policies and participates in disaster drills for applications
We could combine all into one responsibilities list, but that would be huge. Still acceptable.
Requirements: maybe we treat Qualifications as separate heading; Requirements maybe not needed. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes under Requirements vs Qualifications vs Skills. Typically Requirements could be education/experience; Qualifications could be credentials; Skills could be capabilities. But we have both Education & Credentials, Experience & Expertise, Professional & Leadership Capabilities. We could map:
- Requirements: Education & Credentials + Experience & Expertise (maybe combined)
- Qualifications: maybe not needed if we already used Requirements; but we could put Qualifications as Education & Credentials (or combine). However we must not create empty sections. We need to decide.
Better: Use Requirements for education and experience (the must-haves). Use Qualifications for preferred qualifications (Master's degree preferred). Use Skills for professional & leadership capabilities.
But the posting has "Education & Credentials" (Bachelor's required, Master's preferred). "Experience & Expertise" (various years). Then "Professional & Leadership Capabilities". So we can assign:
- Requirements: Education & Credentials (Bachelor's required) + Experience & Expertise (the years etc.)
- Qualifications: maybe Master's degree preferred (but that's part of Education & Credentials). Could also include "Healthcare knowledge and experience preferred." etc. But we might just put Qualifications as the preferred qualifications (Master's degree preferred, Healthcare knowledge preferred, etc.) but we risk duplication.
Simplify: Use Requirements for Education & Credentials + Experience & Expertise (all required). Use Skills for Professional & Leadership Capabilities. Omit Qualifications section (or combine into Requirements). But we need to follow instruction: include a section ONLY when posting has real, specific content for it. If we omit Qualifications, that's fine.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
Now we need to format.
For Requirements, we have list items: Education & Credentials (Bachelor's Degree in ...; Master's Degree ... preferred). Experience & Expertise (multiple bullet points). We'll create
- for each bullet. We must preserve all substantive info; not invent or summarize away detail. So we need to include each bullet exactly as in text, but we can condense? The instruction says do NOT invent or summarize away detail. Summarizing away detail would be removing details. We should keep the details but can we rephrase? Safer to keep the exact phrasing but maybe we can keep as is. However we need to avoid duplication (like duplicate line "Develops long term strategy of AI, ML and RPA technologies." appears twice; we should include once. Let's extract Education & Credentials bullet: "Bachelor's Degree in Computer Science, Business Management, Information Services, Engineering, Finance, Supply Chain, HR; or equivalent education/experience. Master's Degree in Information Services, Business Administration, Healthcare Administration, Public Administration, or a related IS or healthcare field; or equivalent education/experience (preferred)." We can make two list items. Experience & Expertise bullets (many). Let's list them as separate
- items, preserving the text. We need to be careful not to include
- . For benefits, we have a sentence: "We provide best-in-class benefits and we foster an inclusive workplace where diversity is valued, and everyone is essential, heard and respected." Could be
or list? It's prose; we can put in
. For About the role, we have description paragraphs: "Providence is seeking a transformational technology leader..." and "The Opportunity ..." Could be
. We must not duplicate lines. Need to ensure we capture all substantive info. Let's extract sections: About the role: combine first paragraph and "The Opportunity" paragraph(s). The Opportunity paragraph: "The Vice President of Enterprise Business Applications & Technology (EBAT) is responsible for guiding the strategic vision and performance of Providence's enterprise business application and technology portfolio. This executive leads the development and execution of technology strategies that enable operational excellence, business transformation, innovation, and sustainable growth across Finance, Human Resources, Workforce Management, Supply Chain, Real Estate, Legal, Compliance, and other shared services functions. The Vice President oversees a diverse portfolio that includes custom software engineering, service engineering, data and analytics platforms, automation capabilities, and AI-enabled solutions. In partnership with business and technology leaders, this role establishes priorities, investment strategies, modernization roadmaps, and governance frameworks to ensure technology capabilities align with organizational objectives and deliver measurable business value. As a senior technology leader, the Vice President is thought leader; accountable for portfolio health, service performance, strategic planning, resource allocation, financial stewardship, talent development, risk management, cybersecurity and regulatory compliance, and the successful delivery of technology initiatives. The role fosters a culture of innovation, operational excellence, and continuous improvement while advancing Providence's digital transformation agenda and maximizing the impact of technology investments across EBAT." We can put that as
. Responsibilities: from "Accountabilities Include The Following Operational Categories" list: Support of functional business partners and executives; Identification and assessment of technical road maps and requirements; Sponsorship of implementation activities; Production support of assigned applications; Support of and maximization of application usefulness; Effective management of vendor relationships. Also "This position is responsible for leading, mentoring and developing leaders, managers as well as other staff." "This position will work in close collaboration with executives, directors, managers and other leaders and staff across the system." "This position will create and successfully execute strategic plans for highly complex issues involving business and information services operations and support." "It will also work to standardize complex and disparate processes and methodologies related to application management such as design, deployment, support and life cycle." Then Essential Functions broken into Strategic, Management, Operational. Those are more detailed responsibilities. We could combine all into a responsibilities list. But we must not invent or summarize away detail; we can list each bullet as
- . Ensure we capture all.
Let's list responsibilities bullets:
- Support of functional business partners and executives
- Identification and assessment of technical road maps and requirements
- Sponsorship of implementation activities
- Production support of assigned applications
- Support of and maximization of application usefulness
- Effective management of vendor relationships
- Leading, mentoring and developing leaders, managers and other staff
- Working in close collaboration with executives, directors, managers and other leaders and staff across the system
- Creating and successfully executing strategic plans for highly complex issues involving business and information services operations and support
- Standardizing complex and disparate processes and methodologies related to application management (design, deployment, support and life cycle)
Then Strategic responsibilities (list):
- Responsible for the development of enterprise business application digital transformation strategy and roadmap
- Develops long term strategy of AI, ML and RPA technologies (note duplicate line appears twice; we should include only once)
- Responsible for the pre M&A due diligence and post M&A integration strategy for new affiliations and maintenance of legacy systems
- Responsible for the post M&A technical conversion of new affiliations
- Creates and executes the long term enterprise application integration strategy program for EBAT operations and technology
- Maintains relationships with key business partners and other senior leaders in the IT industry in order to leverage best practices, evaluate and manage emerging application technologies
- Directs adoption process for introducing and implementing new services, technologies and/or applications into Information Services
- Implements appropriate service delivery models for core application functions in defining, delivering, and improving services for the enterprise and its customers
- Responsible for working with leaders of IS Strategy and Business Development in ensuring adherence to standards, and continuously evaluating the effectiveness of application systems
- Ensures that the Applications division supports IS services and systems effectively and meets the needs of the business
- Participates in the development of the overall IS strategic plan by identifying needed application management strategies and projects that support business needs
- Manages customer expectations regarding the success of each Information Services strategy and project; ensures measurable outcomes are defined and reported for each strategy or project
- Partners with key stakeholders and customers to implement application services for strategic initiatives that are effective, user-friendly and accurate
Management responsibilities:
- Manages overall technology program budget and the establishment of project financials and controls
- Develops and negotiates preferred information technology vendor contracts and manages key vendor relationships
- Manages strategic vendor relationships, ensuring financial, compliance, and service level goals are achieved
- Ensures the performance of applications within their domain and evaluates the performance of services on the basis of specific KPIs
- Oversees budgeting and expenditures for applications, staff and services within their span of control
- Assists in the development of and monitors compliance with policies and procedures for Application Services that impact all of Providence St. Joseph Health
- Attracts, hires, trains, motivates, retains, and develops a team of first-rate professionals to perform the responsibilities of applications management
- Designs, implements, maintains, and operates departmental Service Level Agreements, Operating Level Agreements, and associated KPIs
- Demonstrates the ability to build an organization and provide responsive leadership; to delegate, coordinate and motivate staff, and to evaluate performance
- Demonstrates ability to coordinate and facilitate teamwork with multidisciplinary groups, building and reaching consensus; agreeing upon a course of action where there are multiple perspectives
- Demonstrates outstanding organizational skills, as well as the ability to manage shifting priorities
Operational responsibilities:
- Plans for monthly and quarterly releases
- Provides leadership for all support activities
- Develops budgets and expenditures for information services related to applications in partnership with other leaders and the PMO
- Provides executive leadership on critical issues, problems or delays in production, projects or any other issues that have an impact on the customer
- Leads process optimization and initiatives to improve service delivery, increase value and promote customer service
- Maintains the delivery of secure, reliable, and scalable applications and processes that support the growth and financial objectives of Providence St. Joseph Health
- Teams with the business and other IS disciplines to develop and maintain appropriate disaster recovery architecture, projects, and policies and participates in disaster drills for applications
We could combine all into one responsibilities list, but that would be huge. Still acceptable.
Requirements: maybe we treat Qualifications as separate heading; Requirements maybe not needed. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes under Requirements vs Qualifications vs Skills. Typically Requirements could be education/experience; Qualifications could be credentials; Skills could be capabilities. But we have both Education & Credentials, Experience & Expertise, Professional & Leadership Capabilities. We could map:
- Requirements: Education & Credentials + Experience & Expertise (maybe combined)
- Qualifications: maybe not needed if we already used Requirements; but we could put Qualifications as Education & Credentials (or combine). However we must not create empty sections. We need to decide.
Better: Use Requirements for education and experience (the must-haves). Use Qualifications for preferred qualifications (Master's degree preferred). Use Skills for professional & leadership capabilities.
But the posting has "Education & Credentials" (Bachelor's required, Master's preferred). "Experience & Expertise" (various years). Then "Professional & Leadership Capabilities". So we can assign:
- Requirements: Education & Credentials (Bachelor's required) + Experience & Expertise (the years etc.)
- Qualifications: maybe Master's degree preferred (but that's part of Education & Credentials). Could also include "Healthcare knowledge and experience preferred." etc. But we might just put Qualifications as the preferred qualifications (Master's degree preferred, Healthcare knowledge preferred, etc.) but we risk duplication.
Simplify: Use Requirements for Education & Credentials + Experience & Expertise (all required). Use Skills for Professional & Leadership Capabilities. Omit Qualifications section (or combine into Requirements). But we need to follow instruction: include a section ONLY when posting has real, specific content for it. If we omit Qualifications, that's fine.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
Now we need to format.
For Requirements, we have list items: Education & Credentials (Bachelor's Degree in ...; Master's Degree ... preferred). Experience & Expertise (multiple bullet points). We'll create