AI Automation and Integration Lead
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, legal, etc. Must not invent or summarize away detail. Must not create sections with placeholder text.
We need to parse the posting.
The posting starts: "The AI Automation and Integration Lead is an individual contributor and cross-functional process leader responsible for connecting enterprise data, modernizing business workflows, and delivering secure AI-enabled solutions. Working directly with the Business Development organization, IT, Security, data owners, and other business stakeholders, this role turns high-value business needs into reliable integrations, governed automations, and measurable process improvements. The role combines enterprise integration, business process leadership, AI engineering, and security-by-design. The successful candidate will establish practical technical standards, lead discovery and prioritization, guide solutions from architecture through adoption, and remain hands-on in building APIs, connectors, data pipelines, automations, copilots, and intelligent agents."
That's like an overview. Could be "About the role" section.
Then "You Will Be Accountable For Enterprise Data Connections and Integration" with bullet-like sentences. Then "Process Leadership and Automation", "Security Governance and Responsible AI", "AI and Intelligent Automation", "Data and Analytics", "Microsoft GCC High Environment". Those could be under "Responsibilities". Or we could make separate sections for each? The instruction: Prefer a few substantive sections over many thin ones. So we could group responsibilities under a single "Responsibilities" section with sub-bullets. But we need to preserve all substantive info; we can keep bullet points under responsibilities.
Then "Qualifications" section includes required qualifications: US Citizenship, Bachelor's degree, onsite requirement, 3-5+ years experience, etc. Then "Preferred Experience" list.
Then there is a company description paragraph: "SHAPING THE FUTURE THROUGH INNOVATION AND DISCOVERY! ..." That's about the company; could be "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under "About the role"? Might be okay but it's about company. However we must not invent sections not in list. Could we put it under "About the role"? It's not exactly about the role but could be considered part of role description. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples but we should use those headings when appropriate. It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should stick to those.
Thus we need to map content to these headings.
- About the role: overview paragraph(s) describing role purpose, maybe also company description? Could include the "SHAPING THE FUTURE..." as part of about the role? Might be okay.
- Responsibilities: all the bullet-like duties under "You Will Be Accountable For..." sections.
- Requirements: maybe the mandatory qualifications (US Citizenship, degree, onsite, years experience, etc.) Could be under Requirements.
- Qualifications: maybe the preferred experience? Or we could combine required and preferred under Qualifications? But we have both Requirements and Qualifications headings. Typically Requirements are mandatory, Qualifications are desired. So we can put mandatory under Requirements, preferred under Qualifications.
- Skills: maybe we could list technical skills from preferred experience (APIs, languages, etc.) but we already have them in preferred experience. Could move to Skills.
- Benefits, Pay, Schedule: we need to see if posting includes any. It mentions "We offer our employees an attractive compensation package with competitive salaries and comprehensive benefits, including health and wellness programs, career development, generous retirement savings plan with company match and more!" That's benefits info. No specific pay or schedule details besides onsite requirement (up to one week/month). That could be schedule? It says "Able to be onsite at our Plano or Kilgore, TX locations up to one week/month." That's a schedule expectation. So we can include Schedule section with that detail. Benefits section can include the benefits description. Pay: no specific salary mentioned, so we should NOT create Pay section because it would be placeholder. So omit Pay.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule.
We must not include empty sections.
Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. We need to keep details but can format as - for lists. For prose, use
.
We must not include boilerplate like EEO, legal, etc. The posting includes an EEO statement at the end: "CPI is proud to be an Equal Opportunity and Affirmative Action employer..." That's boilerplate; must remove.
Also remove navigation, cookie, legal, duplicated lines, application instructions. There's none.
Now let's extract.
About the role: The first paragraph(s) up to maybe before "You Will Be Accountable For". Also maybe include the company description? The company description is after "SHAPING THE FUTURE THROUGH INNOVATION AND DISCOVERY!" It's about the company, not the role. Could we include it under About the role? It's not exactly about the role but could be considered context. However the instruction says preserve ALL substantive information; we must not omit company description. If we don't have a heading for it, we could still include it as a paragraph under About the role (makes sense). It's substantive. So we will include it.
Thus About the role content:
- First paragraph: "The AI Automation and Integration Lead is an individual contributor and cross-functional process leader responsible for connecting enterprise data, modernizing business workflows, and delivering secure AI-enabled solutions. Working directly with the Business Development organization, IT, Security, data owners, and other business stakeholders, this role turns high-value business needs into reliable integrations, governed automations, and measurable process improvements. The role combines enterprise integration, business process leadership, AI engineering, and security-by-design. The successful candidate will establish practical technical standards, lead discovery and prioritization, guide solutions from architecture through adoption, and remain hands-on in building APIs, connectors, data pipelines, automations, copilots, and intelligent agents."
- Then company description: "SHAPING THE FUTURE THROUGH INNOVATION AND DISCOVERY! With a history spanning more than seven decades, Communications & Power Industries’ thousands of products have impacted people’s lives in numerous unseen ways every day. Our highly engineered products serve as the backbone of modern-day commercial and military communications systems, assist in diagnosing medical conditions, empower scientific discoveries and space exploration, and much more. CPI is headquartered in Plano, Texas and is a global manufacturer of electronic components and subsystems. We have manufacturing locations in the United States, Canada, Europe, and Asia. With a heritage of technological excellence, our team serves customers in the communications, defense, medical, industrial, and scientific markets."
We could combine into one or multiple
tags.
Now Responsibilities: All the bullet-like duties under the headings:
"You Will Be Accountable For Enterprise Data Connections and Integration" then list of items each starting with a verb.
Then "Process Leadership and Automation" list.
Then "Security Governance and Responsible AI" list.
Then "AI and Intelligent Automation" list.
Then "Data and Analytics" list.
Then "Microsoft GCC High Environment" list.
We need to preserve each item as a
- . We should not lose any detail.
Let's extract each.
Enterprise Data Connections and Integration:
- Lead the strategy, architecture, delivery, and operational health of connections among business applications, data platforms, AI services, and external systems.
- Design and implement secure integrations using APIs, enterprise connectors, webhooks, event-based patterns, file exchanges, data pipelines, and other appropriate methods.
- Define source-to-target mappings, transformation rules, data contracts, validation controls, and error-handling standards that keep connected data accurate, complete, traceable, and recoverable.
- Partner with system owners and data stewards to clarify ownership, authoritative sources, master and reference data, retention needs, and permitted uses of information.
- Establish reusable integration patterns and technical standards for authentication, authorization, secrets, service accounts, versioning, logging, monitoring, retries, reconciliation, and support.
Process Leadership and Automation:
- Lead structured discoveries with business stakeholders to document current-state processes, identify control gaps and bottlenecks, and design practical future-state workflows.
- Facilitate decisions across business, IT, Security, Legal, Compliance, and data-owner groups; make responsibilities, tradeoffs, approvals, and escalation paths explicit.
- Lead initiatives from intake and requirements through design, testing, change management, deployment, training, operational handoff, and benefits realization.
- Develop process, documentation, and solution standards that enable repeatable delivery across teams while reducing one-off tools and unmanaged workflows.
Security Governance and Responsible AI:
- Evaluate integration risks and dependencies, including data sensitivity, interface limits, vendor constraints, environment boundaries, and downstream business impact.
- Embed security and privacy requirements throughout solution design, including data classification, least-privilege access, segregation of duties, encryption, secure credential handling, and appropriate retention.
- Perform solution-level risk assessments and threat modeling; document data exposure, trust boundaries, failure modes, control requirements, and residual risk before production release.
- Establish governance for AI solutions, including approved data use, grounding sources, human oversight, output validation, model and prompt change control, and monitoring for quality and misuse.
- Ensure solutions comply with company policies, contractual obligations, export-control requirements, and applicable regulatory or customer requirements.
AI and Intelligent Automation:
- Identify and deliver use cases where AI, intelligent agents, and automation improve productivity, accuracy, responsiveness, or decision-making.
- Architect, prototype, build, test, deploy, and support AI-enabled solutions using Microsoft Copilot Studio, Azure AI, OpenAI, Power Platform, and other approved enterprise technologies.
- Integrate AI solutions with governed enterprise data and applications while maintaining clear permissions, provenance, logging, and human review.
- Evaluate emerging technologies and recommend adoption only when the business case, security posture, support model, and operational readiness are clear.
- Measure deployed solutions for accuracy, performance, adoption, cost, control effectiveness, and business impact; improve or retire them based on evidence.
Data and Analytics:
- Develop or enhance governed dashboards, reports, and analytical tools using Power BI, Excel, SQL, or similar technologies.
- Define and validate metrics, data lineage, reconciliation rules, and quality checks so decision-makers can trust reported information.
- Support data preparation and retrieval patterns for AI, automation, reporting, and operational decision-making.
Microsoft GCC High Environment:
- Architect, develop, and support solutions within Microsoft GCC High and approved connected environments.
- Confirm that services, connectors, data locations, and deployment patterns are authorized for the intended data and use case before implementation.
- Partner with IT and Security on environment architecture, identity, tenant configuration, data-loss prevention, audit logging, monitoring, and troubleshooting.
- Maintain production-ready documentation for architectures, integrations, data flows, controls, operating procedures, recovery steps, and technical decisions.
Now Requirements (mandatory):
- U.S. Citizenship Required: Due to government contract and facility security requirements, this position is limited to U.S. citizens. Candidates requiring employment authorization through an EAD, visa, or other non-citizen work authorization are not eligible for consideration.
- Bachelor's degree in Computer Science, Information Systems, Artificial Intelligence, Data Science, Software Engineering, Cybersecurity, Business Analytics, Information Technology, or a related field.
- Able to be onsite at our Pl
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should stick to those.
Thus we need to map content to these headings.
- About the role: overview paragraph(s) describing role purpose, maybe also company description? Could include the "SHAPING THE FUTURE..." as part of about the role? Might be okay.
- Responsibilities: all the bullet-like duties under "You Will Be Accountable For..." sections.
- Requirements: maybe the mandatory qualifications (US Citizenship, degree, onsite, years experience, etc.) Could be under Requirements.
- Qualifications: maybe the preferred experience? Or we could combine required and preferred under Qualifications? But we have both Requirements and Qualifications headings. Typically Requirements are mandatory, Qualifications are desired. So we can put mandatory under Requirements, preferred under Qualifications.
- Skills: maybe we could list technical skills from preferred experience (APIs, languages, etc.) but we already have them in preferred experience. Could move to Skills.
- Benefits, Pay, Schedule: we need to see if posting includes any. It mentions "We offer our employees an attractive compensation package with competitive salaries and comprehensive benefits, including health and wellness programs, career development, generous retirement savings plan with company match and more!" That's benefits info. No specific pay or schedule details besides onsite requirement (up to one week/month). That could be schedule? It says "Able to be onsite at our Plano or Kilgore, TX locations up to one week/month." That's a schedule expectation. So we can include Schedule section with that detail. Benefits section can include the benefits description. Pay: no specific salary mentioned, so we should NOT create Pay section because it would be placeholder. So omit Pay.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule.
We must not include empty sections.
Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. We need to keep details but can format as - for lists. For prose, use
.
We must not include boilerplate like EEO, legal, etc. The posting includes an EEO statement at the end: "CPI is proud to be an Equal Opportunity and Affirmative Action employer..." That's boilerplate; must remove.
Also remove navigation, cookie, legal, duplicated lines, application instructions. There's none.
Now let's extract.
About the role: The first paragraph(s) up to maybe before "You Will Be Accountable For". Also maybe include the company description? The company description is after "SHAPING THE FUTURE THROUGH INNOVATION AND DISCOVERY!" It's about the company, not the role. Could we include it under About the role? It's not exactly about the role but could be considered context. However the instruction says preserve ALL substantive information; we must not omit company description. If we don't have a heading for it, we could still include it as a paragraph under About the role (makes sense). It's substantive. So we will include it.
Thus About the role content:
- First paragraph: "The AI Automation and Integration Lead is an individual contributor and cross-functional process leader responsible for connecting enterprise data, modernizing business workflows, and delivering secure AI-enabled solutions. Working directly with the Business Development organization, IT, Security, data owners, and other business stakeholders, this role turns high-value business needs into reliable integrations, governed automations, and measurable process improvements. The role combines enterprise integration, business process leadership, AI engineering, and security-by-design. The successful candidate will establish practical technical standards, lead discovery and prioritization, guide solutions from architecture through adoption, and remain hands-on in building APIs, connectors, data pipelines, automations, copilots, and intelligent agents."
- Then company description: "SHAPING THE FUTURE THROUGH INNOVATION AND DISCOVERY! With a history spanning more than seven decades, Communications & Power Industries’ thousands of products have impacted people’s lives in numerous unseen ways every day. Our highly engineered products serve as the backbone of modern-day commercial and military communications systems, assist in diagnosing medical conditions, empower scientific discoveries and space exploration, and much more. CPI is headquartered in Plano, Texas and is a global manufacturer of electronic components and subsystems. We have manufacturing locations in the United States, Canada, Europe, and Asia. With a heritage of technological excellence, our team serves customers in the communications, defense, medical, industrial, and scientific markets."
We could combine into one or multiple
tags.
Now Responsibilities: All the bullet-like duties under the headings:
"You Will Be Accountable For Enterprise Data Connections and Integration" then list of items each starting with a verb.
Then "Process Leadership and Automation" list.
Then "Security Governance and Responsible AI" list.
Then "AI and Intelligent Automation" list.
Then "Data and Analytics" list.
Then "Microsoft GCC High Environment" list.
We need to preserve each item as a
- . We should not lose any detail.
Let's extract each.
Enterprise Data Connections and Integration:
- Lead the strategy, architecture, delivery, and operational health of connections among business applications, data platforms, AI services, and external systems.
- Design and implement secure integrations using APIs, enterprise connectors, webhooks, event-based patterns, file exchanges, data pipelines, and other appropriate methods.
- Define source-to-target mappings, transformation rules, data contracts, validation controls, and error-handling standards that keep connected data accurate, complete, traceable, and recoverable.
- Partner with system owners and data stewards to clarify ownership, authoritative sources, master and reference data, retention needs, and permitted uses of information.
- Establish reusable integration patterns and technical standards for authentication, authorization, secrets, service accounts, versioning, logging, monitoring, retries, reconciliation, and support.
Process Leadership and Automation:
- Lead structured discoveries with business stakeholders to document current-state processes, identify control gaps and bottlenecks, and design practical future-state workflows.
- Facilitate decisions across business, IT, Security, Legal, Compliance, and data-owner groups; make responsibilities, tradeoffs, approvals, and escalation paths explicit.
- Lead initiatives from intake and requirements through design, testing, change management, deployment, training, operational handoff, and benefits realization.
- Develop process, documentation, and solution standards that enable repeatable delivery across teams while reducing one-off tools and unmanaged workflows.
Security Governance and Responsible AI:
- Evaluate integration risks and dependencies, including data sensitivity, interface limits, vendor constraints, environment boundaries, and downstream business impact.
- Embed security and privacy requirements throughout solution design, including data classification, least-privilege access, segregation of duties, encryption, secure credential handling, and appropriate retention.
- Perform solution-level risk assessments and threat modeling; document data exposure, trust boundaries, failure modes, control requirements, and residual risk before production release.
- Establish governance for AI solutions, including approved data use, grounding sources, human oversight, output validation, model and prompt change control, and monitoring for quality and misuse.
- Ensure solutions comply with company policies, contractual obligations, export-control requirements, and applicable regulatory or customer requirements.
AI and Intelligent Automation:
- Identify and deliver use cases where AI, intelligent agents, and automation improve productivity, accuracy, responsiveness, or decision-making.
- Architect, prototype, build, test, deploy, and support AI-enabled solutions using Microsoft Copilot Studio, Azure AI, OpenAI, Power Platform, and other approved enterprise technologies.
- Integrate AI solutions with governed enterprise data and applications while maintaining clear permissions, provenance, logging, and human review.
- Evaluate emerging technologies and recommend adoption only when the business case, security posture, support model, and operational readiness are clear.
- Measure deployed solutions for accuracy, performance, adoption, cost, control effectiveness, and business impact; improve or retire them based on evidence.
Data and Analytics:
- Develop or enhance governed dashboards, reports, and analytical tools using Power BI, Excel, SQL, or similar technologies.
- Define and validate metrics, data lineage, reconciliation rules, and quality checks so decision-makers can trust reported information.
- Support data preparation and retrieval patterns for AI, automation, reporting, and operational decision-making.
Microsoft GCC High Environment:
- Architect, develop, and support solutions within Microsoft GCC High and approved connected environments.
- Confirm that services, connectors, data locations, and deployment patterns are authorized for the intended data and use case before implementation.
- Partner with IT and Security on environment architecture, identity, tenant configuration, data-loss prevention, audit logging, monitoring, and troubleshooting.
- Maintain production-ready documentation for architectures, integrations, data flows, controls, operating procedures, recovery steps, and technical decisions.
Now Requirements (mandatory):
- U.S. Citizenship Required: Due to government contract and facility security requirements, this position is limited to U.S. citizens. Candidates requiring employment authorization through an EAD, visa, or other non-citizen work authorization are not eligible for consideration.
- Bachelor's degree in Computer Science, Information Systems, Artificial Intelligence, Data Science, Software Engineering, Cybersecurity, Business Analytics, Information Technology, or a related field.
- Able to be onsite at our Pl
. We must not include boilerplate like EEO, legal, etc. The posting includes an EEO statement at the end: "CPI is proud to be an Equal Opportunity and Affirmative Action employer..." That's boilerplate; must remove. Also remove navigation, cookie, legal, duplicated lines, application instructions. There's none. Now let's extract. About the role: The first paragraph(s) up to maybe before "You Will Be Accountable For". Also maybe include the company description? The company description is after "SHAPING THE FUTURE THROUGH INNOVATION AND DISCOVERY!" It's about the company, not the role. Could we include it under About the role? It's not exactly about the role but could be considered context. However the instruction says preserve ALL substantive information; we must not omit company description. If we don't have a heading for it, we could still include it as a paragraph under About the role (makes sense). It's substantive. So we will include it. Thus About the role content: - First paragraph: "The AI Automation and Integration Lead is an individual contributor and cross-functional process leader responsible for connecting enterprise data, modernizing business workflows, and delivering secure AI-enabled solutions. Working directly with the Business Development organization, IT, Security, data owners, and other business stakeholders, this role turns high-value business needs into reliable integrations, governed automations, and measurable process improvements. The role combines enterprise integration, business process leadership, AI engineering, and security-by-design. The successful candidate will establish practical technical standards, lead discovery and prioritization, guide solutions from architecture through adoption, and remain hands-on in building APIs, connectors, data pipelines, automations, copilots, and intelligent agents." - Then company description: "SHAPING THE FUTURE THROUGH INNOVATION AND DISCOVERY! With a history spanning more than seven decades, Communications & Power Industries’ thousands of products have impacted people’s lives in numerous unseen ways every day. Our highly engineered products serve as the backbone of modern-day commercial and military communications systems, assist in diagnosing medical conditions, empower scientific discoveries and space exploration, and much more. CPI is headquartered in Plano, Texas and is a global manufacturer of electronic components and subsystems. We have manufacturing locations in the United States, Canada, Europe, and Asia. With a heritage of technological excellence, our team serves customers in the communications, defense, medical, industrial, and scientific markets." We could combine into one or multiple
tags. Now Responsibilities: All the bullet-like duties under the headings: "You Will Be Accountable For Enterprise Data Connections and Integration" then list of items each starting with a verb. Then "Process Leadership and Automation" list. Then "Security Governance and Responsible AI" list. Then "AI and Intelligent Automation" list. Then "Data and Analytics" list. Then "Microsoft GCC High Environment" list. We need to preserve each item as a