Associate AI Solution Architect
About the role
thenwith that content (maybe trimmed). Should we include recruiting end date? It's metadata; we can fold into short
or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include recruiting end date in a short
maybe. Next: "Work you'll do: Architect and Design: assist in the design and development of enterprise-grade application architecture applications and platforms, with a focus on scaling for production. This includes defining the technical architecture, selecting appropriate technologies, and ensuring solutions are robust, scalable, and secure. Assist in the design and deployment of applications using Cloud Native principles on a hyperscaler platform (AWS, Azure, GCP). Leverage a wide range of hyperscaler tools and services, including containers (Docker, Kubernetes), serverless functions, and managed databases. Should have experience in leveraging various GenAI tools to accelerate software development life cycle. Assist in the management and delivery components of client engagements that identify, design, and implement technology and creative business solutions for large companies. Responsibilities include, among others, managing small teams in the identification of business requirements, functional design, process design (including scenario design, flow mapping), prototyping, testing, training, defining support procedures. Assisting clients with application architecture design, assessment and optimization including definition, documentation and implementation of new application architectures Review and evaluation of key attributes of existing application architectures Assist in the recommendation of improvements to existing Application Architectures" That's responsibilities. We'll put
Responsibilities
then- items. We need to extract bullet points. Could break into separate li for each distinct duty. List items: - Assist in the design and development of enterprise-grade application architecture applications and platforms, focusing on scaling for production (defining technical architecture, selecting technologies, ensuring robustness, scalability, security). - Assist in the design and deployment of applications using Cloud Native principles on hyperscaler platforms (AWS, Azure, GCP), leveraging containers (Docker, Kubernetes), serverless functions, managed databases. - Should have experience leveraging various GenAI tools to accelerate software development life cycle. - Assist in the management and delivery components of client engagements that identify, design, and implement technology and creative business solutions for large companies, including managing small teams in identification of business requirements, functional design, process design (scenario design, flow mapping), prototyping, testing, training, defining support procedures. - Assist clients with application architecture design, assessment and optimization: definition, documentation, implementation of new application architectures. - Review and evaluation of key attributes of existing application architectures. - Assist in the recommendation of improvements to existing Application Architectures. We'll put each as
- .
Next: "Required Qualifications Bachelor's degree in computer science or engineering, or a related technical field with a strong foundation in development (Java or .NET) with early experience as a full stack developer. 4+ years' experience as a Solution Architect, with a strong focus on application development and scaling solutions for production environments. 4+ years providing hands-on technical assistance to the delivery team, reviewing designs and code for architectural fit, monitoring engineers and serving as the primary technical liaison between business stakeholders and engineering. 4+ years working on large-scale engagements as a Solution Architect in industry or in consulting. Hands-on experience in Java, Python, or .NET. Experience managing small on and offshore teams. 1+ years' experience designing and delivering production-grade AI solutions such as LLM applications, RAG systems, agentic workflows, intelligent automation or ML-enabled products. Hands-on software engineering capability in Python and/or a modern full-stack capability. Experience owning the end-to-end solution architecture which includes defining integration patterns, data flows, and technical design decisions across systems. Experience driving the technical delivery on-site (not remotely), translating business requirements into detailed technical designs, sequencing work across integration and data layers, ensuring the solution is built to spec from design to deployment. Deep understanding of AI/ML concepts, including experience with LLMs and their application in enterprise settings. Familiarity with various hyperscaler tools and services. Hyperscaler Architect certification is required (e.g., AWS Certified Solutions Architect, Azure Solutions Architect Expert, or GCP Professional Cloud Architect). Experience working closely with the functional and testing teams to understand their requirements gauging the impact to the application architecture. Experience leading the configuration and change management teams responsible for application deployments including the coordination of database changes and other necessary application configurations. 3+ years implementing CI/CD and DevSecOps with Cloud Build, GitHub Actions or Jenkins. 1+ years' experience working as an AI Architect on the job with experience using AWS Ability to travel up to 50% nationally based on the work you do and the clients and industries/sectors you serve. Must be legally authorized to work in the United States without the need for sponsorship, now or any time in the future."
That's a long list of required qualifications. We'll put under
Requirements
maybe. Could also be "Qualifications". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Requirements and Qualifications; we need to decide which to use. The posting has "Required Qualifications" and later "Preferred Qualifications". So we can have a Requirements section for required qualifications, and a Qualifications section for preferred qualifications? Or we could combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine required and preferred into Qualifications? But they explicitly list both headings as possible. We could have Requirements (mandatory) and Qualifications (preferred). That seems reasonable. Thus:Requirements
with required qualifications list. ThenQualifications
with preferred qualifications. Preferred Qualifications: "Experience with architecture design patterns such as MVP or MVC, Gang of Four, etc. Experience with JQuery, JavaScript and common JavaScript Patterns Experience or passion for implementing cloud solutions on Amazon Web Services (AWS), Microsoft Azure, and/or Google Cloud Platform Experience with Anthropic Claude, OpenAI-compatible APIs, enterprise Master's degree in computer science or engineering. Hands-on experience in Java, Python or .NET" We need to parse that into bullet list. Let's extract: - Experience with architecture design patterns such as MVP or MVC, Gang of Four, etc. - Experience with JQuery, JavaScript and common JavaScript Patterns. - Experience or passion for implementing cloud solutions on AWS, Microsoft Azure, and/or Google Cloud Platform. - Experience with Anthropic Claude, OpenAI-compatible APIs, enterprise. - Master's degree in computer science or engineering. - Hands-on experience in Java, Python or .NET. Note: "Experience with Anthropic Claude, OpenAI-compatible APIs, enterprise" seems incomplete but we keep as is. Now "Wages and Salary" section: includes pay range $122,000 to $240,500, plus discretionary annual incentive program. That's pay info. So we need a Pay section. We'll putPay
thenwith that info. Benefits: Not mentioned explicitly besides maybe discretionary annual incentive program (which is part of pay). No explicit benefits like health, retirement. So we should not create Benefits section unless posting actually states them. It does not mention benefits. So skip Benefits. Schedule: Not mentioned besides travel up to 50% nationally. That's not schedule. No schedule info. So skip Schedule. We also have "Recruiting for this role ends on 10/15/2026." That's metadata; we can include in About the role paragraph or a short p. We must not include boilerplate like EEO etc. Not present. Now produce HTML fragment. We need to ensure proper nesting:
About the role
...
etc. Let's craft About the role paragraph: combine the introductory paragraphs up to recruiting end date. We'll write:Join our AI & Engineering team in transforming technology platforms, driving innovation, and helping make a significant impact on our clients' success. You'll work alongside talented professionals reimagining and re-engineering operations and processes that are critical to businesses. Your contributions can help clients improve financial performance, accelerate new digital ventures, and fuel growth through innovation. AI & Engineering leverages cutting-edge engineering capabilities to build, deploy, and operate integrated/verticalized sector solutions in software, data, AI, network, and hybrid cloud infrastructure. These solutions are powered by engineering for business advantage, transforming mission-critical operations. We enable clients to stay ahead with the latest advancements by transforming engineering teams and modernizing technology & data platforms. Our delivery models are tailored to meet each client's unique requirements. Engineering as a Service provides complete design, implementation, and technology operations, leveraging our core engineering expertise. We transform engineering teams, modernize technology, and deliver complex programs with a product engineering approach. Our flexible delivery models—traditional teams, pools, or pods—are tailored to each client's needs, offering engineering-led advisory, implementation, and operational capabilities to accelerate innovation. Recruiting for this role ends on 10/15/2026.
Now Responsibilities ul. We'll create li items as described. Now Requirements ul. We need to break required qualifications into bullet points. Let's list them: - Bachelor's degree in computer science or engineering, or a related technical field with a strong foundation in development (Java or .NET) with early experience as a full stack developer. - 4+ years' experience as a Solution Architect, with a strong focus on application development and scaling solutions for production environments. - 4+ years providing hands-on technical assistance to the delivery team, reviewing designs and code for architectural fit, monitoring engineers and serving as the primary technical liaison between business stakeholders and engineering. - 4+ years working on large-scale engagements as a Solution Architect in industry or in consulting. - Hands-on experience in Java, Python, or .NET. - Experience managing small on and offshore teams. - 1+ years' experience designing and delivering production-grade AI solutions such as LLM applications, RAG systems, agentic workflows, intelligent automation or ML-enabled products. - Hands-on software engineering capability in Python and/or a modern full-stack capability. - Experience owning the end-to-end solution architecture which includes defining integration patterns, data flows, and technical design decisions across systems. - Experience driving the technical delivery on-site (not remotely), translating business requirements into detailed technical designs, sequencing work across integration and