AI Workflow Architect
Celestica · Hillsborough County, NH · 1 mo ago
Art & Creative$95k–$126k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role (maybe Summary?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes Summary (maybe "Summary" as about the role). Detailed Description includes responsibilities. Knowledge/Skills/Competencies includes skills. Physical Demands maybe not needed. Salary includes Pay. Benefits: mentions "comprehensive benefits package offered in addition to this range." That's a benefit mention, but not specific details. Should we include Benefits? The rule: never create Benefits section unless posting actually states them. It states "A comprehensive benefits package is offered in addition to this range." That's a statement about benefits, albeit generic. It's still stating benefits exist. Should we include Benefits section with that statement? Probably yes, as it's real content (though generic). However rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "A comprehensive benefits package is offered" is not filler placeholder; it's a statement. So we can include Benefits with that sentence.
Pay: Salary Range $95,000 to $126k. Also note includes base salary and target STI. That's specific. So include Pay.
Schedule: Not mentioned. No schedule info. So omit.
Requirements vs Qualifications: The posting includes "Typical Experience" and "Typical Education". Those could be Requirements/Qualifications. We need to decide which heading to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include both Requirements and Qualifications if content distinct. Typically Requirements: experience, education. Qualifications: maybe skills? But we already have Skills section for knowledge/skills/competencies. So we can put Requirements: Experience and Education. Qualifications maybe not needed. Could combine. But we should not create empty sections. Let's include Requirements (Experience & Education). Qualifications maybe not needed.
Skills: Knowledge/Skills/Competencies section.
About the role: Summary paragraph.
Responsibilities: Detailed Description bullet list.
Now we need to format lists with
- . For prose use
. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Also remove "Notes", "Company Overview", etc. Also remove "Physical Demands" maybe not needed as not a standard heading; but we could ignore it. We must preserve all substantive information. So we need to include the content from Summary, Detailed Description, Knowledge/Skills/Competencies, Salary, Benefits, Typical Experience/Education. We must not invent or summarize away detail. So we need to keep details as is, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can reformat. Likely we should keep the sentences essentially same. We'll produce HTML fragment:
About the role
The Advisor, Business Development is a specialized role in which the incumbent applies expertise across multiple customer sets, addressing diverse challenges informed by experience and guidance from senior departmental members.
Responsibilities
- Use Case Identification & Strategy: Partner with cross-functional leaders (Operations, Business Development, Supply Chain) to surface high-value opportunities for Generative AI and process automation.
- AI Agent & Workflow Architecture: Design, prompt, and test AI agents and automated workflows to synthesize unstructured data, accelerate quote/proposal analysis, and streamline technical documentation.
- Outcome Measurement & Governance: Establish clear baseline metrics, monitor ROI (e.g., hours saved, cycle time reduction, error mitigation), and ensure AI deployments align with enterprise safety and quality standards.
- Pilot & Rollout Management: Scope pilot programs, lead discovery workshops, and oversee user acceptance testing for internal AI tool rollouts.
- Change Management & Upskilling: Act as an internal AI champion, training teams on effective prompt engineering, best practices, and integrating AI tools into daily standard operating procedures.
- Product & IT Liaison: Translate business needs into clear technical specifications for IT and software development teams to continuously refine internal AI infrastructure.
- Working with the Customer Business Unit team, supports any quote activity within a specific customer set.
- Works with more senior Business Development team members to develop bids, proposals and presentation packages for customers.
- Works with the Marketing group to research and summarize information relating to a specific customer’s market, strategies and direction, market share, strengths, weaknesses and competition.
- Applies knowledge to support the team in executing strategy.
- Arranges and coordinates details pertaining to customer visits and audits (including confidentiality agreement activity, visit preparation and logistics).
- Completes customer submitted surveys, self audit forms and information requests.
- Tracks and presents win/loss analysis for customers.
- Performs customer forecast rollups for the sites.
- Collects, reviews and analyzes customer data and market intelligence from all sources.
Requirements
Experience: 3–5+ years in operational consulting, product management, business analytics, or solutions architecture with demonstrated execution in AI adoption.
Education: Bachelor’s degree in Business, Industrial Engineering, Computer Science, Data Analytics, or equivalent combination of education and practical experience.
Skills
- AI & Prompt Engineering: Hands-on experience crafting prompts, building workflow automations, and configuring AI agents using modern LLM platforms (e.g., OpenAI, Claude, enterprise search platforms).
- Process Optimization: Proven ability to map business processes, pinpoint inefficiencies, and redesign workflows around AI capabilities.
- Business Acumen: Understanding of global manufacturing, supply chain logistics, or enterprise B2B sales cycles.
- Stakeholder Management: Strong communication skills with the ability to influence cross-functional teams and present actionable insights to senior executives.
- Data Fluency: Familiarity with business intelligence platforms (e.g., Power BI) to track adoption and operational performance metrics.
- Excellent communication skills (both verbal and written).
- Strong business acumen, interpersonal, and time management skills.
- Ability to function independently and as a member of a team.
- Ability to work with and influence other individuals.
- Strong administration, prioritization, and logistics/coordination skills.
- Knowledge of Microsoft Office and Google Suite.
- Some background in complex problem management and resolution.
Benefits
A comprehensive benefits package is offered in addition to this range.
Pay
The stated range includes Base Salary and target Short-Term Incentive (STI) compensation only. Salary Range $95,000 to $126k.
We should also include location info? Not a standard heading; maybe ignore. The posting includes Location: remote, with travel as necessary, open to candidates near certain US locations. Could be considered under "About the role" or maybe a separate section? Not in allowed headings. Could incorporate into About the role paragraph. But we must preserve all substantive information. The location info is substantive. We could add a sentence in About the role: "This is a remote position, with travel as necessary. We are open to considering candidates close to any of our US locations in Massachusetts, Pennsylvania, Minnesota, Texas, Arizona, Oregon or California as well as locations near major airports such as the Northeast, Southeast, Midwest and Pacific Coast." That preserves info. We should also include "Typical Experience" and "Typical Education" we already did. We should also include "Bonus points for experience working with Hyperscaler and Enterprise customers on data management equipment" - that's part of Typical Experience? Actually it's under Typical Experience paragraph: "Bonus points for experience working with Hyperscaler and Enterprise customers on data management equipment". We need to include that. So add to Experience bullet or sentence. Let's adjust Experience paragraph: "Experience: 3–5+ years in operational consulting, product management, business analytics, or solutions architecture with demonstrated execution in AI adoption. Bonus points for experience working with Hyperscaler and Enterprise customers on data management equipment." Now ensure we didn't miss any substantive info: The Summary also includes "The Advisor, Business Development is a specialized role..." we used that. Also "The responsibilities include supporting quotation activities, developing bids and proposals, conducting market research, coordinating customer visits, and analyzing customer and market data." That's covered in responsibilities list but we might want to include that as a separate bullet? The Detailed Description already includes many items; but the summary sentence is a high-level overview. We could add it as a bullet or incorporate into responsibilities. Since we must preserve all substantive info, we should include that sentence somewhere. Could add as first bullet under Responsibilities: "Supports quotation activities, develops bids and proposals, conducts market research, coordinates customer visits, and analyzes customer and market data." But we already have many detailed bullets; still we should include it to not lose info. Let's add as first bullet. Also the Detailed Description includes "Performs tasks such as, but not limited to, the following:" then list. We already captured list. Now check for any other substantive info: "Physical Demands" details: normal office environment, extended sitting, visual concentration, repetitive manual movements, overnight travel may be required. This is substantive but not under standard headings. Could we add a section? Not in allowed headings. Could we incorporate into About the role or Responsibilities? Probably not appropriate. But we must preserve all substantive information. The instruction says we should only include sections when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It didn't say we cannot add other headings not in the list; but the list is examples. It says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections, but we could also use other headings if needed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; we should stick to them. However we need to preserve all substantive info; if we omit Physical Demands, we lose info. Could we fold Physical Demands into About the role or Responsibilities? It's not really about role or responsibilities but working conditions. Could we add a section "Working Conditions"? Not in list but maybe acceptable as it's a section heading. The examples are not exhaustive; they say e.g. So we could add a heading for Working Conditions. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe, we could add a section "Working Conditions". However the instruction also says "Prefer a few substantive sections over many thin ones." Adding a thin section may be okay if it has content. But we must also avoid creating sections with filler. Physical Demands has specific content, so it's okay. Thus we add
Working Conditions
withcontaining the details. Also we have "Notes" about job description not exhaustive etc. That's boilerplate? It's generic but still substantive? It's a note about job description not exhaustive; could be considered boilerplate. Likely we can drop it