Director, Principal Cloud Architect
for each heading. Use - for lists. Use
for prose.
We must not repeat job title as heading. No Job ID. Remove boilerplate. Keep all substantive info.
We need to parse the content.
First paragraph: "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 about the role.
Then "Position Responsibilities" heading followed by bullet-like sentences each starting with a verb. We'll list them as
- .
Then "What you have Required Qualifications" heading then list of qualifications.
Then "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." That's pay info? It mentions salary range but not given; we cannot create Pay section unless posting actually states them. It mentions salary range but not actual numbers, so we should not create Pay section because it's not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." That's stating that there is a salary range and bonus eligibility, but not giving numbers. Is that enough to create a Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that there is a salary range and bonus eligibility, so we could include a Pay section with that info. However they also say "Prefer a few substantive sections over many thin ones." Might be okay to include Pay with that sentence. But they also said "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "salary range" is not filler; it's stating that there is a range but not giving numbers. Might be considered placeholder? It's ambiguous. Safer to not create Pay section because no actual numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that there is a salary range and bonus eligibility, which is stating them (though not numbers). I'd lean to include a Pay section with that sentence.
Benefits: they list benefits after "What’s in it for you". So we can create Benefits section with list.
Schedule: not mentioned.
Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits.
We need to use
for each heading.
We must not repeat job title as heading.
We need to preserve all substantive info.
Let's extract About the role prose: combine the first paragraph(s) up to before "Position Responsibilities". We'll keep as
.
Responsibilities: list each sentence after "Position Responsibilities". Let's extract them:
- 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'll put each as
- .
Qualifications: after "What you have Required Qualifications". Let's extract bullet points (they are sentences). List:
- 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.
- 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.
We'll list each as
- .
Pay: sentence: "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." We'll put as
.
Benefits: after "What’s in it for you At Schwab, you’re empowered to shape your future. We champion your growth through meaningful work, continuous learning, and a culture of trust and collaboration—so you can build the skills to make a lasting impact. 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. We offer a competitive benefits package that takes care of the whole you – both today and in the future:" then list:
- 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
We'll put as
- .
We must not include any boilerplate like EEO etc. Already removed.
Now produce HTML fragment.
Let's craft:
About the role
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.
Responsibilities
- 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.
Qualifications
- 10+ years
for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate. Keep all substantive info. We need to parse the content. First paragraph: "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 about the role. Then "Position Responsibilities" heading followed by bullet-like sentences each starting with a verb. We'll list them as
- .
Then "What you have Required Qualifications" heading then list of qualifications.
Then "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." That's pay info? It mentions salary range but not given; we cannot create Pay section unless posting actually states them. It mentions salary range but not actual numbers, so we should not create Pay section because it's not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." That's stating that there is a salary range and bonus eligibility, but not giving numbers. Is that enough to create a Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that there is a salary range and bonus eligibility, so we could include a Pay section with that info. However they also say "Prefer a few substantive sections over many thin ones." Might be okay to include Pay with that sentence. But they also said "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "salary range" is not filler; it's stating that there is a range but not giving numbers. Might be considered placeholder? It's ambiguous. Safer to not create Pay section because no actual numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that there is a salary range and bonus eligibility, which is stating them (though not numbers). I'd lean to include a Pay section with that sentence.
Benefits: they list benefits after "What’s in it for you". So we can create Benefits section with list.
Schedule: not mentioned.
Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits.
We need to use
for each heading. We must not repeat job title as heading. We need to preserve all substantive info. Let's extract About the role prose: combine the first paragraph(s) up to before "Position Responsibilities". We'll keep as
. Responsibilities: list each sentence after "Position Responsibilities". Let's extract them: - 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'll put each as
- . Qualifications: after "What you have Required Qualifications". Let's extract bullet points (they are sentences). List: - 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. - 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. We'll list each as
- .
Pay: sentence: "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." We'll put as
. Benefits: after "What’s in it for you At Schwab, you’re empowered to shape your future. We champion your growth through meaningful work, continuous learning, and a culture of trust and collaboration—so you can build the skills to make a lasting impact. 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. We offer a competitive benefits package that takes care of the whole you – both today and in the future:" then list: - 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 We'll put as
- .
We must not include any boilerplate like EEO etc. Already removed.
Now produce HTML fragment.
Let's craft:
About the role
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.
Responsibilities
- 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.
Qualifications
- 10+ years
- .
We must not include any boilerplate like EEO etc. Already removed.
Now produce HTML fragment.
Let's craft: