Forward Deployed AI Architect
Alzheimer's Association - Orange County Chapter · Chicago, IL · 3 wk ago
Art & Creative$155k/yrFull-time
We need to output HTML fragment with headings for sections: 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 (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove sections like "Position Summary" maybe part of About the role. We need to map content.
Let's parse the posting.
Key sections:
- Position Summary (first paragraph) -> could be About the role.
- Essential Responsibilities (list) -> Responsibilities.
- Required Qualifications -> Requirements? Actually "Required Qualifications" could be Requirements.
- Preferred Qualifications -> maybe Qualifications? But we have separate sections: Requirements, Qualifications, Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have "Required Qualifications" (bullet list) -> could be Requirements.
We have "Preferred Qualifications" -> could be Qualifications.
We have "Knowledge, Skills & Abilities" -> Skills.
We have "Physical & Practical Requirements" -> maybe part of Requirements? But we already used Requirements for Required Qualifications. Could incorporate physical requirements into Requirements or maybe separate? But we only have headings listed; we can include Physical & Practical Requirements under Requirements or maybe under Skills? Probably better to include under Requirements as they are requirements.
We have "Location: US Remote Work Schedule: Full-Time (37.5 hours per week)" -> Schedule and Location. Location maybe not a heading; we could put location in About the role or maybe not needed. Schedule heading: we have schedule info.
We have "Reports To: Sr. Director, AI + Digital Transformation" -> could be in About the role.
We have "Position Grade & Compensation: Grade 512 The Alzheimer’s Association’s good faith expectation for the salary range for this role is $155,000-$168,000. This position is eligible for a bonus based on both individual and organizational performance, up to 6%" -> Pay section.
We have benefits description later: "Employees working 24 hours/week or more are eligible for a comprehensive benefits package, including medical, dental, vision, flex accounts, short and long-term disability, life insurance, long term care insurance, tuition reimbursement, generous Paid Time Off, 12 annual holidays and Paid Family Leave, as well as an annual Cultural & Heritage Day and Volunteer Day of their choosing. They are also eligible for our gold standard 401(k) retirement plan. Please click HERE for more information. Full time employees (37.5 hours/week), will enjoy all of the above plus an annual School Visitation Day and an Elder Care Facility Day of their choosing." -> Benefits section.
We also have EEO etc which we must remove.
We also have "Qualified Applicants with arrest or Conviction records..." etc - that's legal/EEO, remove.
We also have background check details - remove.
We also have mission statements etc - maybe part of About the role? Could include but not boilerplate? The mission statement is substantive about organization; we can include in About the role.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep details like responsibilities list, qualifications, etc.
We must not include headings with filler text. So we need to ensure each heading has content.
Let's craft sections:
for sections: 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 (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove sections like "Position Summary" maybe part of About the role. We need to map content.
Let's parse the posting.
Key sections:
- Position Summary (first paragraph) -> could be About the role.
- Essential Responsibilities (list) -> Responsibilities.
- Required Qualifications -> Requirements? Actually "Required Qualifications" could be Requirements.
- Preferred Qualifications -> maybe Qualifications? But we have separate sections: Requirements, Qualifications, Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have "Required Qualifications" (bullet list) -> could be Requirements.
We have "Preferred Qualifications" -> could be Qualifications.
We have "Knowledge, Skills & Abilities" -> Skills.
We have "Physical & Practical Requirements" -> maybe part of Requirements? But we already used Requirements for Required Qualifications. Could incorporate physical requirements into Requirements or maybe separate? But we only have headings listed; we can include Physical & Practical Requirements under Requirements or maybe under Skills? Probably better to include under Requirements as they are requirements.
We have "Location: US Remote Work Schedule: Full-Time (37.5 hours per week)" -> Schedule and Location. Location maybe not a heading; we could put location in About the role or maybe not needed. Schedule heading: we have schedule info.
We have "Reports To: Sr. Director, AI + Digital Transformation" -> could be in About the role.
We have "Position Grade & Compensation: Grade 512 The Alzheimer’s Association’s good faith expectation for the salary range for this role is $155,000-$168,000. This position is eligible for a bonus based on both individual and organizational performance, up to 6%" -> Pay section.
We have benefits description later: "Employees working 24 hours/week or more are eligible for a comprehensive benefits package, including medical, dental, vision, flex accounts, short and long-term disability, life insurance, long term care insurance, tuition reimbursement, generous Paid Time Off, 12 annual holidays and Paid Family Leave, as well as an annual Cultural & Heritage Day and Volunteer Day of their choosing. They are also eligible for our gold standard 401(k) retirement plan. Please click HERE for more information. Full time employees (37.5 hours/week), will enjoy all of the above plus an annual School Visitation Day and an Elder Care Facility Day of their choosing." -> Benefits section.
We also have EEO etc which we must remove.
We also have "Qualified Applicants with arrest or Conviction records..." etc - that's legal/EEO, remove.
We also have background check details - remove.
We also have mission statements etc - maybe part of About the role? Could include but not boilerplate? The mission statement is substantive about organization; we can include in About the role.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep details like responsibilities list, qualifications, etc.
We must not include headings with filler text. So we need to ensure each heading has content.
Let's craft sections:
About the role
-> include position summary, reporting line, location remote, maybe mission.
Content: Position Summary paragraph(s). Also mention reporting to Sr. Director of AI + Digital Transformation, close relationship to Direct, AI Platform Operations. Location: US Remote. Also mention mission? Could include but not required. We'll keep it concise but preserve details.
Responsibilities
-> list of essential responsibilities (Process Discovery, Building, Sprint Delivery and Handoff, Troubleshooting, Reuse and Pattern Library, Value Measurement, Responsible Deployment, Cross-Functional Partnership). Use - .
Requirements
-> Required Qualifications bullet list. Also Physical & Practical Requirements maybe included here. Could combine.
We need to preserve all details: Bachelor's degree or equivalent experience, 3-5 years professional experience in process understanding and change, hands-on experience building AI agents, etc. Also comfort with APIs, etc. Also ability to teach while building, strong communication, comfort operating without playbook. Also Physical & Practical Requirements: ability to work at computer extended periods, occasional evening/weekend availability, travel up to 15%, ability to facilitate sessions.
We'll put those under Requirements.
Qualifications
-> Preferred Qualifications bullet list.
Skills
-> Knowledge, Skills & Abilities bullet list (Granular Curiosity, Bias Toward Building, Teaching Instinct, Judgment on Where to Stop, Plain Language). Could also include other skills like working fluency with Claude etc but those are in Requirements. We'll keep as given.
Benefits
-> benefits description.
Pay
-> salary range and bonus eligibility.
Schedule
-> Work Schedule: Full-Time (37.5 hours per week). Also maybe mention occasional evening/weekend availability but that's in Requirements. We'll keep schedule.
We must not include headings with filler like "not specified". All have content.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's craft.
We need to ensure we don't include duplicated lines. Remove boilerplate like EEO statements, application instructions, etc.
Check for any duplicated lines: The posting repeats some sentences? Not many.
Now produce HTML.
We'll need to escape any HTML special characters? Not needed.
Let's write:
About the role
The Forward Deployed AI Architect sits with a team, learns how their work actually happens, and then rebuilds that work with them using AI. Reporting to the Sr. Director of AI + Digital Transformation, with a close relationship to the Direct, AI Platform Operations, this role takes prioritized processes from across the Alzheimer’s Association and makes them agentic, in whole or in part. Each engagement is a sprint lasting weeks to a few months, focusing on one process at a time, sometimes spanning several business areas. The work begins by observing teammates in detail to understand where time is spent, where errors occur, and which parts are dreaded, then co‑designing solutions with the team. It ends with a running solution that returns hours, includes documentation the team can maintain, and a clean handoff to AI Platform Operations and IT, followed by a 30‑day stabilization window. The role is based remotely in the United States.
That captures summary.
Now Responsibilities:
Responsibilities
- Process Discovery: Embed with a team and learn their work in granular detail. Sit through the actual task. Map where the time goes, where errors creep in, and which parts of the job people dread. Bring the team into the redesign from the first day so they own what comes out of it.
- Building: Build working agents, automations, skills, and tools using approved AI platforms, primarily Claude. Ship something people can use inside the sprint. Work in real time alongside the staff who will use it, iterating on their actual deliverables rather than a sample.
- Sprint Delivery and Handoff: Run each engagement as a time‑boxed sprint with a defined start and end. Set the value target up front. Prove it at the close. Hand the solution to AI Platform Operations and IT with the documentation, test cases, and runbook they need to support it, then stay available through a 30‑day stabilization window before moving to the next process.
- Troubleshooting: Diagnose and fix what you built while a sprint is live and through stabilization. After that, partner with the standing IT support group on resolution rather than owning it. Feed every failure back into how the next thing gets built.
- Reuse and Pattern Library: Recognize when a solution built for one team fits four others. Turn one‑off builds into reusable skills, agents, and templates. Maintain a working library that the AI Collective and staff across the Association can pull from without asking permission.
- Value Measurement: Define a measurable target for every engagement before the work starts, whether that is hours returned, cycle time reduced, or capacity created. Track it through delivery and after. Report results to the Sr. Director and the AI Steering Committee, including the engagements that did not pay off.
- Responsible Deployment: Work inside the Association’s Responsible AI guidelines, data handling standards, and information security requirements. Know which processes should stay in human hands and say so early. Partner with Enterprise Risk and AI Platform Operations before any solution touches constituent, donor, research, or staff data.
- Cross‑Functional Partnership: Maintain a close working relationship with the Director of AI Platform Operations, who owns platform configuration, enterprise connectors, security review, and consumption. Coordinate early when a build needs new system access or new credentials. Serve as a dedicated member of the AI Collective.
Now Requirements:
Requirements
- Bachelor’s degree in a related field, or equivalent professional experience.
- 3–5 years of professional experience in work that required understanding how a process actually runs and then changing it. Consulting, operations, product, program delivery, or a dedicated AI transformation role all qualify.
- Hands‑on experience building AI agents, automations, or tools that real people adopted and continued using in their day‑to‑day work. Candidates should be prepared to walk through what they built, who used it, and what changed as a result.
- Working fluency with Claude or a comparable enterprise AI platform, including experience going beyond chat into agentic and multi‑step workflows. Candidates coming from applied AI, forward deployed, or solutions delivery backgrounds are encouraged to apply.
- Comfort working with APIs, connectors, and structured data well enough to wire a solution to the systems where work lives.
- A clear understanding of what separates a prototype from a production system, and the judgment to know which one a given situation calls for.
- Ability to teach while building, so that the people you build for can maintain and extend the work after you leave.
- Strong written and verbal communication with non‑technical staff, and the patience to work through a process with someone who is skeptical of AI.
- Comfort operating in a role with no established playbook, in an organization where trust is earned over time.
- Physical & Practical Requirements: Ability to work at a computer for extended periods; occasional evening or weekend availability during active sprints or at handoff; travel up to 15% to work on site with teams, including field and chapter operations; ability to facilitate working sessions with groups of varying sizes, both virtual and in person.
Now Qualifications (Preferred):
Qualifications
- Direct experience with Claude Code, Claude Cowork, MCP servers, or comparable agent development frameworks.
- Experience delivering AI or automation work inside a large, matrixed organization.
- Background in one or more of the areas the Association works in: scientific research, public policy and advocacy, healthcare, fundraising, or field and volunteer operations.
- Familiarity with Microsoft 365, Salesforce, Workday, or CXone as the systems a solution connects to.
- Prior nonprofit sector experience.
- Experience documenting and scaling a solution beyond the team it was built for.
Now Skills:
Skills
- Granular Curiosity: Wants to know what
Requirements
-> Required Qualifications bullet list. Also Physical & Practical Requirements maybe included here. Could combine. We need to preserve all details: Bachelor's degree or equivalent experience, 3-5 years professional experience in process understanding and change, hands-on experience building AI agents, etc. Also comfort with APIs, etc. Also ability to teach while building, strong communication, comfort operating without playbook. Also Physical & Practical Requirements: ability to work at computer extended periods, occasional evening/weekend availability, travel up to 15%, ability to facilitate sessions. We'll put those under Requirements.Qualifications
-> Preferred Qualifications bullet list.Skills
-> Knowledge, Skills & Abilities bullet list (Granular Curiosity, Bias Toward Building, Teaching Instinct, Judgment on Where to Stop, Plain Language). Could also include other skills like working fluency with Claude etc but those are in Requirements. We'll keep as given.Benefits
-> benefits description.Pay
-> salary range and bonus eligibility.Schedule
-> Work Schedule: Full-Time (37.5 hours per week). Also maybe mention occasional evening/weekend availability but that's in Requirements. We'll keep schedule. We must not include headings with filler like "not specified". All have content. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. We need to ensure we don't include duplicated lines. Remove boilerplate like EEO statements, application instructions, etc. Check for any duplicated lines: The posting repeats some sentences? Not many. Now produce HTML. We'll need to escape any HTML special characters? Not needed. Let's write:About the role
The Forward Deployed AI Architect sits with a team, learns how their work actually happens, and then rebuilds that work with them using AI. Reporting to the Sr. Director of AI + Digital Transformation, with a close relationship to the Direct, AI Platform Operations, this role takes prioritized processes from across the Alzheimer’s Association and makes them agentic, in whole or in part. Each engagement is a sprint lasting weeks to a few months, focusing on one process at a time, sometimes spanning several business areas. The work begins by observing teammates in detail to understand where time is spent, where errors occur, and which parts are dreaded, then co‑designing solutions with the team. It ends with a running solution that returns hours, includes documentation the team can maintain, and a clean handoff to AI Platform Operations and IT, followed by a 30‑day stabilization window. The role is based remotely in the United States.
That captures summary. Now Responsibilities:Responsibilities
- Process Discovery: Embed with a team and learn their work in granular detail. Sit through the actual task. Map where the time goes, where errors creep in, and which parts of the job people dread. Bring the team into the redesign from the first day so they own what comes out of it.
- Building: Build working agents, automations, skills, and tools using approved AI platforms, primarily Claude. Ship something people can use inside the sprint. Work in real time alongside the staff who will use it, iterating on their actual deliverables rather than a sample.
- Sprint Delivery and Handoff: Run each engagement as a time‑boxed sprint with a defined start and end. Set the value target up front. Prove it at the close. Hand the solution to AI Platform Operations and IT with the documentation, test cases, and runbook they need to support it, then stay available through a 30‑day stabilization window before moving to the next process.
- Troubleshooting: Diagnose and fix what you built while a sprint is live and through stabilization. After that, partner with the standing IT support group on resolution rather than owning it. Feed every failure back into how the next thing gets built.
- Reuse and Pattern Library: Recognize when a solution built for one team fits four others. Turn one‑off builds into reusable skills, agents, and templates. Maintain a working library that the AI Collective and staff across the Association can pull from without asking permission.
- Value Measurement: Define a measurable target for every engagement before the work starts, whether that is hours returned, cycle time reduced, or capacity created. Track it through delivery and after. Report results to the Sr. Director and the AI Steering Committee, including the engagements that did not pay off.
- Responsible Deployment: Work inside the Association’s Responsible AI guidelines, data handling standards, and information security requirements. Know which processes should stay in human hands and say so early. Partner with Enterprise Risk and AI Platform Operations before any solution touches constituent, donor, research, or staff data.
- Cross‑Functional Partnership: Maintain a close working relationship with the Director of AI Platform Operations, who owns platform configuration, enterprise connectors, security review, and consumption. Coordinate early when a build needs new system access or new credentials. Serve as a dedicated member of the AI Collective.
Requirements
- Bachelor’s degree in a related field, or equivalent professional experience.
- 3–5 years of professional experience in work that required understanding how a process actually runs and then changing it. Consulting, operations, product, program delivery, or a dedicated AI transformation role all qualify.
- Hands‑on experience building AI agents, automations, or tools that real people adopted and continued using in their day‑to‑day work. Candidates should be prepared to walk through what they built, who used it, and what changed as a result.
- Working fluency with Claude or a comparable enterprise AI platform, including experience going beyond chat into agentic and multi‑step workflows. Candidates coming from applied AI, forward deployed, or solutions delivery backgrounds are encouraged to apply.
- Comfort working with APIs, connectors, and structured data well enough to wire a solution to the systems where work lives.
- A clear understanding of what separates a prototype from a production system, and the judgment to know which one a given situation calls for.
- Ability to teach while building, so that the people you build for can maintain and extend the work after you leave.
- Strong written and verbal communication with non‑technical staff, and the patience to work through a process with someone who is skeptical of AI.
- Comfort operating in a role with no established playbook, in an organization where trust is earned over time.
- Physical & Practical Requirements: Ability to work at a computer for extended periods; occasional evening or weekend availability during active sprints or at handoff; travel up to 15% to work on site with teams, including field and chapter operations; ability to facilitate working sessions with groups of varying sizes, both virtual and in person.
Qualifications
- Direct experience with Claude Code, Claude Cowork, MCP servers, or comparable agent development frameworks.
- Experience delivering AI or automation work inside a large, matrixed organization.
- Background in one or more of the areas the Association works in: scientific research, public policy and advocacy, healthcare, fundraising, or field and volunteer operations.
- Familiarity with Microsoft 365, Salesforce, Workday, or CXone as the systems a solution connects to.
- Prior nonprofit sector experience.
- Experience documenting and scaling a solution beyond the team it was built for.
Skills
- Granular Curiosity: Wants to know what