Forward Deployed Architect
Gallagher Bassett · Rolling Meadows, IL · 3 wk ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections only if real content. Need to extract sections: About the role? The posting has Introduction, Overview, How You'll Make An Impact, Responsibilities, Strong Business Acumen Required About You (maybe "About You"), Preferred: What Sets You Apart, Work Traits, Compensation And Benefits.
We need headings: Use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content to these headings. The posting includes responsibilities, requirements (experience, skills), qualifications (education), maybe skills list, benefits, compensation. No explicit Pay or Schedule details, so we should not create those sections unless present. There's "Compensation And Benefits" but only generic statements, no specific compensation numbers or benefits details besides generic. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says "Compensation And Benefits" but only generic statements like "Competitive compensation", "Comprehensive benefits programs". That's still stating benefits exist but not specifics. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but not specifics. However we need to decide if we should include a Benefits section with the generic statements? The instruction: "Prefer a few substantive sections over many thin ones." Also "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The benefits section would contain generic statements like "Competitive compensation", "Comprehensive benefits programs designed to support your well-being", etc. That's not placeholder but still vague. Might be considered substantive enough? It's not specific like health insurance, 401k, etc. Might be considered filler. Safer to omit Benefits section because no specific details. Similarly no Pay or Schedule.
Thus we will have sections: About the role? Could use Overview as About the role. How You'll Make An Impact could be part of About the role or separate? Could be "About the role". But we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content.
We have Overview (intro to role) -> could be About the role.
We have How You'll Make An Impact -> could be part of About the role or maybe separate but we can merge.
We have Responsibilities (clear list) -> Responsibilities section.
We have Strong Business Acumen Required About You -> that's requirements/qualifications. Could split into Requirements (experience) and Qualifications (education) and Skills (technologies). We'll need to decide.
We have Preferred: What Sets You Apart -> could be additional qualifications/skills.
We have Work Traits -> could be Skills? Or maybe part of Requirements.
We'll produce sections: About the role (combining Overview and How You'll Make An Impact), Responsibilities, Requirements (experience + work traits?), Qualifications (education + preferred), Skills (technical skills list). Benefits omitted.
We must not repeat job title as heading. No Job ID.
We need to use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content to these headings. The posting includes responsibilities, requirements (experience, skills), qualifications (education), maybe skills list, benefits, compensation. No explicit Pay or Schedule details, so we should not create those sections unless present. There's "Compensation And Benefits" but only generic statements, no specific compensation numbers or benefits details besides generic. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says "Compensation And Benefits" but only generic statements like "Competitive compensation", "Comprehensive benefits programs". That's still stating benefits exist but not specifics. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but not specifics. However we need to decide if we should include a Benefits section with the generic statements? The instruction: "Prefer a few substantive sections over many thin ones." Also "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The benefits section would contain generic statements like "Competitive compensation", "Comprehensive benefits programs designed to support your well-being", etc. That's not placeholder but still vague. Might be considered substantive enough? It's not specific like health insurance, 401k, etc. Might be considered filler. Safer to omit Benefits section because no specific details. Similarly no Pay or Schedule.
Thus we will have sections: About the role? Could use Overview as About the role. How You'll Make An Impact could be part of About the role or separate? Could be "About the role". But we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content.
We have Overview (intro to role) -> could be About the role.
We have How You'll Make An Impact -> could be part of About the role or maybe separate but we can merge.
We have Responsibilities (clear list) -> Responsibilities section.
We have Strong Business Acumen Required About You -> that's requirements/qualifications. Could split into Requirements (experience) and Qualifications (education) and Skills (technologies). We'll need to decide.
We have Preferred: What Sets You Apart -> could be additional qualifications/skills.
We have Work Traits -> could be Skills? Or maybe part of Requirements.
We'll produce sections: About the role (combining Overview and How You'll Make An Impact), Responsibilities, Requirements (experience + work traits?), Qualifications (education + preferred), Skills (technical skills list). Benefits omitted.
We must not repeat job title as heading. No Job ID.
We need to use - for any list of duties/requirements/benefits. So for responsibilities list, we need
- . For requirements list (like experience, skills) also list.
We need to preserve all substantive information, not invent or summarize away detail. Must keep details.
We'll need to parse the text and produce HTML.
Let's extract content.
Introduction paragraph: "At Gallagher Bassett, we're there when it matters most because helping people through challenging moments is more than just our job, it’s our purpose. Every day, we help clients navigate complexity, support recovery, and deliver outcomes that make a real difference in people’s lives. It takes empathy, precision, and a strong sense of partnership—and that’s exactly what you’ll find here. We’re a team of fast-paced fixers, empathetic experts, and outcomes drivers — people who care deeply about doing the right thing and doing it well. Whether you're managing claims, supporting clients, or improving processes, you’ll play a vital role in helping businesses and individuals move forward with confidence. Here, you’ll be supported by a culture that values teamwork, encourages curiosity, and celebrates the impact of your work. Because when you’re here, you’re part of something bigger. You’re part of a team that shows up, stands together, and leads with purpose."
Overview: "We are seeking a Forward Deployed Architect/Engineer a hands-on, high-impact technologist who sits at the intersection of breaking down complex business problems and building real, working solutions using the latest advances in AI-assisted software delivery. This is not a traditional architecture role. You will be embedded directly with business stakeholders, product teams, and claims operations leaders across geographies to rapidly translate unstructured challenges into prototyped, validated, and production-ready solutions that align globally."
How You'll Make An Impact: paragraph describing role.
Responsibilities list: bullet points each starting with bold? We'll need to capture each responsibility sentence.
Let's list responsibilities as given:
- Decompose Complex Business Problems: Embed directly with business leaders, claims operations, product owners, and subject-matter experts to deeply understand unstructured problems, then break them into solvable, architecturally sound components with clear technical paths forward.
- Prototype at Velocity Using AI-Assisted SDLC: Leverage AI-native development tools agentic coding workflows, and rapid iteration cycles to build working prototypes, not slide decks, that validate hypotheses and demonstrate value within days, not quarters.
- Architect Solutions That Scale Globally: Design prototyped solutions with an enterprise lens, ensuring that what works in a US claims workflow can be adapted and extended across UK, Australian, and other international operations without rearchitecting from scratch. Apply modular, cloud-native, and API-first design patterns that respect regional compliance and data residency requirements.
- Bridge AI Innovation and Business Adoption: Serve as the technical translator between cutting-edge AI capabilities (LLMs, RAG, vector search, multi-agent systems, computer vision) and practical claims, risk management, and operational workflows. Ensure AI isn't just technically interesting, but operationally valuable and adopted by the people doing the work.
- Own End-to-End Delivery of Proof-of-Value Initiatives: Drive solutions from ideation through discovery, data wrangling, integration, deployment, and feedback, operating with startup-like autonomy backed by enterprise resources. Be accountable for measurable outcomes, not just deliverables.
- Accelerate the Architecture Team's AI Fluency: Model and evangelize AI-assisted development practices across the broader architecture and engineering organization. Contribute reusable patterns, reference architectures, and working examples that elevate the team's collective capability.
- Engage Executive Stakeholders with Clarity: Communicate technical decisions, trade-offs, and progress to both technical teams and executive leadership (CIO, CDO, line-of-business leaders), adapting your message to the audience without losing precision.
- Contribute to Architectural Governance: Participate in the Architecture Review Board (ARB), contribute solution architecture artifacts, and ensure prototyped solutions align with enterprise standards, security posture, and the strategic technology roadmap.
Strong Business Acumen Required About You: This paragraph includes requirements:
"8+ years of progressive experience in software architecture, solution architecture, or platform engineering, with a demonstrated ability to both design and build.
Hands-on fluency with at least two of the following: C#/.NET, Python, TypeScript/JavaScript. This means more than familiarity; it means the ability to produce production-quality code under ambiguity.
Deep cloud architecture expertise on Microsoft Azure (App Services, Container Apps, Azure AI Services, Azure SQL, Cosmos DB, Service Bus, APIM) or equivalent hyperscaler.
Demonstrated experience with AI-assisted software development, including active use of tools like GitHub Copilot, Cursor, Claude Code, Windsurf, or similar AI-native IDEs to accelerate delivery.
Strong working knowledge of AI/ML application patterns: Retrieval-Augmented Generation (RAG), vector databases (Azure AI Search, Pinecone), LLM integration (OpenAI, Azure OpenAI, Anthropic), prompt engineering, and multi-agent orchestration frameworks (Semantic Kernel, LangChain, AutoGen).
Proven ability to decompose ambiguous business problems into structured technical approaches without waiting for a 40-page BRD.
Exceptional communication skills, with comfort leading a whiteboard session with a claims supervisor in the morning and presenting a solution architecture to the CIO in the afternoon.
Experience working across geographies, including comfort with distributed teams, time zone management, and cultural sensitivity in solution design.
Bachelor's degree in Computer Science, Software Engineering, or a related field (or equivalent experience)."
Preferred: What Sets You Apart:
"Experience in insurance, claims administration, TPA, or risk management, with an understanding of the claims lifecycle, regulatory landscape, and operational workflows considered a significant advantage.
Prior experience in a Forward Deployed Engineer, field engineer, or customer-embedded technical role, even if it was not formally titled "Forward Deployed."
Familiarity with AI-enabled SDLC acceleration patterns: intent-driven delivery, MCP-based architectures, context engineering for structured AI reasoning, and autonomous coding agent workflows.
Track record of shipping prototypes that became products, with examples of work that started as a POC and became a production solution serving real users.
Experience with DevSecOps pipelines, infrastructure-as-code (Bicep/Terraform), and containerized workloads (Docker, Kubernetes, Azure Container Apps).
Architectural governance experience, including comfort with TOGAF, C4 model, or equivalent frameworks for documenting and communicating architecture decisions.
Graduate degree, TOGAF certification, or Azure Solutions Architect Expert certification is a plus."
Work Traits:
"Builder mentality, with a default preference for "let me show you" over "let me tell you." You prototype to think.
High-ambiguity tolerance, with the ability to thrive when requirements are vague, the data is messy, and the timeline is aggressive. You find clarity by building, not by waiting.
First-principles thinker, with the curiosity to question assumptions, challenge inherited complexity, and ask "why is it done this way?" before accepting the status quo.
Empathetic operator, with genuine care for the people who will use what you build. You sit with Resolution Managers, understand their pain, and design solutions that respect their expertise.
Global mindset, with natural consideration for how a solution designed in Rolling Meadows will work in London, Sydney, or Mumbai.
Intellectual curiosity, with a habit of independently researching the latest in AI tooling, SDLC patterns, and platform engineering because the work is genuinely interesting."
Compensation And Benefits:
"At Gallagher, we believe supporting our colleagues goes far beyond the role itself. For more information, visit our Benefits page.
Competitive compensation
Comprehensive benefits programs designed to support your well-being
Career development opportunities and ongoing learning
A collaborative, people-first culture with accessible leadership
The opportunity to do meaningful work with global reach and local impact
At Gallagher, we are dedicated to building an inclusive and authentic workplace. If your past experience doesn’t align perfectly, we encourage you to join our Talent Community to stay connected to additional career opportunities. At times, we will consider transferable skills from previous roles.
Gallagher is an affirmative action/equal opportunity employer (Minorities/Females/Veterans/Disabled)"
We need to remove boilerplate like EEO etc. So we should drop the last line about affirmative action etc. Also remove "For more information, visit our Benefits page." maybe considered boilerplate? It's a reference to benefits page but not specific benefit. Might be considered boilerplate. We'll remove it.
We also need to remove duplicated lines.
Now craft HTML.
We'll have:
About the role
Introduction paragraph + Overview + How You'll Make An Impact combined into prose.
But we must not repeat job title as heading. Already not.
We'll combine the three paragraphs into one maybe multiple
allowed? The rule: use
for prose. Could have multiple
elements.
- . For requirements list (like experience, skills) also list.
We need to preserve all substantive information, not invent or summarize away detail. Must keep details.
We'll need to parse the text and produce HTML.
Let's extract content.
Introduction paragraph: "At Gallagher Bassett, we're there when it matters most because helping people through challenging moments is more than just our job, it’s our purpose. Every day, we help clients navigate complexity, support recovery, and deliver outcomes that make a real difference in people’s lives. It takes empathy, precision, and a strong sense of partnership—and that’s exactly what you’ll find here. We’re a team of fast-paced fixers, empathetic experts, and outcomes drivers — people who care deeply about doing the right thing and doing it well. Whether you're managing claims, supporting clients, or improving processes, you’ll play a vital role in helping businesses and individuals move forward with confidence. Here, you’ll be supported by a culture that values teamwork, encourages curiosity, and celebrates the impact of your work. Because when you’re here, you’re part of something bigger. You’re part of a team that shows up, stands together, and leads with purpose."
Overview: "We are seeking a Forward Deployed Architect/Engineer a hands-on, high-impact technologist who sits at the intersection of breaking down complex business problems and building real, working solutions using the latest advances in AI-assisted software delivery. This is not a traditional architecture role. You will be embedded directly with business stakeholders, product teams, and claims operations leaders across geographies to rapidly translate unstructured challenges into prototyped, validated, and production-ready solutions that align globally."
How You'll Make An Impact: paragraph describing role.
Responsibilities list: bullet points each starting with bold? We'll need to capture each responsibility sentence.
Let's list responsibilities as given:
- Decompose Complex Business Problems: Embed directly with business leaders, claims operations, product owners, and subject-matter experts to deeply understand unstructured problems, then break them into solvable, architecturally sound components with clear technical paths forward.
- Prototype at Velocity Using AI-Assisted SDLC: Leverage AI-native development tools agentic coding workflows, and rapid iteration cycles to build working prototypes, not slide decks, that validate hypotheses and demonstrate value within days, not quarters.
- Architect Solutions That Scale Globally: Design prototyped solutions with an enterprise lens, ensuring that what works in a US claims workflow can be adapted and extended across UK, Australian, and other international operations without rearchitecting from scratch. Apply modular, cloud-native, and API-first design patterns that respect regional compliance and data residency requirements.
- Bridge AI Innovation and Business Adoption: Serve as the technical translator between cutting-edge AI capabilities (LLMs, RAG, vector search, multi-agent systems, computer vision) and practical claims, risk management, and operational workflows. Ensure AI isn't just technically interesting, but operationally valuable and adopted by the people doing the work.
- Own End-to-End Delivery of Proof-of-Value Initiatives: Drive solutions from ideation through discovery, data wrangling, integration, deployment, and feedback, operating with startup-like autonomy backed by enterprise resources. Be accountable for measurable outcomes, not just deliverables.
- Accelerate the Architecture Team's AI Fluency: Model and evangelize AI-assisted development practices across the broader architecture and engineering organization. Contribute reusable patterns, reference architectures, and working examples that elevate the team's collective capability.
- Engage Executive Stakeholders with Clarity: Communicate technical decisions, trade-offs, and progress to both technical teams and executive leadership (CIO, CDO, line-of-business leaders), adapting your message to the audience without losing precision.
- Contribute to Architectural Governance: Participate in the Architecture Review Board (ARB), contribute solution architecture artifacts, and ensure prototyped solutions align with enterprise standards, security posture, and the strategic technology roadmap.
Strong Business Acumen Required About You: This paragraph includes requirements:
"8+ years of progressive experience in software architecture, solution architecture, or platform engineering, with a demonstrated ability to both design and build.
Hands-on fluency with at least two of the following: C#/.NET, Python, TypeScript/JavaScript. This means more than familiarity; it means the ability to produce production-quality code under ambiguity.
Deep cloud architecture expertise on Microsoft Azure (App Services, Container Apps, Azure AI Services, Azure SQL, Cosmos DB, Service Bus, APIM) or equivalent hyperscaler.
Demonstrated experience with AI-assisted software development, including active use of tools like GitHub Copilot, Cursor, Claude Code, Windsurf, or similar AI-native IDEs to accelerate delivery.
Strong working knowledge of AI/ML application patterns: Retrieval-Augmented Generation (RAG), vector databases (Azure AI Search, Pinecone), LLM integration (OpenAI, Azure OpenAI, Anthropic), prompt engineering, and multi-agent orchestration frameworks (Semantic Kernel, LangChain, AutoGen).
Proven ability to decompose ambiguous business problems into structured technical approaches without waiting for a 40-page BRD.
Exceptional communication skills, with comfort leading a whiteboard session with a claims supervisor in the morning and presenting a solution architecture to the CIO in the afternoon.
Experience working across geographies, including comfort with distributed teams, time zone management, and cultural sensitivity in solution design.
Bachelor's degree in Computer Science, Software Engineering, or a related field (or equivalent experience)."
Preferred: What Sets You Apart:
"Experience in insurance, claims administration, TPA, or risk management, with an understanding of the claims lifecycle, regulatory landscape, and operational workflows considered a significant advantage.
Prior experience in a Forward Deployed Engineer, field engineer, or customer-embedded technical role, even if it was not formally titled "Forward Deployed."
Familiarity with AI-enabled SDLC acceleration patterns: intent-driven delivery, MCP-based architectures, context engineering for structured AI reasoning, and autonomous coding agent workflows.
Track record of shipping prototypes that became products, with examples of work that started as a POC and became a production solution serving real users.
Experience with DevSecOps pipelines, infrastructure-as-code (Bicep/Terraform), and containerized workloads (Docker, Kubernetes, Azure Container Apps).
Architectural governance experience, including comfort with TOGAF, C4 model, or equivalent frameworks for documenting and communicating architecture decisions.
Graduate degree, TOGAF certification, or Azure Solutions Architect Expert certification is a plus."
Work Traits:
"Builder mentality, with a default preference for "let me show you" over "let me tell you." You prototype to think.
High-ambiguity tolerance, with the ability to thrive when requirements are vague, the data is messy, and the timeline is aggressive. You find clarity by building, not by waiting.
First-principles thinker, with the curiosity to question assumptions, challenge inherited complexity, and ask "why is it done this way?" before accepting the status quo.
Empathetic operator, with genuine care for the people who will use what you build. You sit with Resolution Managers, understand their pain, and design solutions that respect their expertise.
Global mindset, with natural consideration for how a solution designed in Rolling Meadows will work in London, Sydney, or Mumbai.
Intellectual curiosity, with a habit of independently researching the latest in AI tooling, SDLC patterns, and platform engineering because the work is genuinely interesting."
Compensation And Benefits:
"At Gallagher, we believe supporting our colleagues goes far beyond the role itself. For more information, visit our Benefits page.
Competitive compensation
Comprehensive benefits programs designed to support your well-being
Career development opportunities and ongoing learning
A collaborative, people-first culture with accessible leadership
The opportunity to do meaningful work with global reach and local impact
At Gallagher, we are dedicated to building an inclusive and authentic workplace. If your past experience doesn’t align perfectly, we encourage you to join our Talent Community to stay connected to additional career opportunities. At times, we will consider transferable skills from previous roles.
Gallagher is an affirmative action/equal opportunity employer (Minorities/Females/Veterans/Disabled)"
We need to remove boilerplate like EEO etc. So we should drop the last line about affirmative action etc. Also remove "For more information, visit our Benefits page." maybe considered boilerplate? It's a reference to benefits page but not specific benefit. Might be considered boilerplate. We'll remove it.
We also need to remove duplicated lines.
Now craft HTML.
We'll have:
About the role
Introduction paragraph + Overview + How You'll Make An Impact combined into prose.
But we must not repeat job title as heading. Already not. We'll combine the three paragraphs into onemaybe multiple
allowed? The rule: use
for prose. Could have multiple
elements.