Forward Deployed AI Architect

We need to output HTML fragment with sections: headings using

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 (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Must not create sections with filler like "commensurate with experience". Must include Pay and Schedule only if posting actually states them. The posting includes: "Location: US Remote Work Schedule: Full-Time (37.5 hours per week)" and "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%". So we have Pay and Schedule info. Also Benefits: there is a paragraph about benefits: "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." So we have benefits content. Also there is a lot of EEO etc which we must remove. Also there is mission statement etc which may be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Mission statement maybe not boilerplate? It's substantive about organization but could be considered fluff. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The mission statement is substantive about the organization but not directly about the role. Might be considered okay to keep? However they said remove EEO/equal-opportunity/scam-warning boilerplate. Mission statement is not that. It's okay to keep but we need to decide if we include as a section. There's no specific heading for "About the Association" but we could put under "About the role" maybe includes position summary. The position summary is given at start: "Position Summary The Forward Deployed AI Architect sits with a team, learns how their work actually happens, and then rebuilds that work with them using AI....". That's substantive. We'll put that under

About the role

maybe. Or we could have separate sections: About the role (position summary), Responsibilities (Essential Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Skills (Knowledge, Skills & Abilities), Benefits, Pay, Schedule. Also Physical & Practical Requirements maybe could be under Requirements or separate? But we can incorporate into Requirements or Skills. The instruction: prefer a few substantive sections over many thin ones. So we could combine Physical & Practical Requirements into Requirements or Skills. But we have separate sections for Requirements and Qualifications already. Could put Physical under Requirements. Also Location: US Remote maybe under Schedule? Actually location is separate but not a heading we have. Could include in About the role or maybe as a note in Schedule? But we have Schedule heading for work schedule. Location could be included in About the role or maybe as a separate short paragraph not under a heading. Since we must not create headings without real content, we could just include location in a

after About the role. We must not include duplicated lines. Need to extract responsibilities list: they are bullet-like sentences separated by periods. We'll make

• for each duty. Responsibilities list: - 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. We'll put those as
  • . Required Qualifications: list: - 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 Preferred Qualifications: list: - 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 Knowledge, Skills & Abilities: list: - Granular Curiosity: Wants to know what someone clicks on at 9:15 on a Tuesday. Learns an unfamiliar business area fast and earns credibility with the people doing the work - Bias Toward Building: Would rather show a working prototype on someone’s real deliverable this week than present a polished plan for next quarter - Teaching Instinct: Builds with people rather than for them, and measures success partly by how little the team needs you afterward - Judgment on Where to Stop: Recognizes when a process should stay human, when a prototype is good enough, and when a build needs to go to IT before it goes any further - Plain Language: Explains technical decisions to a program director, a fundraiser, and a C-suite leader without changing the substance Physical & Practical Requirements: list: - 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 Location: US Remote (we can include as a paragraph). Work Schedule: Full-Time (37.5 hours per week) Pay: Grade 512; salary range $155,000-$168,000; bonus up to 6% based on individual and organizational performance. Benefits: comprehensive benefits package details. We must not include boilerplate like mission statement, EEO, etc. Also must not include duplicated lines. Also must not include application instructions like "Please click HERE for more information." That's maybe part of benefits but it's an instruction; we should remove application instructions. The sentence "Please click HERE for more information." is an application instruction; we should remove it. Also "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." That's part of benefits; we keep that. Also we must remove lines about Qualified Applicants with arrest or Conviction records etc. That's EEO/legal; remove. Also remove mission statement paragraphs about Alzheimer's Association etc. That's not EEO but could be considered boilerplate? It's organizational description; maybe we keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Mission statement is not those; but it's not directly about the role. However it's substantive info about the organization. I'd keep it maybe under a short "About the Association" but we don't have a heading for that. Could include in About the role section after position summary. But to keep sections few, we could incorporate into About the role. But the instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role (includes position summary and maybe brief org description), Responsibilities, Requirements (includes Required Qualifications, Preferred Qualifications, Knowledge, Skills & Abilities, Physical & Practical Requirements), Benefits, Pay, Schedule. That's many sections though. Could combine Requirements and Qualifications into one "Requirements" section that includes both required and preferred? But they asked to use headings like Requirements, Qualifications, Skills. So we should follow that: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to output those headings only if we have content. We'll include all eight sections because we have content for each. Thus:

    About the role

    Position Summary ... plus maybe brief org description? We'll keep just the position summary (the paragraph). Could also add location US Remote as a separate

    after.

    Responsibilities