Cloud Platforms and Agentic AI Architect
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include each bullet point as list items.
Let's parse the posting.
"The Opportunity: Drive the architecture, design, and delivery of scalable, multi‑cloud AI systems and API‑driven, event‑based applications. Lead teams in integrating structured and unstructured data to build Lakehouse architectures and support retrieval‑augmented AI pipelines. Establish API governance and multi‑cloud LLM routing using Azure APIM or AI Gateway. Oversee cloud infrastructure provisioning and full‑stack observability across Azure and AWS environments. Guide end‑to‑end ML lifecycle implementation, from ingestion through training, deployment, and traceability, and promote modern agentic delivery practices. Mentor teams, drive technical excellence, and support public‑health aligned mission needs with empathy and strong leadership instincts."
That's the opportunity paragraph. Could be About the role.
Then "You Have:" list:
- 10+ years of experience leading enterprise IT and software delivery programs, including cloud migration or modernization
- 8+ years of experience designing Azure or AWS cloud architectures
- 5+ years of experience building API‑first, microservices‑based, and event‑driven applications such as Azure Service Bus and Event Grid
- 3+ years of experience implementing AI, ML, or knowledge‑based systems, including agentic workflows, RAG pipelines, ontology‑driven architecture, and vector search
- Experience in Azure AI Search and PostgreSQL PgVector, including conceptualizing vector index strategies for varied use cases
- Experience with Azure APIM or AI Gateway to enable secure API exposure and multi‑cloud model routing, including Azure OpenAI, Bedrock, and partner LLMs
- Experience designing and implementing full‑stack observability for applications, microservices, and AI agents using Azure Monitor, App Insights, and OTel for telemetry, tracing, and cost visibility
- Experience with cloud infrastructure provisioning and operations across Azure, including AKS, Container Apps, App Service, Functions, Logic Apps, and Storage, and AWS
- Experience with end‑to‑end ML lifecycle workflows, including ingestion, feature engineering, training, deployment, cataloging, drift tracking, and Azure Databricks, for Lakehouse integration and delta sharing
- Bachelor’s degree
Then "Nice If You Have:" list:
- Experience implementing ML workflows within enterprise or public‑health environments
- Experience leading technical delivery teams
- Knowledge of microservice API orchestration, caching strategies, and secure API exposure patterns
- Knowledge of multi‑cloud AI access models and architectural integration patterns
- Knowledge of responsible AI, data ethics, privacy, and security best practices
- Possession of strong communication skills
- Master's degree in CS, Management Information Systems, or IT
- Azure or AWS Certifications
Then "Compensation At Booz Allen..." paragraph about benefits, then salary range.
We need Benefits section: list of benefits: health, life, disability, financial, and retirement benefits, as well as paid leave, professional development, tuition assistance, work-life programs, and dependent care. Recognition awards program acknowledges employees for exceptional performance and superior demonstration of our values. Full-time and part-time employees working at least 20 hours a week on a regular basis are eligible to participate in Booz Allen’s benefit programs. Individuals that do not meet the threshold are only eligible for select offerings, not inclusive of health benefits. We encourage you to learn more about our total benefits by visiting the Resource page on our Careers site and reviewing Our Employee Benefits page.
We should keep that as prose or list? It's a paragraph; we can put in
. Could also list benefits as
- . The instruction: Use
- for any list of duties/requirements/benefits. So we should list benefits as list items.
Thus Benefits section:
Benefits
- health benefits
- life benefits
- disability benefits
- financial benefits
- retirement benefits
- paid leave
- professional development
- tuition assistance
- work-life programs
- dependent care
- recognition awards program (acknowledges employees for exceptional performance and superior demonstration of our values)
- Full-time and part-time employees working at least 20 hours a week on a regular basis are eligible to participate in Booz Allen’s benefit programs.
- Individuals that do not meet the threshold are only eligible for select offerings, not inclusive of health benefits.
But we need to preserve all substantive info; we could keep the eligibility statements as separate list items.
Pay section: Pay
The projected compensation range for this position is $142,900.00 to $266,000.00 (annualized USD). The estimate displayed represents the typical salary range for this position and is just one component of Booz Allen’s total compensation package for employees.
We might also include that posting will close within 90 days from the Posting Date. That's substantive? It's about timeline. Could be included maybe in About the role? But it's not a duty/requirement. It's more metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. The closing date is minor metadata; we could fold into a short
maybe under About the role or separate? Probably better to drop it as it's not essential? But we need to preserve ALL substantive information; is closing date substantive? It's about application timeline; maybe considered minor metadata. The instruction says fold minor metadata into a short
or drop it. So we could include a short
somewhere, maybe after About the role.
But we must not include application instructions. The closing date is not an instruction but could be considered minor metadata. We'll include a short
after About the role:
This posting will close within 90 days from the Posting Date.
Now we need to ensure we don't repeat job title as heading. We'll not.
Now we need to output only HTML fragment, no /, no markdown.
Let's structure:
About the role
Drive the architecture, design, and delivery of scalable, multi‑cloud AI systems and API‑driven, event‑based applications. Lead teams in integrating structured and unstructured data to build Lakehouse architectures and support retrieval‑augmented AI pipelines. Establish API governance and multi‑cloud LLM routing using Azure APIM or AI Gateway. Oversee cloud infrastructure provisioning and full‑stack observability across Azure and AWS environments. Guide end‑to‑end ML lifecycle implementation, from ingestion through training, deployment, and traceability, and promote modern agentic delivery practices. Mentor teams, drive technical excellence, and support public‑health aligned mission needs with empathy and strong leadership instincts.
This posting will close within 90 days from the Posting Date.
Then Responsibilities? The opportunity paragraph already covers responsibilities. Could we treat that as Responsibilities? But we already used About the role. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have About the role. We could also have Responsibilities separate if we have distinct content. But we might not need Responsibilities if we already covered in About the role. However we should not create thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine About the role and Responsibilities into one section? But we need to follow headings: we can choose to include only About the role and skip Responsibilities if content overlaps. But we need to preserve all substantive info; we already have the opportunity paragraph which includes responsibilities. So we can put that under About the role. That's fine.
Then Requirements: list of "You Have". Use - .
Then Qualifications: maybe Bachelor's degree is a qualification; but it's already in You Have list. Could treat Qualifications as education: Bachelor's degree. But we already have it in Requirements list. To avoid duplication, we could keep Bachelor's degree in Requirements list and not have separate Qualifications. Or we could move it to Qualifications. The instruction: include a section ONLY when the posting has real, specific content for it. We have Bachelor's degree as a qualification. So we could have Qualifications section with Bachelor's degree. But then we would duplicate if we also list it under Requirements. Better to keep it under Requirements as part of experience list? Actually the "You Have" list includes Bachelor’s degree at the end. It's a qualification. So we could treat Requirements as experience, and Qualifications as education. But we need to avoid duplication. We could split: Requirements: the experience items (10+ years etc). Qualifications: Bachelor’s degree. That seems reasonable and not duplicate.
Thus:
Requirements
- 10+ years of experience leading enterprise IT and software delivery programs, including cloud migration or modernization
- 8+ years of experience designing Azure or AWS cloud architectures
- 5+ years of experience building API‑first, microservices‑based, and event‑driven applications such as Azure Service Bus and Event Grid
- 3+ years of experience implementing AI, ML, or knowledge‑based systems, including agentic workflows, RAG pipelines, ontology‑driven architecture, and vector search
- Experience in Azure AI Search and PostgreSQL PgVector, including conceptualizing vector index strategies for varied use cases
- Experience with Azure APIM or AI Gateway to enable secure API exposure and multi‑cloud model routing, including Azure OpenAI, Bedrock, and partner LLMs
- Experience designing and implementing full‑stack observability for applications, microservices, and AI agents using Azure Monitor, App Insights, and OTel for telemetry, tracing, and cost visibility
- Experience with cloud infrastructure provisioning and operations across Azure, including AKS, Container Apps, App Service, Functions, Logic Apps, and Storage, and AWS
- Experience with end‑to‑end ML lifecycle workflows, including ingestion, feature engineering, training, deployment, cataloging, drift tracking, and Azure Databricks, for Lakehouse integration and delta sharing
Qualifications
- Bachelor’s degree
for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to include each bullet point as list items. Let's parse the posting. "The Opportunity: Drive the architecture, design, and delivery of scalable, multi‑cloud AI systems and API‑driven, event‑based applications. Lead teams in integrating structured and unstructured data to build Lakehouse architectures and support retrieval‑augmented AI pipelines. Establish API governance and multi‑cloud LLM routing using Azure APIM or AI Gateway. Oversee cloud infrastructure provisioning and full‑stack observability across Azure and AWS environments. Guide end‑to‑end ML lifecycle implementation, from ingestion through training, deployment, and traceability, and promote modern agentic delivery practices. Mentor teams, drive technical excellence, and support public‑health aligned mission needs with empathy and strong leadership instincts." That's the opportunity paragraph. Could be About the role. Then "You Have:" list: - 10+ years of experience leading enterprise IT and software delivery programs, including cloud migration or modernization - 8+ years of experience designing Azure or AWS cloud architectures - 5+ years of experience building API‑first, microservices‑based, and event‑driven applications such as Azure Service Bus and Event Grid - 3+ years of experience implementing AI, ML, or knowledge‑based systems, including agentic workflows, RAG pipelines, ontology‑driven architecture, and vector search - Experience in Azure AI Search and PostgreSQL PgVector, including conceptualizing vector index strategies for varied use cases - Experience with Azure APIM or AI Gateway to enable secure API exposure and multi‑cloud model routing, including Azure OpenAI, Bedrock, and partner LLMs - Experience designing and implementing full‑stack observability for applications, microservices, and AI agents using Azure Monitor, App Insights, and OTel for telemetry, tracing, and cost visibility - Experience with cloud infrastructure provisioning and operations across Azure, including AKS, Container Apps, App Service, Functions, Logic Apps, and Storage, and AWS - Experience with end‑to‑end ML lifecycle workflows, including ingestion, feature engineering, training, deployment, cataloging, drift tracking, and Azure Databricks, for Lakehouse integration and delta sharing - Bachelor’s degree Then "Nice If You Have:" list: - Experience implementing ML workflows within enterprise or public‑health environments - Experience leading technical delivery teams - Knowledge of microservice API orchestration, caching strategies, and secure API exposure patterns - Knowledge of multi‑cloud AI access models and architectural integration patterns - Knowledge of responsible AI, data ethics, privacy, and security best practices - Possession of strong communication skills - Master's degree in CS, Management Information Systems, or IT - Azure or AWS Certifications Then "Compensation At Booz Allen..." paragraph about benefits, then salary range. We need Benefits section: list of benefits: health, life, disability, financial, and retirement benefits, as well as paid leave, professional development, tuition assistance, work-life programs, and dependent care. Recognition awards program acknowledges employees for exceptional performance and superior demonstration of our values. Full-time and part-time employees working at least 20 hours a week on a regular basis are eligible to participate in Booz Allen’s benefit programs. Individuals that do not meet the threshold are only eligible for select offerings, not inclusive of health benefits. We encourage you to learn more about our total benefits by visiting the Resource page on our Careers site and reviewing Our Employee Benefits page. We should keep that as prose or list? It's a paragraph; we can put in
. Could also list benefits as
- . The instruction: Use
- for any list of duties/requirements/benefits. So we should list benefits as list items.
Thus Benefits section:
Benefits
- health benefits
- life benefits
- disability benefits
- financial benefits
- retirement benefits
- paid leave
- professional development
- tuition assistance
- work-life programs
- dependent care
- recognition awards program (acknowledges employees for exceptional performance and superior demonstration of our values)
- Full-time and part-time employees working at least 20 hours a week on a regular basis are eligible to participate in Booz Allen’s benefit programs.
- Individuals that do not meet the threshold are only eligible for select offerings, not inclusive of health benefits.
Pay
The projected compensation range for this position is $142,900.00 to $266,000.00 (annualized USD). The estimate displayed represents the typical salary range for this position and is just one component of Booz Allen’s total compensation package for employees.
We might also include that posting will close within 90 days from the Posting Date. That's substantive? It's about timeline. Could be included maybe in About the role? But it's not a duty/requirement. It's more metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. The closing date is minor metadata; we could fold into a short
maybe under About the role or separate? Probably better to drop it as it's not essential? But we need to preserve ALL substantive information; is closing date substantive? It's about application timeline; maybe considered minor metadata. The instruction says fold minor metadata into a short
or drop it. So we could include a short
somewhere, maybe after About the role. But we must not include application instructions. The closing date is not an instruction but could be considered minor metadata. We'll include a short
after About the role:
This posting will close within 90 days from the Posting Date.
Now we need to ensure we don't repeat job title as heading. We'll not. Now we need to output only HTML fragment, no /, no markdown. Let's structure:About the role
Drive the architecture, design, and delivery of scalable, multi‑cloud AI systems and API‑driven, event‑based applications. Lead teams in integrating structured and unstructured data to build Lakehouse architectures and support retrieval‑augmented AI pipelines. Establish API governance and multi‑cloud LLM routing using Azure APIM or AI Gateway. Oversee cloud infrastructure provisioning and full‑stack observability across Azure and AWS environments. Guide end‑to‑end ML lifecycle implementation, from ingestion through training, deployment, and traceability, and promote modern agentic delivery practices. Mentor teams, drive technical excellence, and support public‑health aligned mission needs with empathy and strong leadership instincts.
This posting will close within 90 days from the Posting Date.
Then Responsibilities? The opportunity paragraph already covers responsibilities. Could we treat that as Responsibilities? But we already used About the role. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have About the role. We could also have Responsibilities separate if we have distinct content. But we might not need Responsibilities if we already covered in About the role. However we should not create thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine About the role and Responsibilities into one section? But we need to follow headings: we can choose to include only About the role and skip Responsibilities if content overlaps. But we need to preserve all substantive info; we already have the opportunity paragraph which includes responsibilities. So we can put that under About the role. That's fine. Then Requirements: list of "You Have". Use- .
Then Qualifications: maybe Bachelor's degree is a qualification; but it's already in You Have list. Could treat Qualifications as education: Bachelor's degree. But we already have it in Requirements list. To avoid duplication, we could keep Bachelor's degree in Requirements list and not have separate Qualifications. Or we could move it to Qualifications. The instruction: include a section ONLY when the posting has real, specific content for it. We have Bachelor's degree as a qualification. So we could have Qualifications section with Bachelor's degree. But then we would duplicate if we also list it under Requirements. Better to keep it under Requirements as part of experience list? Actually the "You Have" list includes Bachelor’s degree at the end. It's a qualification. So we could treat Requirements as experience, and Qualifications as education. But we need to avoid duplication. We could split: Requirements: the experience items (10+ years etc). Qualifications: Bachelor’s degree. That seems reasonable and not duplicate.
Thus:
Requirements
- 10+ years of experience leading enterprise IT and software delivery programs, including cloud migration or modernization
- 8+ years of experience designing Azure or AWS cloud architectures
- 5+ years of experience building API‑first, microservices‑based, and event‑driven applications such as Azure Service Bus and Event Grid
- 3+ years of experience implementing AI, ML, or knowledge‑based systems, including agentic workflows, RAG pipelines, ontology‑driven architecture, and vector search
- Experience in Azure AI Search and PostgreSQL PgVector, including conceptualizing vector index strategies for varied use cases
- Experience with Azure APIM or AI Gateway to enable secure API exposure and multi‑cloud model routing, including Azure OpenAI, Bedrock, and partner LLMs
- Experience designing and implementing full‑stack observability for applications, microservices, and AI agents using Azure Monitor, App Insights, and OTel for telemetry, tracing, and cost visibility
- Experience with cloud infrastructure provisioning and operations across Azure, including AKS, Container Apps, App Service, Functions, Logic Apps, and Storage, and AWS
- Experience with end‑to‑end ML lifecycle workflows, including ingestion, feature engineering, training, deployment, cataloging, drift tracking, and Azure Databricks, for Lakehouse integration and delta sharing
Qualifications
- Bachelor’s degree
- for any list of duties/requirements/benefits. So we should list benefits as list items.
Thus Benefits section: