Director, Principal Cloud Architect
- .
- Requirements: Could be the "What you have Required Qualifications" list. That's required qualifications.
- Qualifications: Might be overlapping; maybe we can treat "Required Qualifications" as Requirements, and "Current advanced certification..." as Qualifications? But we need to avoid thin sections. Better to combine into one section "Requirements" that includes both required qualifications and preferred qualifications? However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct.
We have:
Required Qualifications bullet list (starting with "10+ years of progressive experience...").
Then after that: "Current advanced certification in GCP, AWS, Azure, security, data, or AI is preferred." That's a qualification (preferred). Also "Experience in financial services or another highly regulated industry is preferred..." That's also preferred.
Thus we can have Requirements (mandatory) and Qualifications (preferred/certifications). Also Skills maybe not explicitly listed; but we could infer skills from responsibilities? Better not to create Skills unless explicit. The posting does not have a separate "Skills" section. So we omit Skills.
Benefits: There is a paragraph under "What’s in it for you" describing benefits: 401(k) with company match and Employee stock purchase plan, Paid time for vacation, volunteering, and 28-day sabbatical after every 5 years of service for eligible positions, Paid parental leave and family building benefits, Tuition reimbursement, Health, dental, and vision insurance. That's specific benefits. So we include Benefits section.
Pay: The posting mentions "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." No actual salary range given. It says "In addition to the salary range" but does not give numbers. That's vague; we should not create Pay section unless posting actually states them. It does not give a specific range, just mentions eligibility for bonus. That's not a concrete pay figure. According to instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Since salary range not specified, we should not include Pay section.
Schedule: The posting mentions "We believe in the importance of in-office collaboration and fully intend for the selected candidate for this role to work on site in the specified location(s)." Also later: "Our Hybrid Work and Flexibility approach balances our ongoing commitment to workplace flexibility, serving our clients, and our strong belief in the value of being together in person on a regular basis." That indicates hybrid work expectation. That's schedule info: on-site/hybrid. It's specific: they intend for selected candidate to work on site in the specified location(s). Also mention hybrid work flexibility. So we can include Schedule section with that info.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule.
We need to output HTML fragment only, no /. Use
for headings. Use
- for lists. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to copy the text exactly? We can preserve meaning but not invent. We should try to keep the wording similar but can rephrase slightly? Safer to copy the sentences as they appear, maybe split into paragraphs. Let's extract content. About the role: The first paragraph(s) before "Position Responsibilities". Let's capture: "Your opportunity At Schwab, you’re empowered to make an impact on your career. Here, innovative thought meets creative problem solving, helping us “challenge the status quo” and transform the finance industry together. We believe in the importance of in-office collaboration and fully intend for the selected candidate for this role to work on site in the specified location(s). The Principal Cloud Architect will help shape the next generation of enterprise cloud and AI strategy and translate that strategy into secure, resilient, scalable, and reusable solutions. This senior individual-contributor role combines deep cloud architecture expertise with demonstrated experience designing production-grade AI and Enterprise Cloud platforms and solutions. The architect will lead technical workstreams, establish reusable architecture patterns, mentor peers, and drive alignment across engineering, architecture, security, data, risk, and platform teams. The ideal candidate will bring deep experience designing enterprise-scale cloud solutions, with strong architecture depth in GCP and demonstrated ability to operate effectively across AWS and Azure. Success requires strong technical judgment, clear architectural communication, and the ability to translate executive strategy into practical engineering execution in a highly regulated environment." That's a single paragraph but we can keep as
. Responsibilities: The bullet list under "Position Responsibilities". Let's capture each line: - Lead the architecture of secure, resilient, scalable, operable, and maintainable enterprise cloud and AI solutions from strategy and option analysis through production implementation and operational readiness. - Lead complex architecture workstreams, reviews, and governance decisions across architecture, engineering, security, data, risk, infrastructure, and operations, balancing delivery needs with architecture integrity, enterprise standards, and long-term sustainability. - Mentor engineers, architects, and technical leaders, and create reusable guidance that improves cloud and AI architecture quality, technical judgment, design consistency, and organizational capability. - Translate business and technology requirements into reusable cloud and AI architecture patterns, reference designs, decision frameworks, and implementation guidance that reduce duplication, accelerate delivery, and improve security, resiliency, operational consistency, and enterprise scalability. - Ensure cloud and AI solutions align with enterprise architecture, security, data, privacy, compliance, model-risk, resiliency, operational, and governance requirements. Clearly document architecture decisions, alternatives, assumptions, risks, exceptions, mitigations, and ownership. - Communicate effectively with engineers, architects, executives, and governance partners. Translate complex cloud and AI topics, limitations, risks, and tradeoffs into clear decisions, actionable plans, and accountable next steps. - Drive clarity, decisions, and execution in ambiguous, fast-moving environments with evolving requirements, competing priorities, and multiple stakeholders. - Partner with engineering and platform teams to move architecture from concept through implementation, production readiness, and ongoing operational ownership. Validate critical assumptions through proofs of concept, implementation reviews, infrastructure-as-code reviews, and technical evaluation where appropriate. - Bring strong critical thinking, problem-solving ability, and sound technical judgment to complex enterprise challenges. We need to preserve all. We'll put each as
- .
Requirements: The "What you have Required Qualifications" bullet list. Let's capture:
- 10+ years of progressive experience in technology architecture, including at least 8 years designing enterprise cloud solutions and demonstrated recent experience architecting production AI or generative AI capabilities.
- Deep experience creating enterprise architecture designs in GCP or AWS, with GCP strongly preferred, covering compute, networking, identity, data, integration, security, resiliency, observability, and platform operations.
- Deep understanding of secure-by-design cloud and AI architecture, including identity, least privilege, network segmentation, encryption, secrets management, logging, threat modeling, software supply-chain controls, and data protection in regulated environments.
- Experience establishing and applying Infrastructure as Code and policy-as-code patterns using Terraform or comparable technologies, including modular design, automated validation, security controls, versioning, and lifecycle management.
- Working proficiency with source control, CI/CD, artifact management, automated testing, and DevSecOps toolchains. The candidate must understand how architecture controls can be integrated into delivery pipelines.
- Experience designing mission-critical platforms with defined availability objectives, failure isolation, disaster recovery, observability, incident-management integration, auditability, and clear operational ownership.
- Demonstrated experience architecting and delivering production-grade AI and generative AI solutions, including data ingestion and preparation, model selection and integration, retrieval-augmented generation, agentic workflows, model serving, evaluation, observability, security, governance, and lifecycle management.
- Demonstrated ability to lead complex cross-functional architecture decisions, mentor technical professionals, and influence direction across engineering, infrastructure, security, data, risk, operations, and business stakeholders.
- Experience driving architecture from concept through implementation in partnership with engineering and platform teams.
- Experience working within iterative delivery models and integrating architecture guidance, governance, security, and operational-readiness requirements into continuous delivery practices.
- Bachelor’s degree in Information Technology, Computer Science, Cyber Security, or a related field, or equivalent practical experience.
We'll put as
- . Qualifications: The preferred qualifications/certifications and financial services experience. Content: - Current advanced certification in GCP, AWS, Azure, security, data, or AI is preferred. Certifications support, but do not replace, demonstrated architecture and production-delivery experience. - Experience in financial services or another highly regulated industry is preferred, particularly where architecture decisions required strong security, privacy, auditability, resiliency, risk-management, and regulatory controls. - In addition to the salary range, this role is also eligible for bonus or incentive opportunities. But note the last sentence about bonus is pay-related; we decided not to include Pay section. However it's still substantive info about bonus eligibility. Could we include it under Qualifications? It's not a qualification but a compensation detail. Since we are not making a Pay section, we could incorporate that sentence into Qualifications or Benefits? Probably better to keep it under Qualifications as a note about compensation eligibility. But instruction: do not create Pay/Schedule/Benefits sections unless posting actually states them. It does state bonus eligibility, but we are not making a Pay section; we could include that sentence elsewhere. However we must preserve ALL substantive information. So we need to include that sentence somewhere. Where? Could add to Benefits? It's about compensation, not benefits. Could add to Qualifications as a note. Or we could add a separate "Compensation" heading but not allowed because only allowed headings list includes Pay. Since we are not to create Pay unless posting actually states them; it does state bonus eligibility, but not a salary range. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state bonus eligibility, which is part of pay. So we could create a Pay section with that info. However the instruction also says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since they do state bonus eligibility, we could create a Pay section with that statement. But we need to avoid filler like "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." That's not filler; it's actual statement about bonus eligibility. So we could include Pay section with that sentence. But we also have no specific salary range; but the sentence mentions "In addition to the salary range". That's referencing a salary range not given. That could be considered filler? It's referencing unspecified range. Might be considered not specific. However the sentence still provides info about bonus eligibility. It's not filler like "commensurate with experience". It's a concrete statement about bonus eligibility. I'd say we can include Pay section with that sentence. But we must check if we already used "What’s in it for you" for benefits. That section includes benefits. Pay separate. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay
- for lists. Use