Lead Solution Architect with Financial Services Experience

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, we need to extract sections: The posting includes: - Intro paragraph: "Lead Solution Architect with Financial Services Experience- AI & Engineering/EaaS Lead Architect Join our AI & Engineering team..." This is about the role. - Then "Work you'll do:" with bullet-like sentences describing responsibilities. - Then "Recruiting for this role ends on 9/30/2026." That's metadata; we can fold into a short

maybe. - Then "Required Qualifications" list. - Then "Preferred Qualifications:" list. - Then "Limited immigration sponsorship may be available." That's maybe a note. - Also "6bility to travel up to 50% nationally based on the work you do and the clients and industries/sectors you serve." Likely a typo: "Ability to travel up to 50% nationally". That's schedule/travel. - No explicit Benefits, Pay, Schedule sections besides travel. We need to decide which sections to include. We have content for About the role (intro). Responsibilities (Work you'll do). Requirements (Required Qualifications). Qualifications (Preferred Qualifications). Skills maybe can be derived from required qualifications? But we could include a Skills section summarizing technical skills? However we must not invent or summarize away detail; we can only include sections if posting has real specific content for it. The posting does not have a separate "Skills" heading; but we could create a Skills section if we have specific skill list? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we cannot create a Skills section unless the posting explicitly mentions skills as a list. It does mention many skills within qualifications, but not under a "Skills" heading. Safer to not create Skills section. Benefits: Not mentioned. Pay: Not mentioned. Schedule: Travel mention could be considered schedule? It's about travel ability. Could be considered Schedule? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could include Schedule if posting states travel percentage. It says "6bility to travel up to 50% nationally based on the work you do and the clients and industries/sectors you serve." That's schedule/travel. So we can include Schedule section with that sentence. We also have recruitment end date; could be folded into a short

maybe under About the role or separate? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a

for the recruiting end date. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities and qualifications. We need to format lists with

• . For prose, use

  . We need to avoid repeating job title as heading. The page already shows it, so we don't add heading for title. We need to output only HTML fragment, no /, no markdown fences. Thus structure:

  About the role

  Lead Solution Architect with Financial Services Experience- AI & Engineering/EaaS Lead Architect 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 9/30/2026.

  Responsibilities

  • 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.
  • Support modernization efforts across clients' services capabilities working with a highly matrixed collaborative environment, working as a valued member of a cohesive architecture and development team.
  • 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 (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

  Requirements

  • 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.
  • 8+ years' experience as a Solution Architect, with a strong focus on application development and scaling solutions for production environments working with financial services clients.
  • 8+ years of experience with on-prem to AWS Cloud migration/integration which should include migration patterns (auth, middleware, data stores, event patterns, caching, telemetry); serverless patterns; data migration
  • 6+ 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.
  • 8+ years working on large-scale engagements as a Solution Architect in industry or in consulting.
  • Experience working as part of a large collaborative team.
  • 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.
  • Ability to travel up to 50% nationally based on the work you do and the clients and industries/sectors you serve.
  • Limited immigration sponsorship may be available.

  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 have also included travel ability under Requirements (though it's more schedule). But we also need a Schedule section? The instruction says we can include Schedule if posting actually states them. The travel ability is schedule-related. We could either put it under Requirements (as we did) or create a Schedule section. Since we already placed it under Requirements, we might not need a separate Schedule section. However we need to check if we missed any schedule-specific content besides travel. There's no explicit schedule like "full-time", "part-time". So we could keep travel under Requirements or create Schedule. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to keep travel under Requirements rather than create a thin Schedule section. But we already have a Schedule heading in the list of possible headings; we are not required to use it. So we can omit Schedule. We also need to ensure we didn't miss any responsibilities: The "Work you'll do:" section includes multiple sentences; we turned each into li. Need to verify we captured all. Original "Work you'll do:" paragraph: "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. Support modernization efforts across clients' services capabilities working with a highly matrixed collaborative environment, working as a valued member of a cohesive architecture and development team. 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" We captured each as li. Need to check punctuation and ensure we didn't lose any content. We missed the sentence "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." We